Custom Task Performers Debugging in Visual Studio

Posts   
 
    
basik
User
Posts: 123
Joined: 20-Aug-2012
# Posted on: 23-Jul-2014 12:16:11   

Using LLBGen Pro 4.2 - how do you get Visual Studio to repeatedly debug custom task performers?

I've read the SDK documentation: http://www.llblgen.com/documentation/4.1/SDK/hh_start.htm

I know that the project is loading the assembly because it does run the task performer custom actions as I have coded them. Also if I put a Debugger.Break line in the Perform method it does ask me to debug. But this is not ideal as it causes the designer to hang once it completes the debugging.

Attached is a view of our custom TaskPerformer project. The project references are to the LLBLGen Pro assemblies as installed in c:\program files

This is what I have tried: 1. Build the TaskPerformer project 2. Attach to Process in Visual Studio and select LLBLGen Pro 4.2 from the list 3. Then open a project where the Additional task performer folder is set to the bin\debug folder of the project built in step 1 4. Run the source generator

I've tried cleaning the project, deleting obj folders and ensuring that Debug configuration is set for the task performer project.

Any help would be greatly appreciated.

basik
User
Posts: 123
Joined: 20-Aug-2012
# Posted on: 23-Jul-2014 12:50:43   

Resolved it!

Attached is the setting in Visual Studio that was needed.

On the Attach to Process Dialog: It seems that Visual Studio is not able to** Automatically determine the type of code to debug** and by changing it to specifically debug Managed (v4.5,v4.0) code it hits the break points as expected.

Maybe the SDK documentation could be updated to include such tips as I certainly have spent way too much time getting this to work.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 23-Jul-2014 13:34:47   

(removed the pdf's as it's not a safe format. Please attach docs in other formats, e.g. .txt. If it just contains a picture, attach that instead)

I must say I never had any problems debugging task performers. You could also do the following: in the startup setting for the task performer vs.net project properties, select the llblgen pro exe and specify also the working folder to be the llblgen pro installation folder. Pressing F5 in your task performer project then will launch the designer with the debugger already attached. A post build step could be added too to automatically copy the task performer dll to the place you want it to be for easy loading at startup. (the llblgen pro .exe process also accepts a llblgenproj parameter so you can specify a project to load at startup, so things are easy to automate)

Frans Bouma | Lead developer LLBLGen Pro
basik
User
Posts: 123
Joined: 20-Aug-2012
# Posted on: 23-Jul-2014 16:27:01   

Thank you. Debugging works fine now.