Browse by term
How to fix SharpDevelop's 'F# compiler is not installed' error by creating a Windows junction from the expected F# compiler path to the actual F# SDK installation.
Why build machines need the actual SDKs installed, not just referenced targets, for MSBuild to reliably build Silverlight and web-application projects.
A note on machine- and edition-specific Code Analysis paths added to Visual Studio project files and the problems they cause for portable projects, mixed-edition teams, and continuous integration builds.
Explains why Silverlight and Web Application projects require Microsoft.WebApplication.targets at Visual Studio's expected MSBuild location, and how to work around this dependency on a toolset-free continuous integration server.
Troubleshooting PostSharp license errors on a TeamCity continuous integration server and configuring the correct license activation for unattended builds.
Troubleshooting a Jenkins MSBuild failure caused by using the .NET 3.5 MSBuild version with the ImportGroup element, which requires MSBuild 4.0, despite targeting .NET Framework 3.5.
How to run StyleCop on a minimal Continuous Integration server without installing it by storing the required assemblies and MSBuild target in the project's DevTree.
How to integrate NuGet package restore into an MSBuild target, keeping dependencies out of source control while ensuring Visual Studio and CI builds restore the required package versions.
How to suppress automatic ArcGIS Add-In registration during Visual Studio builds under limited permissions by placing a Dont_EsriRegAddin.txt file beside the project file.
How to run esriRegasm outside an ArcGIS installation and on build/CI servers without ArcGIS, including the required permissions and MSBuild target changes.
How to use a project-specific FxCop custom dictionary with Visual Studio Code Analysis by linking the dictionary into each project and configuring CodeAnalysisDictionary in the csproj file.
How to use a renamed FxCop custom dictionary with Visual Studio Code Analysis, MSBuild targets, FxCopCmd, and the standalone FxCop GUI.
How missing custom cultures can cause the MSB3105 duplicate Resources error during compilation
Fixing a Code Analysis/FxCop error in mixed VS2005/VS2008 projects by pointing the VS2005 targets at the VS2008 FxCop binaries.
How to make a custom FxCop dictionary available to Visual Studio.
How to integrate Microsoft FxCop into Visual Studio builds using post-build events
How to fix MSB3073 errors in Visual Studio post-build events by quoting macros such as $(TargetPath) when file or folder paths contain spaces.
How an orphaned assembly in the GAC can cause the misleading MSB3217 'Cannot register assembly' build error and why removing stale dependencies solves it.