Hi all! I'm struggling with not being able to step through or even hit any break points in a custom ASR. I have reviewed the couple of discussions on here as well as the KB article on debugging appserver rules, and still can't debug.
Here is what I've done/verified so far:
Built and imported+registered my ASR assembly using LCS Customization Assistant, set the "disable app server rule synchronization" check box in it while I was at it, then:
1. Changed identity of the Pivotal LifeCycle AppServer in Component Services to "Interactive User"
2. Set up the project to build into the ePower\{System Name}\Assemblies folder, enabled the other debugging options in the project properties (Enable ASP debugging, enable ASP.Net debugging)
3. Set the debugging mode to Program - > start application C:\WINDOWS\system32\dllhst3g.exe and command line arguments: /ProcessID:{20248358-4A67-4FAC-B298-23CC94BC44EE} <-- this is the GUID of my Lifecycle Engine AppServer component in Component Services.
When I hit "debug" button in VS, it builds successfully and shows as attached to a process. Also, I am able to attach to the similar processes in the Debug->Processes list that show dllhst3g.exe and "T-SQL" in the type column. I've been hunting for the highest process ID in hopes of getting the "right" one.
In summary, I am able to interact with the business rule, and for instance I am able to make a change to stub away or re-enable a particular method, so I know the code runs and makes it into the system during deployment. BUT Visual Studio debugger does not hit any break-points.
I've lost a ton of hours and desperately need HELP! Please and thank you!

My environment:
- Server 2003 R2 32bit with 6GB+PAE
- Working remotely via RDP (Could this be my problem? I notice if there's a console-logon session, the lifecycle dllhst3g.exe processes spawn under _that_ session, not mine!)
- VS 2003
- The ASR project is referencing the Pivotal assemblies for 5.7 and .Net 1.1 references