I've recently added some custom Portable Class Library projects to an application that is built in an build server. The build was working fine, but after that it stopped working and shows me the following messages:
C:WindowsMicrosoft.NETFramework64v4.0.30319Microsoft.Common.targets(983,
5): warning MSB3644: The reference assemblies for framework
".NETPortable,Version=v4.0,Profile=Profile136" were not found.
C:WindowsMicrosoft.NETFramework64v4.0.30319Microsoft.Common.targets(1578,
5): warning MSB3270: There was a mismatch between the processor
architecture of the project being built "MSIL" and the processor
architecture of the reference
"C:WindowsMicrosoft.NETFramework64v4.0.30319mscorlib.dll",
"AMD64".
error CS0234: The type or namespace name 'Linq' does not exist in the
namespace 'System' (are you missing an assembly reference?)
The build server specs:
The solution is a .NET 4.0 application and the portable projects target .NET4.0+ e Silverlight 5, only.
I have checked my development machine (Windows 8, Visual Studio 2012). There is indeed a folder "C:Program Files (x86)Reference AssembliesMicrosoftFramework.NETPortablev4.0ProfileProfile136" (in fact, the profiles for .NET 4.0 go up to 158).
In the build machine, however, there are only folders for profiles up to 131.
Is Portable Class Library Tools up to date? It seems it miss installing profiles for the most recent platforms.
UPDATE
I copied the ".NETPortablev4.0ProfileProfile136" of my development machine to the build server, and now the application builds successfully. I still would like to know why installing the Portable Class Library Tools does not work out of the box.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
