This project is read-only.

Missing MSBuild reference


The last line of the generated project files (ProjectName.csproj):
<Import Project="$(MSBuildExtensionsPath)\Microsoft\XNA Game Studio\Microsoft.Xna.GameStudio.targets" />
Causes all references become missing and outputs the warning message "The referenced component 'System' can not be found".

It seems that the behavior of "$(MSBuildExtensionsPath)" referenced in Microsoft.Xna.GameStudio.targets has changed from "C:\Program Files (x86)\MSBuild\" to "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\"

By copying the "XNA Game Studio" directory from the old to the new directory, the problem is resolved.

I'm using Windows 8.1 if it matters.

Thank you so much for the work on the plugin. Now I can finally save some space by deleting old Visual Studio versions.


Enfenion wrote Mar 23 at 10:20 AM

Hmm... My fix doesn't seem to fix everything.

I get the following error message when compiling a project with an image in the Content project:
Error loading pipeline assembly "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Microsoft.Build.Framework.dll".

wrote Mar 26 at 1:20 AM

jamesgoggin wrote Mar 26 at 1:28 AM

Getting the same issue as Enfenion:
Error loading pipeline assembly "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Microsoft.Build.Framework.dll".
Haven't had any luck debugging the issue but my assumption is that it is related to the BeforeBuild/AfterBuild process for the content library. My solution is made up of the following:
  1. Windows Game (4.0) Project
  2. Content Project (4.0)
  3. Windows Game Library (4.0) Project
  4. Content Pipeline Extension Library (4.0) Project
Hope this helps.

wrote Mar 26 at 10:38 AM

mklemarczyk wrote Mar 26 at 10:40 AM

Unfortunately Microsoft changed some aliases.
I'm working on it. Solution should be available on Sunday (April 2nd, 2017)

wrote Mar 28 at 12:02 PM

mklemarczyk wrote Mar 29 at 10:35 PM

Problem is much bigger, we should rebuild content libraries with new MSBuild to make it work.

There is a workaround to make it work for now:

The solution should be published before April 30th, 2017. Sorry for so long time.
If anyone want to participate in this process let me know via message.
It will require good C# knowledge and Build process..