MaximumASP
Packet Sniffer
Home Loan
conference calling services


VS.NET 2005 Debugger chokes on COM/.NET Interop Debugging

Posted by: Rick Strahls WebLog, on 26 Oct 2005 | View original

Aargh…   I’m spending some time today adding .NET 2.0 features to Help Builder’s type import routines. For the most part I expected this to go real smoothly but as it turns out a lot more work than I anticipated, no thanks to VS.NET which is getting in the way...   It looks like VS.NET 2005 RC does not want to debug COM objects properly. I have the debugger set up properly to debug into some specific code that does type parsing and a few breakpoints set. The debugger...

Advertisement
The leading UI suite for ASP.NET - Telerik radControls
Outstanding performance. Full ASP.NET AJAX support. Nearly codeless development.
Category: #Regex | Other Posts: View all posts by this blogger | Login to add this post to your profile favorites Report as irrelevant | View bloggers stats

Similar Posts

  • Add-in Comparison: VSFileFinder 2005 vs. SonicFileFinder more
  • No Fluff Just Stuff panel discussion - level 100 more
  • Functional Programming via Anonymous Delegates and Script# more
  • Introducing CaptainHook - A Subversion Hook Framework For .NET more
  • Web Service Proxy Objects and COM Interop Problems more
  • Throughput and Latency Considerations more
  • Adding CoComment support to Community Server 2.1 more
  • Why no CAPTCHA? more
  • CS Dev Guide: User manipulation more
  • On Microsoft Not Joining the OpenDocument Format (ODF) Committee more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD