|
|
You're in the
dotnet windows forms designtime
group:Debugging Design-Time-Code
dotnet windows forms designtime:
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?
See Windows Forms Tips and Tricks
-- 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. [quoted text, click to view] "Sparhawk" <Kay.Eckernkamp@gmx.de> wrote in message news:1119339307.541263.197080@g49g2000cwa.googlegroups.com... > 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? >
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 ... "Sparhawk" <Kay.Eckernkamp@gmx.de> a écrit dans le message de news:1119339307.541263.197080@g49g2000cwa.googlegroups.com... [quoted text, click to view] > 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? >
[quoted text, click to view]
> 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. -- 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. [quoted text, click to view] "azerty" <azerty@aaaa.fr> wrote in message news:%23alMlFqdFHA.3032@TK2MSFTNGP10.phx.gbl... > 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 ... > > > > "Sparhawk" <Kay.Eckernkamp@gmx.de> a écrit dans le message de > news:1119339307.541263.197080@g49g2000cwa.googlegroups.com... >> 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? >> > >
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 ! "Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> a écrit dans le message de news:umuJ3azdFHA.616@TK2MSFTNGP12.phx.gbl... [quoted text, click to view] > > 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. > > -- > 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. > > > > > > "azerty" <azerty@aaaa.fr> wrote in message > news:%23alMlFqdFHA.3032@TK2MSFTNGP10.phx.gbl... > > 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 ... > > > > > > > > "Sparhawk" <Kay.Eckernkamp@gmx.de> a écrit dans le message de > > news:1119339307.541263.197080@g49g2000cwa.googlegroups.com... > >> 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? > >> > > > > > >
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. -- 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. [quoted text, click to view] "azerty" <azerty@aaaa.fr> wrote in message news:eFgXxZ1eFHA.580@TK2MSFTNGP15.phx.gbl... >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 ! > > > > "Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> a écrit dans le message > de news:umuJ3azdFHA.616@TK2MSFTNGP12.phx.gbl... >> > 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. >> >> -- >> 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. >> >> >> >> >> >> "azerty" <azerty@aaaa.fr> wrote in message >> news:%23alMlFqdFHA.3032@TK2MSFTNGP10.phx.gbl... >> > 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 ... >> > >> > >> > >> > "Sparhawk" <Kay.Eckernkamp@gmx.de> a écrit dans le message de >> > news:1119339307.541263.197080@g49g2000cwa.googlegroups.com... >> >> 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? >> >> >> > >> > >> >> > >
Don't see what you're looking for? Try a search.
|
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
February 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |