Is the Broken Code Related to UAC Settings in AppData Folder?

[CRGreathouse]

Broken code -- UAC related?

Here's the code I'm having trouble with, cut down the relevant part:

protected void ProcessFiles(string[] files)
{
	if (File.Exists(outputFilename))
		throw new Exception("Output file " + outputFilename + " already exists!");
	if (Directory.Exists(direc(outputFilename)))
		throw new Exception("Output file directory " + direc(outputFilename) + " does not exist!");
	MessageBox.Show("output filename ok");
	StreamWriter sw;
	try
	{
		sw = new StreamWriter(outputFilename);
	}
	catch
	{
		throw new Exception("Unspecified error");
	}
	MessageBox.Show("sw setup");
	// . . .

The "output filename ok" dialog comes up, but then nothing. The program doesn't crash, the exception doesn't occur, the "sw setup" dialog doesn't appear.

The output filename, for what it's worth, is in the user's AppData folder, so I don't think this should be a problem even with Vista's UAC, but I might be missing something obvious.

 

[Future Bruno]

The answer to this might be UAC-related. To check, you can try running the program as an administrator. If that works, then it's likely that UAC is blocking the program from writing to the AppData folder. To fix this, you can either create a shortcut to the program and select "Run as administrator" or modify the UAC settings so that the program is allowed to write to that folder.

 

[quicknote]

It is possible that the code is not properly handling the User Account Control (UAC) settings in the user's AppData folder. UAC is a security feature in Windows that requires user permission for certain actions, such as creating or modifying files in certain protected locations. It is possible that the code is not properly requesting permission from the user to create the output file in the AppData folder, causing the program to get stuck at the "sw setup" dialog.

To fix this issue, the code may need to be modified to properly handle UAC settings. This could involve adding code to request permission from the user before attempting to create the output file or changing the location of the output file to a location that does not have UAC restrictions. Alternatively, the code may need to be run with elevated privileges to bypass UAC restrictions.

It is also possible that there could be other underlying issues causing the code to break, so further debugging and troubleshooting may be necessary. It may be helpful to review any error logs or try running the code on a different system to see if the issue persists.