JomiTech Forums

No, the TwineCompile MSBuild assembly has no issues with brackets in the path. Try this: 1. Create a registry key called: HKEY_LOCAL_MACHINE\SOFTWARE\JomiTech\TwineCompile Note that I've left out the Wow6432Node. 2. Create a string value called InstallPath in there, set to the TwineCompile path (C:\...

What version of TwineCompile are you using?

Use regedit to see if Administrator has the necessary permissions to read that key.

Does the user have access to the following registry key?

We'll make a note to add this back into the setup.

Glad you solved it - although it was the hard way.

TwineCompile does not change the include paths at all. I'm very surprised that you're seeing compiler errors when switching back to bcc32.

With TwineCompile 3.2, we made TC the default compiler with MSBuild. To revert it, call MSBuild using this command line parameter:

/p:CoreCompileDependsOnTargets="DccCompile;BccCompile;TasmCompile;BrccCompile;"

Do your project files include the TCTargets.targets file?

Thanks, we'll definitely try to get you an early beta.