diskpart.txt created in relative path location.

[DatKyle]

Pull Request #151 Changed the diskpart logic to use a relative path(.\diskpart.txt) instead of $diskpartScriptFile ($env:APPDATA\dbaclone\diskpartcommand.txt)

This has the side effect of leaving the file in the path the command was run in.

solution

Use the $diskpartScriptFile, as previously, and add logic to create the file location on the remote instance if it doesn't exist. not sure if we want to remove the file after we have finished with it.

I'm in the process of fixing this, just raising the issue so others know of the issue.

[lowlydba]

Not sure if this is still needed after #205 adds functionality to cleanup the file.

[DatKyle]

No longer needed as stated above.