views:

2396

answers:

4

I've taken the plunge and upgraded (or maybe downgraded?!) from WinXP to Vista.

Everything appeared to be working ok except that when I fired up my machine this morning and opened my C# application in Visual Studio I got a few "Load of property 'OutputPath' failed. The entered path is not a valid output path" errors.

I tried to rebuild the application and found that for some mysterious reason I'd lost access to the executables that Visual Studio creates. Everything else in the solution was still mine, but the compilation results weren't. In some cases the 'Administrator' owned them, and in some cases I still owned them but had no rights.

I'm running as Administrator, so to be denied access to my own files that I created myself is more than a little infuriating.

Have I missed something in the way Visual Studio and Vista play together, or do I wipe the machine and burn another two days reinstalling WinXP?

A: 

Oh.. this is a cool one =D

have you tried to change your output path?

Well, click on the right button on your project in the "solution explorer". Go on properties, in the Build tab. There you can try to work some things out..

VS2008 is a very strange thing, since it was developed to run in Vista! =D

good luck!

José Leal
A: 

On top of my head:

  1. Disable User Access Control.
  2. Make sure you've not checked in your executables into source control (they may be readonly) :)

EDIT: I'd few problems on my Vista x64 box that got me confused as well [I was also running as Administrator]. Disabling UAC got rid of this 'Administrator' but not an Administrator problems :D

Vyas Bharghava
If developers insist on running with UAC disabled, then we shall never make any progress.
Will Dean
Maybe UAC should have been developed properly before being implemented then? I'm not going to suggest to a user that they should use broken software.
Malfist
This did the trick.
Andrew
I'm assuming this has been voted down because it advocates disabling UAC. From my past experience with Vista UAC is a complete trainwreck, and having disabled it on this install has proved that again since the problem has disappeared.
Andrew
@Will: I'm not sure what UAC accomplishes except ask user permission to proceed (which the user may not have the foggiest about). Vista is a tool in the end and must serve users' needs. If disabling UAC gets something done, so be it. And hey, we're talking about developers here.
Vyas Bharghava
@Andrew: Glad it worked for you. :)
Vyas Bharghava
A: 

Open your .csproj file and make sure your output path C:\test\ is correct that one more place to check.

A: 

When I debug programs under VS08 (running VS08 as administrator), they cannot create folders or files off the root directory. I have changed the security settings on the folders and still nothing. I get access denied errors on all writes.

I have used Vista since it came out. I have never had ANYTHING but problems with it. I recently bought a new machine loaded with plenty of RAM and processor power. It is the SLOWEST machine I have EVER owned - and I bought my first computer in 1979!

I have to develop to run on Vista, but MS needs to pull their head out and give us some options. I have wasted 100's of hours on security issues with Vista. I even removed ALL anti-virus software because, from what I can tell, I don't need it. I can't even get access to my own OS, how the HELL is a virus going to do it?

Vista ... what a waste.

Mike