Tools version 4.0

We're using Cruse Control to manage our build process. AS we convert vs projects to vs, we're leaving the target framework set at 3. At this point we're not going through and converting all our solutions to vs; not if we don't have to. All was well until a web project that was targeting the 4. At which point this error popped up:. CS The type 'System. So why was a 3. Probably because I was using MSBuild 4.

To resolve this issue, I went to the relevant MSBuild project files that cruise control uses and changed their toolsVersion to 4. This got passed that conflict error. But now everytime it tries to build a project that's in a solution that we haven't yet converted to a vs project, it breaks with an error like this:.

This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded. If I open the solution that contains that project in Visual Studio and do the conversion, build it and commit that and force another build, I get passed that error only to find that another not yet converted project is tossing that same error.

So now I am for sure using MSBuild 4. Why can't 4. The issue is that you have migrated part of your projects to to visual studio Any project that references a project by project reference will give you this compile time error. Try updating all. When you build a solution on the command line and specify a ToolsVersion for msbuild. The ToolsVersion attribute is also used for project migration. If you then try to open that project in Visual Studio , it doesn't recognize the upgraded ToolsVersion and therefore builds the project as though the attribute was still set to 3.

Visual Studio uses a ToolsVersion of Visual Studio uses ToolsVersion In many cases, you can open the project in multiple versions of Visual Studio without modification. Visual Studio always uses the correct Toolset, but you will be notified if the version used does not match the version in the project file. In almost all cases, this warning is benign as the Toolsets are compatible in most cases.

Sub-toolsets, which are described later in this topic, allow MSBuild to automatically switch which set of tools to use based on the context in which the build is being run.

For example, MSBuild uses a newer set of tools when it's run in Visual Studio than when it's run in Visual Studio , without your having to explicitly change the project file.

Implement a Toolset by selecting the paths of the various tools, targets, and tasks that make up the Toolset. The tools in the Toolset that MSBuild defines come from the following sources:. By using ToolLocationHelper methods. Toolset properties specify the paths of the tools. In earlier versions, MSBuild uses the value of the ToolsVersion attribute in the project file to locate the corresponding registry key, and then uses the information in the registry key to set the Toolset properties.

For example, if ToolsVersion has the value Alternately, you can determine the Toolset programmatically by calling the methods of the ToolLocationHelper class. The class includes these methods:. NET Framework folder. GetPathToBuildTools returns the path of the build tools. For versions MSBuild prior to Note for RStudio users: you need at least RStudio version 1.

After installation is complete, you need to perform one more step to be able to compile R packages: we put the location of the Rtools make utilities bash , make , etc on the PATH. The easiest way to do so is by creating a text file. Renviron in your Documents folder which contains the following line:. You can do this with a text editor, or from R like so note that in R code you need to escape backslashes :.

Restart R, and verify that make can be found, which should show the path to your Rtools installation. See the links below to learn more about rtools4 and the Windows build infrastructure.