Documentation:Turnkey debug

The different scenarios for debugging Turnkey generic code

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

Case 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>

Case 2: MDrivenServer stable and you want to step through Turnkey-generic code but also the CodeDress code from the model. 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>

Case 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.