androidi said:
figuerres said:
*snip*

The app I made needs to know where the file is and modify it even when putting in a hdd from another computer. So if I put in a system hdd from another computer it would be quite crappy to start figuring out where the file might be without access to environment variables etc. An ok compromise would be if I could elevate the program when needed at runtime instead of doing that on every run. I agree on your other points however that still leaves the question why the Demand/Assert gave no errors.

 

re: Guidelines. Just following the same guideline as Microsoft when throwing these files in C:\ Smiley

 

dd_depcheckdotnetfx30.txt
dd_dotnetfx3error.txt
dd_dotnetfx3install.txt
dd_vcredistMSI782E.txt
dd_vcredistUI782E.txt
dd_VC_i64RuntimeMSI27F6.txt
dd_VC_i64RuntimeUI27F6.txt
dd_VC_x64RuntimeMSI27EF.txt
dd_VC_x64RuntimeUI27EF.txt
dd_VC_x86RuntimeMSI27E6.txt
dd_VC_x86RuntimeUI27E6.txt

if you need to get the file from a networked computer then the correct way is to save a config setting that lists the "standard" locations and add an option for UNC path

if UNC then store a string for the path name to the network share.

 

not hard to do.  and also will follow the standards for this kind of use.