MaximumASP
Packet Sniffer


Crash and Burn in the VS.NET Solution Explorer

Posted by: Rick Strahls WebLog, on 30 May 2006 | View original

So, I'm hammering away in Visual Studio for the last two days working on a number of projects. Everything is fine. I'm running apps, modifying projects and solutions… Several instances of VS has been running for quite some time chugging along.   About an hour ago I did some major reworking of a fairly big project. I renamed a number of projects and ran some hairy refactoring on some of the code that renames a few widely used control classes and properties on those classes. The final step...

Advertisement
Category: #Visual Studio | 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

  • Run Cassini as Root Web within Visual Studio more
  • Annoying Visual Studio Add Existing Project Behavior Solved more
  • Extending Visual Studio, and open source more
  • Netgear SC101 Storage Central more
  • Building your own VS2005-compatible NUnit distribution more
  • Open Source and Visual Studio more
  • Retrieving a CodeElement reliably in VS.NET 2005 more
  • Interesting bug in Saxon.NET/Mono/OSX usage more
  • Wondering where the latest build is more
  • How do I work around "Empty choice is unsatisfiable if minOccurs not equal to 0. An error occured at file://[some path to XSD]" 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