If you have less than 1GB of RAM in your machine, I highly suggest upgrading. The difference in performance of VS from 512MB to 1GB is significant.
-------------------- "All left-wing parties in the highly industrialised countries are at bottom a sham" - George Orwell "Rudyard Kipling" (1942) > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Sebastian Good > Sent: Tuesday, March 14, 2006 6:58 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] Debugging IE Hosted WinForms > Controls... > > I always debug this way. Visual Studio is so slow when you > launch the application from within it. I always run it alone > (either in IIS or the pocket server that comes with VS2005) > and then manually attach when I need to debug something. It > saves oodles of time. I often end up attaching to aspnet_wp > and ieexec.exe at the same time. In fact, it's the damndest > thing... if you "step into" a web service call and the server > for that service is on your machine, VS will in fact > automatically attach to IIS. No idea how it figures that out. > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Shawn Wildermuth > Sent: Tuesday, March 14, 2006 6:44 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] Debugging IE Hosted WinForms > Controls... > > > But then I can't debug ASP.NET code because I will have to > "Run" not "Start" > the ASP.NET project to get IExplorer running. If I try to > attach to it after starting the site, IEXPLORE is already > attached to, but not debugging into my process. > > > Thanks, > > Shawn Wildermuth > http://adoguy.com > C# MVP, MCSD.NET, Author and Speaker > > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Sebastian Good > Sent: Tuesday, March 14, 2006 7:19 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] Debugging IE Hosted WinForms > Controls... > > You can attach directly to IEXPLORE or IEEXEC and set > breakpoints that way. > (You'll have to attach manually) Or you can put an explicit > System.Diagnostics.Debug.Debugger.Break() (or something like > that) -- that works great. > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Shawn Wildermuth > Sent: Tuesday, March 14, 2006 6:04 PM > To: [email protected] > Subject: [ADVANCED-DOTNET] Debugging IE Hosted WinForms Controls... > > > I have some WinForms controls hosted in IE. They are > successfully launching (so I am *not* debugging normal > startup behavior with too few permissions) the controls in > IE. I also have an ASP.NET 2.0 project in the same solution. > > > What I want is to be able to launch the ASP.NET 2.0 project > and if my WinForm control is launched, I want to be able to > set breakpoints in it. > Anyone figure this out? I've googled until my fingers bled. > > Thanks, > > Shawn Wildermuth > <blocked::http://adoguy.com/> http://adoguy.com C# MVP, > MCSD.NET, Author and Speaker > > > > =================================== > This list is hosted by DevelopMentorR http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor. http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentorR http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor. http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
