Build/Test Issues

Building MonoGame project

Started by narshe on 7,221 views

I have a monogame project that I would like to test. Run NCrunch tries to build it, it fails on running the content pipeline. Is there any way to fix this?

Here is the error.

NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues
..\..\..\..\Program Files (x86)\MSBuild\MonoGame\v3.0\MonoGame.Content.Builder.targets (67, 5): The command ""C:\Program Files (x86)\MSBuild\MonoGame\v3.0\Tools\MGCB.exe" /@:"C:\Users\Josh\AppData\Local\NCrunch\25000\1\Shmup\Content\Content.mgcb" /platform:Windows /outputDir:"C:\Users\Josh\AppData\Local\NCrunch\25000\1\Shmup\Content\bin\Windows" /intermediateDir:"C:\Users\Josh\AppData\Local\NCrunch\25000\1\Shmup\Content\obj\Windows" /quiet" exited with code -532462766.
Is there a generic way to ignore this? It's an <ItemGroup> of <MonoGameContentReference Include="Content\Content.mgcb" /> in the project file. Can that be ignored some how?

If not, what do you suggest as a workaround? I think I could move pretty much ALL my code into a class library that the monogame project references.
Taking another look at the error you've received from your build, there is a possibility that this error is being thrown because NCrunch hasn't identified the .mgcb files and copied them to the workspace. If you include all .mgcb files using the 'Additional files to include' project-level configuration setting (http://www.ncrunch.net/documentation/reference_project-configuration_additional-files-to-include), for example, using the wildcard '**.mgcb', this will tell NCrunch about these files so that they can be copied to the workspace.

Otherwise, the best option here may well be to use a build override to prevent NCrunch from either running the monogame build steps or from including the content reference declarations.

For example:

<ItemGroup Condition="'$(NCrunch)' != '1'">
<MonoGameContentReference Include="Content\Content.mgcb" />
</ItemGroup>

If there is an import statement importing the monogame build targets, specifying a similar condition to the above on the target import tag may also suppress the monogame build steps.
Adding that file to additional files worked. Thanks!

Post a reply

Log in to reply.