This project is read-only.
1
Vote

Run issue on Visual Studio 11 Express Web Edition

description

After installing the external js scripts and running the NuGet installer script the project won't build on VS 11 Express Web Edition because of the Code Analysis feature.

Fortunately this can be disabled in all four sub-projects using the sub-project property page 'Code Analysis' tab. This, or any better solution off course, should be added to the manual.

comments

aadami wrote May 21, 2012 at 7:14 PM

Hi,

We have been able to reproduce this behavior. When building the solution (after following all installation steps) in Visual Studio 2011 Express Web Edition beta, many build errors are thrown. On the other hand when we installed MilageStats in Visual Studio 2011 Beta Ultimate, there were no build errors.

It seems that the Express version runs only the basic analysis. In this version, you don't have access to the configuration tools on the Analyze menu, therefore I believe the custom rule sets that come by default with the application are not being loaded, and these build errors appear. In this case we verify that disabling the Enable Code Analysis on Build feature from the projects property page 'Code Analysis' tab as mentioned avoids the errors.

Additionally, when running the application we encountered the following error:

...Section or group name 'dotNetOpenAuth' is already defined. This can not be defined multiple times.

It seems that there may be an extra section definition in the web.config file after installing the NuGet packages. As we could avoid this error by removing the following section definition from the web.config file:

<section name="dotNetOpenAuth" type="DotNetOpenAuth.Configuration.DotNetOpenAuthSection" requirePermission="false" allowLocation="true" />

Thanks,

Agustin Adami
http://blogs.southworks.net/aadami

GerardVeneman wrote May 22, 2012 at 8:44 AM

Thanks for the reply. I've encountered the DotNetOpenAuth config issue as well and have been able to cope with it in the manner described in your comment.

As far as I'm concerned, this issue can be closed (workaround).