Quote:Original post by Rydinare Anyone else using Visual Studio on Vista? The big annoyance I have is that periodically when creating new files or folders programmatically or through external programs called by VS, they are created with no permissions and I have to manually fix the permissions. This seems ridiculous. How can a security model prevent me from accessing the files I just created? That makes no sense, so maybe I'm missing something?
One suggested option was disabling UAC, but I had complications when trying that option.
In what directory are you creating these files? It almost sounds like they're not inheriting permissions correctly from the parent directory.
In many of the cases, it was simply creating temporary files below the folder that my project was in. The folder had permissions but the lower level folders were granted with no permissions and the local user as owner instead of the domain user. Very strange, right?
It's a no brainer, but can make things go boom; if not checked already -- ensure VS is always running as Admin -- and that anything it invokes is too. Otherwise ownership issues will keep spawning :(
If this doesn't help...hm, I use TweakVI to turn off all scary Vista UAC stuff -- maybe you can avoid the problems this way. Obviously this won't help for testing (everyone at home will likely have it turned ON), but for dev it might :)
~Shiny
------------'C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, it blows away your whole leg.' -Bjarne Stroustrup
Quote:Original post by Rydinare Anyone else using Visual Studio on Vista? The big annoyance I have is that periodically when creating new files or folders programmatically or through external programs called by VS, they are created with no permissions and I have to manually fix the permissions. This seems ridiculous. How can a security model prevent me from accessing the files I just created? That makes no sense, so maybe I'm missing something?
One suggested option was disabling UAC, but I had complications when trying that option.
In what directory are you creating these files? It almost sounds like they're not inheriting permissions correctly from the parent directory.
In many of the cases, it was simply creating temporary files below the folder that my project was in. The folder had permissions but the lower level folders were granted with no permissions and the local user as owner instead of the domain user. Very strange, right?
And what folder do you store your projects in, and what are the permissions on that folder?
It sounds bizarre to me because I've never had problems like this, and I run both VS 2005 and 2008 unelevated with UAC turned on.
Quote:Original post by Rydinare Anyone else using Visual Studio on Vista? The big annoyance I have is that periodically when creating new files or folders programmatically or through external programs called by VS, they are created with no permissions and I have to manually fix the permissions. This seems ridiculous. How can a security model prevent me from accessing the files I just created? That makes no sense, so maybe I'm missing something?
One suggested option was disabling UAC, but I had complications when trying that option.
In what directory are you creating these files? It almost sounds like they're not inheriting permissions correctly from the parent directory.
In many of the cases, it was simply creating temporary files below the folder that my project was in. The folder had permissions but the lower level folders were granted with no permissions and the local user as owner instead of the domain user. Very strange, right?
And what folder do you store your projects in, and what are the permissions on that folder?
It sounds bizarre to me because I've never had problems like this, and I run both VS 2005 and 2008 unelevated with UAC turned on.
There is quite a list of issues actually with VS2005 and Vista which you can see here. That's probably why they advise to run with admin permission since it doesn't look like they will be releasing another service pack for VS2005 anytime soon now that VS 2008 is out. Same thing goes for SQL Server 2005. Actually, same problems will most likely occur for any app that wasn't designed with Vista's elevated security precautions in mind hence the aggravation and refusal of some individuals to upgrade!
[size="2"]Don't talk about writing games, don't write design docs, don't spend your time on web boards. Sit in your house write 20 games when you complete them you will either want to do it the rest of your life or not * Andre Lamothe
