@kgambill wrote:
I've recently installed MonoGame and have begun building our first game project using it. Initially I installed the prebuilt MonoGame install and everything worked fine with a simple Game1 project using the MonoGame Framework.
Currently I'm in the process of attempting to change our project over to include our game project as well as all the source for the MonoGame Framework (for Windows). I'm attempting to get things set up so that there are no dependencies on other programmers installing the MonoGame SDK on their own, everything is built and linked directly from the source depot.
For reference, a rough idea of our directory structure is:
/code/external/MonoGame-3.7.1
/code/src/Game1.csprojThe external/MonoGame-3.7.1 directory has the downloaded source from GitHub and I've run protobuild on it already.
The first issue I encountered was the Game1.csproj file had the following:
I updated this to be:
That solved the issue, but now when attempting to build I'm seeing the following error:
1>\code\external\MonoGame-3.7.1\MonoGame.Framework.Content.Pipeline\MonoGame.Content.Builder.targets(40,5): error MSB4062: The "MonoGame.Build.Tasks.CollectContentReferences" task could not be loaded from the assembly \code\external\MonoGame-3.7.1\MonoGame.Framework.Content.Pipeline\MonoGame.Build.Tasks.dll. Could not load file or assembly 'file:///\code\external\MonoGame-3.7.1\MonoGame.Framework.Content.Pipeline\MonoGame.Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.The issue is that the DLL is not in that location, it's in
code\external\MonoGame-3.7.1\Tools\MonoGame.Build.Tasks\bin\Windows\AnyCPU\DebugHowever I'm not sure what the proper solution is here. I could just update the Output Directory of the BuildTasks project to point to where the ContentReferences error is mentioning, but I suspect that is a band-aid instead of a proper fix as I'm not sure exactly where that path is being determined in the first place. I'm not extremely familiar with the .targets file.
Any advice on this (and setting up the source to be fully built from within your game's solution) is greatly appreciated.
Posts: 1
Participants: 1