Hans Karlsen (talk | contribs) (Created page with "The different scenarios for debugging Turnkey # You have the MDrivenServer stable and you want to step through Turnkey-generic code # You have the MDrivenServer stable and you...") |
Hans Karlsen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
The different scenarios for debugging Turnkey | The different scenarios for debugging Turnkey generic code | ||
# You have the MDrivenServer stable and you want to step through Turnkey-generic code | # You have the MDrivenServer stable and you want to step through Turnkey-generic code | ||
# You have the MDrivenServer stable and you want to step through Turnkey-generic code but also the CodeDress code from the model | # You have the MDrivenServer stable and you want to step through Turnkey-generic code but also the CodeDress code from the model | ||
| Line 10: | Line 10: | ||
Case 3: You want to debug towards local prototyping xml based persistence - cutting MDrivenServer out of the equation. Use MDrivenServerOverride.xml with setting: | Case 3: You want to debug towards local prototyping xml based persistence - cutting MDrivenServer out of the equation. Use MDrivenServerOverride.xml with setting: | ||
<MDrivenServerOverride '''PrototypeWithMDrivenDesignerInPath'''="C:\PathToLocalModel modlr or ecomdl"></MDrivenServerOverride> | <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. | |||
Revision as of 10:32, 6 August 2018
The different scenarios for debugging Turnkey generic code
- You have the MDrivenServer stable and you want to step through Turnkey-generic code
- You have the MDrivenServer stable and you want to step through Turnkey-generic code but also the CodeDress code from the model
- 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. 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.