Today I needed to run some unit tests in an admin console (thanks to Aaron), so I fired up VS as admin and built the project and ran my tests. This was the first time I had built the project, so when I went back to loading VS as Non-Admin, I got an access denied when VS was trying to build the .resources file in the obj directory. How annoying. Now the reason for this is because by default Windows 2003 (my dev platform) takes ownership of files and other objects by the Administrators group. So as an admin, the file was owned by Administrators and I did not have access to the file anymore . Now you can change this policy to creator in Local Security Policy (secpol.msc) in the user rights assignment so I leave it up to you how you want to deal with this. Aaron has posts on this so you should give it a read before you make your decision.