.NET 4.0 build server reference assemblies warnings MSB3644 [duplicate]

Answer 1

Make sure you've installed .NET Framework Developer Pack, not a regular package.

If you're using Visual Studio, Code or other IDE, you should also install a .NET Targeting Pack.

Downloads page: https://www.microsoft.com/net/download

Related:

• The reference assemblies for framework ".NETFramework,Version=v4.6.2" were not found
• Targeting pack for .NET 4.5.2 not installed

Answer 2

Ok I found a solution that works. You need to do two things:

1. First add FrameworkPathOverride as a commandline parameter and point it to the references assemblies directory.

Something like

  msbuild -p:FrameworkPathOverride="C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0"

2. The second thing you need to do is find a full version of the reference assemblies directory. Since the copy installed by the windows SDK and the one installed by visual studio, I just copied mine from my development machine. Works fine.

One final note: the reason this might have happened to me in the first place is that our build server is a nice old windows server 2003 one. Too old for the windows SDK install to cope with?

Answer 3

Installation of SDK 8.1 (also for Windows 7) should also work in case of .net 4.5 requitements https://msdn.microsoft.com/en-US/windows/desktop/bg162891

Answer 4

This works for me, run it in powershell (without using FrameworkPathOverride):

cp -r "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.1\" "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0"

It's because 4.5 (or 4.5.1) is a drop-in replacement for 4.0

Answer 5

Because both .Net 4.0 and .Net 4.5 use CLR 4 and .NET 4.5 is an in-place replacement for .NET 4.0, you can safely apply the next solution:

in the folder:

    C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework

there are set of folders, one for every installed framework. The folder "v4.0" contain only xml files and folder "v4.5" contain both dll and xml files.

I created a symbolic link to this folder.

1. Run command prompt as an administrator.

2. Run the following script:

   cd C:\Program Files\Reference Assemblies\Microsoft\Framework.NETFramework ren v4.0 v4.0_old mklink /d v4.0 v4.5

A symbolic folder named "v4.0" is created and point to dlls of v4.5

Note: This solution is not a hack for net4,because I introduced why this solution is safe, i provide excerpt from .NET 4.5 is an in-place replacement for .NET 4.0:

When .NET 4.5 is installed it effectively replaces .NET 4.0 on the machine. .NET 4.0 gets overwritten by a new version of .NET 4.5 which - according to Microsoft - is supposed to be 100% backwards compatible.

When you install .NET 4.5 your .NET 4.0 assemblies in the \Windows.NET Framework\V4.0.30319 are overwritten with a new set of assemblies. You end up with overwritten assemblies as well as a bunch of new ones.

If you open the properties of System.dll assembly in .NET 4.5 you'll also see: Notice that the file version is also left at 4.0.xxx.

This solution is like my own except it copies the assemblies from net45 to net4.

See also.NET Versioning and Multi-Targeting - .NET 4.5 is an in-place upgrade to .NET 4.0 Note: Net 4 life time is ended, it is better to upgrade to net 4.5.2

Answer 6

To add to cixelsyd's answer:

The default setting in the Windows SDK v7.1 installer is that "Intellisense and Reference Assemblies" is 'semi-checked' - change that to fully checked and the warnings are gone :-)