Debugging Design-Time-Code

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sparhawk - 21 Jun 2005 08:35 GMT

Hi,

simple question: is there any way to debug design-time-code except with
MessageBoxes? If I develop, for example, a TypeConverter it is never
used at run-time. Any way to debug this?

Reply to this Message

Bob Powell [MVP] - 21 Jun 2005 19:04 GMT

See Windows Forms Tips and Tricks

Signature

Bob Powell [MVP]
Visual C#, System.Drawing

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

> Hi,
>
> simple question: is there any way to debug design-time-code except with
> MessageBoxes? If I develop, for example, a TypeConverter it is never
> used at run-time. Any way to debug this?

Reply to this Message

azerty - 21 Jun 2005 21:40 GMT

It is very easy

You need to use Devenv.Exe for application host of your assembly

(in C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE)

and you need to define the output file of your assembly in good place like

C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\IDE\PrivateAssemblies

The first instance of Visual Studio must never open this assembly, so you
did not have to open the final solution with this instance of VS

The first instance open the solution with Design assembly and the second
open a simple solution with form to test your component.

NB : you collect a lot information with this approach, for exemple, you
collect the entire call stack when you have an exception, with Reflector,
you can understand how VS work ...

> Hi,
>
> simple question: is there any way to debug design-time-code except with
> MessageBoxes? If I develop, for example, a TypeConverter it is never
> used at run-time. Any way to debug this?

Reply to this Message

Bob Powell [MVP] - 22 Jun 2005 15:30 GMT

> and you need to define the output file of your assembly in good place like
>
> C:\Program Files\Microsoft Visual Studio .NET
> 2003\Common7\IDE\PrivateAssemblies

Most of what you say is good but the snippet above isn't very sound advice.

Signature

> It is very easy
>
[quoted text clipped - 22 lines]
>> MessageBoxes? If I develop, for example, a TypeConverter it is never
>> used at run-time. Any way to debug this?

Reply to this Message

azerty - 27 Jun 2005 21:26 GMT

I agree with you

It is just a simple way

in fact, I did not very well understand of Visual studio find its assembly
but if I put my assembly in privateAssemblies, It seems work fine !

> > and you need to define the output file of your assembly in good place like
> >
[quoted text clipped - 29 lines]
> >> MessageBoxes? If I develop, for example, a TypeConverter it is never
> >> used at run-time. Any way to debug this?

Reply to this Message

Bob Powell [MVP] - 28 Jun 2005 08:16 GMT

You can add a path to the registry that enables VS to find your assemblies.

Use
HKEY_LOCAL_MACHINE/Software/Microsoft/VisualStudio/7.1/AssemblyFolders/<your
own subkey> should contain a default entry with the path of the folder that
you'd like to include in the reference searches.

Signature

Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

>I agree with you
>
[quoted text clipped - 43 lines]
>> >> MessageBoxes? If I develop, for example, a TypeConverter it is never
>> >> used at run-time. Any way to debug this?

Reply to this Message

Debugging Design-Time-Code

Free Magazines