Wout

I'm building an installer which installs some example solution files. Shortcuts to these solutions are created in the windows menu. However when clicking the shortcut (they are "advertised" shortcuts, in .msi lingo), a security warning pops up. (Similar to the one mentioned in http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=395354&SiteID=1.)

Now my questions are (in order to get rid of that popup! It will be annoying to customers):

The "More Details" button mentions the following:

---------------------------
Microsoft Visual Studio
---------------------------
An item referring to the file "C:\Program Files\XXX\YYY\SomeApp.exe.config" was found in the project file "C:\Program Files\XXX\YYY\Examples\ZZZ\SomeProject.csproj". Since this file is located within a system directory, root directory, or network share, it could be harmful to write to this file.
---------------------------
OK
---------------------------

I see no item referring to that file when inspecting the .csproj file. So what is it talking about

Further VS says that the project has been "customized". What does this mean (I.e. how do I "uncustomize" it )

Any help is appreciated,

Wout



Re: Visual C# IDE Getting security warning when starting Visual Studio.

Wout

Some more info: I figured out where the dialog box comes from, see here:
http://msdn2.microsoft.com/en-us/library/ms228217(VS.80).aspx

The issue seems to be that in the solutions I'm building to a directory higher in the hierarchy, but still within the directory tree that belongs to the component (Several solutions build into a single binary directory). So the security police seems to be a bit over active. And the funny thing is that when I click to load the project, and ignore the warning in the future, a .suo file gets written. And if I include that .suo file in the installer, then no problem! So there goes the security!

Anyways, I still prefer a good solution to this then this hack...

Wout





Re: Visual C# IDE Getting security warning when starting Visual Studio.

Wout

I worked around this by building into the normal directory, and then doing a copy in the post build event. (I guess that means that the security warning is pretty useless).

Wout