Documentation:Debug CodeDress

Set up the IIS and install the Turnkey application. You can use the following articles to get help with the installation of IIS and MDrivenTurnkey locally on your machine: Development in Visual Studio, Installing MDriven Server on Windows.

Scenario 1: Debug Turnkey CodeDress with data from cloud MDriven Server

Set up your your local turnkey app by copying the template files (green) and rename them to be active(yellow):

In the MDrivenServerOverride.xml point out the MDrivenServer you want to run towards and its password:

Verify that is starts, and that it fetch data from the given MDriven Server:

Make sure your Apppool user has full access to Log catalog and to ModelCodeAssemblies (easiest way give full control to everyone on these):

As the Turnkey App started it got the zip containing the model and the CodeDress assemblies (your code) from the MDrivenServer.

This fetch is done on start – if you want to restart to fetch to do it again – best way is to kill the w3wp process and refresh turnkey browser:

But maybe the ModelCodeAssemblies are skipped due to Turnkey finding nothing new – you can see this in the log:

To force it – delete the wwwroot\test88\App_Data\AssetsTKChecksum.xml file, and restart.

When successful CodeDress has been performed you should see something like this in the log:

Now you are ready to debug – Start VS and your project holding the model with CodeDress.

Make sure you codegen, then build then upload the current version of the model (build first to ensure you have the correct assemblies available to upload).

Restart your turnkey app (kill w3wp process and refresh browser app-page to force it to start)

In VS do Debug/AttachToProcess – Select managed .NET4 code, Check the Show processes from all users – attach w3wp (the one corresponding to your apppool):

You must be admin and you will get warned:

When your web UI calls your model code your breakpoints will be hit: