Memi.Reflection

Private members of memi's thoughts

Beware of DevPartner Community Edition

Roy posted about a free edition of the DevPartner Profiler.

I've downloaded and installed it, and the gates of hell were opened. Looks like the tool installs the .NET v1.0 (!) automatically, without checking what there is already on the machine (I had v1.1 & whidbey). Since then, the VS.NET just gone creazy. I can't debug any web application anymore, and I start debugging, I get the following message:

“Unable to start debugging on the web server. There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running in the process before attaching.”

There is almost no docs about this error message in the web.

what I tried to do until now is:

- Uninstall the DevPartner

- Repair the VS.NET installation

- Reinstall the .NET Framework

- Remove / Create the root application of the IIS

But nothing helps. Of course I tried to attach the process manually after starting with CTRL+F5, but that didn't help either.

THIS DRIVING ME NUTS!

If you know about this message and how to overcome it, please drop me a line. And if someone from Compuware is reading this - please improve your installation process. I found some posts in the internet of other guys who encountered the same problem with your product, but no one found a solution yet.

Posted: May 10 2004, 09:37 AM by memi | with 8 comment(s)
Filed under:

Comments

TrackBack said:

# May 10, 2004 2:57 AM

dev said:

When I registered and installed this last year (there was an ad for it in the VS.NET 2003 update package I bought), I started recieving (unanswered) phonecalls from the company within 24 hours. I think the last one I got from them was about a month ago. I never got around to installing so I never bothered returning their phone calls.

Hopefully you'll get the same harassment and will be able to ask them personally about hte problem.
# May 10, 2004 3:52 AM

Wim said:

Check your IIS mappings. All your sites are now likely to be mapped to the ASP.NET 1.0 version of ASPNET_ISAPI.DLL.

When running VS.NET 2003 the debugger expects version 1.1 of the ASP.NET ISAPI, but since your website maps to version 1.0, you can't debug it...

Try remapping your websites to 1.1 and you should be OK.

Cheers,
Wim
# May 10, 2004 5:39 AM

Ido Samuelson said:

How about trying to run the aspnet_regiis.exe
# May 10, 2004 7:26 AM

Memi Lavi said:

Thanks for the info, but I've already checked the IIS mappings.
# May 10, 2004 7:36 AM

Kyle Heon said:

Yes, I too received numerous phone calls once I downloaded tha app. That is always fun. I would also recommend trying aspnet_regiis because that has solved issues for me in the past that made little to no sense at all.
# May 10, 2004 11:48 AM

Mike said:

I used aspnet_regiis.exe to remove all versions of ASP.NET and then installed the 1.1 version and all worked fine.
# May 20, 2004 1:01 PM

Nat said:

check http://blogs.msdn.com/mkpark/articles/86872.aspx whether it helps
# May 21, 2004 3:50 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)