Profiling Add-ins with VS.net 2003

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Valentino Kyriakides - 31 Oct 2005 12:33 GMT

I wonder if there is a recommended way of how to profile VS.net 2003
*add-ins* and which profilers might be usable for such tasks? I've searched
the net and didn't found any VS-net add-in specific articles related to this
theme.

I've took a look at the Devpartner community edition, which seems to be a
somehow much striped down profiler version (contains no memory profiler as
far as I understand) and I assume that this one is not capable to profile
VS.net add-ins at all.

In my understanding so far, the way to profile an add-in would be, to use a
profiler which is capable to start another instrumented instance of VS.net
and which allows to perform filtering, so that one can drill down to the
add-in related code portions when executing VS.net with a loaded and
performed add-in.

Any recommendations or approved ways to profile add-ins in a foolprove
manner?

Reply to this Message

Carlos J. Quintero [VB MVP] - 31 Oct 2005 14:01 GMT

While the DevPartner Community Edition can not profile DLLs, the full
version can. Also, VS 2005 Team Edition allows you to profile DLLs.

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

>I wonder if there is a recommended way of how to profile VS.net 2003
> *add-ins* and which profilers might be usable for such tasks? I've
[quoted text clipped - 17 lines]
> Any recommendations or approved ways to profile add-ins in a foolprove
> manner?

Reply to this Message

Valentino Kyriakides - 31 Oct 2005 20:09 GMT

> While the DevPartner Community Edition can not profile DLLs, the full
> version can. Also, VS 2005 Team Edition allows you to profile DLLs.

I already partly used/tried out the VS 2005/B2 Team Edition and usually like
the way it offers these profiling and testing capabilities for VS.net 2005
Team Edition.

However, for one of my add-ins, which I ported over from VS.net 2003, I
actually encountered there some problems for showing it up at all inside the
VS.2005/TE IDE. So far I was't able to get the add-in, which usually hooks
itself into the "code window" comandbar/menu, to show up correctly there,
even it was loaded correctly during the VS.net 2005 startup. Also things
like devenv.exe /setup etc. seem not to work either in my case and thus I
first have to analyze, what the cause for this behaviour might be under VS
2005, before I can successfully profile my add-in there. The previously
named issues are the reason why I'am looking to profile the add-in also
under 2003.

Well, I think I will not invest in a full version of Devpartner, since I
sooner or later will make the transition over towards the final released
version of VS.net 2005 Team Edition, which already contains mostly what I
need from a developers point of view.

Reply to this Message

Dustin Campbell - 31 Oct 2005 16:23 GMT

> Any recommendations or approved ways to profile add-ins in a foolprove
> manner?

AQTime 4 from Automated QA (www.automatedqa.com) works great for
profiling add-ins.

Signature

Best Regards,
Dustin Campbell
Developer Express, Inc

Reply to this Message

Valentino Kyriakides - 31 Oct 2005 20:17 GMT

> > Any recommendations or approved ways to profile add-ins in a foolprove
> > manner?
>
> AQTime 4 from Automated QA (www.automatedqa.com) works great for
> profiling add-ins.

Ok, thank's for the info, I'am going to give this AQtime 4.7 demo a try.

...hmm, so far when I try to use this AQtime 4.7 demo version via an user
account (not from the Admin account) it cores and throws exceptions. Seems
that demo version has some problems to find/read registry entries or the
like when used under a user account on a W2K Pro system.

Reply to this Message

Valentino Kyriakides - 31 Oct 2005 20:32 GMT

Ok thank's, I will give it a try for VS.net 2003!

--
Regards

Valentino Kyriakides

> > Any recommendations or approved ways to profile add-ins in a foolprove
> > manner?
>
> AQTime 4 from Automated QA (www.automatedqa.com) works great for
> profiling add-ins.

Reply to this Message

Profiling Add-ins with VS.net 2003

Free Magazines