I hope someone can help me though as i am a bit stuck :-(.
I need to be able to debug a class inherited from WorkflowType and would like some tips on the best way to do this ... i have the impression i need to run the whole of umbraco from visual studio? If this is the case then my heart goes out to the developers of Contour who either got it right first time or spent a *long* time waiting for breakpoints to be hit...
For anyone who hasn't got enough time to wait for another non existent response, you should look into remote debugging, specifically using 'msvsmon.exe' (installed with vs ... share the 'msvsmon.exe' parent folder over your network then you can run it on your server from the '//vs install pc' ... no further config necessary).
There are permissions that need to be set in 'msvsmon.exe' to allow non administrators debug priviledges.
You need to copy your compiled workflow .dll and .pdb into the bin folder of your website. You should be able to set some break points and then connect to the 'msvsmon.exe' instance from your version of VS (debug > attach to process).
Obviously, firewalls are probably not going to be you best friends whilst you get it working.
Also, if you have multiple app pools, there is no information in 'attach to process' that allows you to see which worker process (w3wp.exe for .NET 4) is running which app pool. You can get around this by creating a separate user to run your 'debug' umbraco install app pool ... the user name appears in the 'attach to process window'. You can also use this technique, which takes longer!.. http://abhijitjana.net/2010/07/15/identifying-worker-process-w3wp-exe-iis-6-0-and-iis-7-0-for-debugging-asp-net-application/.
Best way to debug derived WorkflowType class?!
Hi,
Contour = Excellent!
I hope someone can help me though as i am a bit stuck :-(.
I need to be able to debug a class inherited from WorkflowType and would like some tips on the best way to do this ... i have the impression i need to run the whole of umbraco from visual studio? If this is the case then my heart goes out to the developers of Contour who either got it right first time or spent a *long* time waiting for breakpoints to be hit...
All tips will be most greatfully received,
James.
Again,
Thanks for all the help :-p.
For anyone who hasn't got enough time to wait for another non existent response, you should look into remote debugging, specifically using 'msvsmon.exe' (installed with vs ... share the 'msvsmon.exe' parent folder over your network then you can run it on your server from the '//vs install pc' ... no further config necessary).
There are permissions that need to be set in 'msvsmon.exe' to allow non administrators debug priviledges.
You need to copy your compiled workflow .dll and .pdb into the bin folder of your website. You should be able to set some break points and then connect to the 'msvsmon.exe' instance from your version of VS (debug > attach to process).
Obviously, firewalls are probably not going to be you best friends whilst you get it working.
Also, if you have multiple app pools, there is no information in 'attach to process' that allows you to see which worker process (w3wp.exe for .NET 4) is running which app pool. You can get around this by creating a separate user to run your 'debug' umbraco install app pool ... the user name appears in the 'attach to process window'. You can also use this technique, which takes longer!.. http://abhijitjana.net/2010/07/15/identifying-worker-process-w3wp-exe-iis-6-0-and-iis-7-0-for-debugging-asp-net-application/.
Good luck.
is working on a reply...