Are there any issues with moving a project to a different machine?

Hi all,

I reported an unrelated bug in VS to Microsoft and gave them the sample project that I found the bug in. I said that they would need to install Paradox and gave the link. The technician however, said that he couldn’t get the project to compile. Are there any issues with moving projects to a different machine ? I suggested that using GameStudio to rebuild the asset chain might help. But I’m not really sure why the project wouldn’t build.

I can’t think of anything that would make it fails if moved to another machine.

You could always delete obj/bin folder to make sure of that (if this happens to fix it, let us know, we could investigate about what makes it machine dependent).

What is the error? Is there any error/diagnostic/build log?

He didn’t give me much information. Here’s what he said … “I’m able to build new projects in paradox studio but once I open them in VS, the references appear to get messed up and it no longer builds. I was able to make some progress with your repro code by launching the game exe directly after building in paradox studio.”

I will start up the laptop tonight and see if i can reproduce any build issues myself. And if i can get any build-log from Microsoft I will get it to you.

Microsoft sent me the error log …

For Paradox build, I get this error in VS:
Show Details Severity Code Description Project File Line
Error The
command
"“C:\Users\marcpop\AppData\Local\Programs\Paradox\GamePackages\Paradox.1.0.0-beta03\Bin\Windows-Direct3D11\SiliconStudio.AssemblyProcessor.exe”
–platform=Windows --targetFramework=v4.5 --auto-notify-property
–parameter-key --auto-module-initializer --serialization
"C:\Users\marcpop\Documents\Bug 1079396
Repro\Samples\Samples\Bin\Windows-Direct3D11\Debug\Samples.Game.dll""
exited with code 1. Samples.Game

When I try to build in Paradox studio, I get a similar error but it includes more information in the build log:
[(0,0)]:
Info:
“C:\Users\marcpop\AppData\Local\Programs\Paradox\GamePackages\Paradox.1.0.0-beta03\Bin\Windows-Direct3D11\SiliconStudio.AssemblyProcessor.exe”
–platform=Windows --targetFramework=v4.5 --auto-notify-property
–parameter-key --auto-module-initializer --serialization
"C:\Users\marcpop\Documents\Bug 1079396
Repro\Samples\Samples\Bin\Windows-Direct3D11\Debug\Samples.Game.dll"
[(0,0)]: Info: Unknown custom metadata item kind: 6
[(0,0)]: Info: Microsoft.Cci.Pdb.PdbDebugException: Unknown custom metadata item kind: 6
[(0,0)]: Info: at Microsoft.Cci.Pdb.PdbFunction.ReadCustomMetadata(BitAccess bits)
[(0,0)]: Info: at Microsoft.Cci.Pdb.PdbFunction…ctor(ManProcSym proc, BitAccess bits)
[(0,0)]: Info: at Microsoft.Cci.Pdb.PdbFunction.LoadManagedFunctions(BitAccess bits, UInt32 limit, Boolean readStrings)
[(0,0)]:
Info: at Microsoft.Cci.Pdb.PdbFile.LoadFuncsFromDbiModule(BitAccess
bits, DbiModuleInfo info, IntHashTable names, ArrayList funcList,
Boolean readStrings, MsfDirectory dir, Dictionary2 nameIndex, PdbReader reader) [(0,0)]: Info: at Microsoft.Cci.Pdb.PdbFile.LoadFunctions(Stream read, Dictionary2&
tokenToSourceMapping, String& sourceServerData, Int32& age,
Guid& guid)
[(0,0)]: Info: at Mono.Cecil.Pdb.PdbReader.PopulateFunctions()
[(0,0)]: Info: at Mono.Cecil.Pdb.PdbReader.ProcessDebugHeader(ImageDebugDirectory directory, Byte[] header)
[(0,0)]: Info: at Mono.Cecil.ModuleDefinition.ProcessDebugHeader()
[(0,0)]: Info: at Mono.Cecil.ModuleDefinition.ReadSymbols(ISymbolReader reader)
[(0,0)]: Info: at Mono.Cecil.ModuleReader.ReadSymbols(ModuleDefinition module, ReaderParameters parameters)
[(0,0)]: Info: at Mono.Cecil.ModuleReader.CreateModuleFrom(Image image, ReaderParameters parameters)
[(0,0)]: Info: at Mono.Cecil.ModuleDefinition.ReadModule(Stream stream, ReaderParameters parameters)
[(0,0)]: Info: at Mono.Cecil.ModuleDefinition.ReadModule(String fileName, ReaderParameters parameters)
[(0,0)]: Info: at SiliconStudio.AssemblyProcessor.AssemblyProcessorApp.Run(String inputFile, String outputFile)
[(0,0)]: Info: Unknown custom metadata item kind: 6

I
was not able to find a solution to this on the internet but maybe the
Paradox guys have seen it before. I get the same error once I’ve opened
the project in either 2013 or 2015. If I don’t open in VS, then the
project continues to build fine in Paradox Studio.