The different scenarios for debugging Turnkey generic code

1. You have the MDrivenServer stable and you want to step through Turnkey-generic code
2. Debug CodeDress code from the model or you have the MDrivenServer stable and you want to step through Turnkey-generic code
3. You want to debug towards local prototyping xml based persistence - cutting MDrivenServer out of the equation

1: MDrivenServer stable and you want to step through Turnkey-generic code

Use MDrivenServerOverride.xml with setting:

<MDrivenServerOverride MDrivenServerPWD="pwd for mdrivenserver user a">https://<urltomdrivenserver usually ending with __MDrivenServer></MDrivenServerOverride>

2: Debug CodeDress code from the model or you have the MDrivenServer stable and you want to step through Turnkey-generic code

Make sure you have the same model version in the MDrivenServer as you have locally in Visual Studio. Use MDrivenServerOverride.xml with setting:

<MDrivenServerOverride MDrivenServerPWD="pwd for mdrivenserver user a" CodeDressOverride="C:\PathToCodeDress_bin_Debug_assemblies" >https://<urltomdrivenserver usually ending with __MDrivenServer></MDrivenServerOverride>

3: You want to debug towards local prototyping xml based persistence - cutting MDrivenServer out of the equation

Note that for this option CodeDress will always try to find assemblies close to the model rather than in ModelCodeAssemblies. The tried paths for assemblies are "bin/debug" and "../bin/debug" (relative to model path): .Use MDrivenServerOverride.xml with setting:

<MDrivenServerOverride PrototypeWithMDrivenDesignerInPath="C:\PathToLocalModel modlr or ecomdl"></MDrivenServerOverride>

All steps require Turnkey generic code access to work fully - but can be used partially by opening turnkey local installations in visual studio as web site.

If you want to see status of a running Turnkey app look here: Serverinfo

Other tips and tricks:

There are many chrome plugins to intercept where files are loaded from -> great when you want you app to grab stuff from your development folder to avoid reloading the css all the time.

There are chrome plugins for intercepting redirects -> great when you have a openid provider set up for production but need to debug locally - then catch the openid redirect back to your localhost