Using assembly names that contain the word update in Visual Studio 2005

I have been using Visual Studio 2005 for several years, and I have run into a problem that I am wondering if this is her stupidity. I am using Windows Vista, and I cannot debug a project with an assembly name containing the word "update" without starting Visual Studio in administrator mode.

For example, I created a new Windows Form Application project, leaving the default assembly name windowapplication1 and pressing F5 for debugging and, of course, completed the project. Then I changed the assembly name to UpdateManager and hit F5 again. This time it will not work and says that this requires increased permissions. Changing the assembly name in UpdatManager (no 'e') and re-executing?

Is this setting or behavior built into Visual Studio?

+3
source share
1 answer

Amazing problem. You are using an old version of VS that does not automatically embed the manifest in the EXE to signal Vista that your program is aware of Vista's UAC policies. This makes it treat your program as an outdated program; it automatically redirects access to files and registries to safe places.

This works well for older programs, except for those designed to update, fix, or install programs. There is no easy way in Vista to see that a program is an installer. In addition, you guessed it, this is the name of the program.

VS2005. , , , UAC.

+4

Source: https://habr.com/ru/post/1748131/


All Articles