The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I used to, but I am now moving fully into C#. I started out with VB, and always compiled with Option Strict On, and tried to never use the 'Shared Instance Methods' thing VB has. I always used either a singleton form or the My.Forms namespace.
Visual Studio 2012 tries to run code after importing it from another project
This is a general problem with Visual Studio, especially with WPF projects. I have it regularly with Visual Studio 2008. The XAML designer routinely fails when supporting classes don't compile cleanly, as is typically the case when you're refactoring. They rely on the runtime to do the heavy lifting while you're editing.
It's almost like a return to the days of the Ada development environments, where you had to implement from the bottom up because the compiler failed otherwise.
Sucks. Yes it is useful, but WHY ON EARTH did they put WinForms and WPF stuff in the same assembly?!??! Some applications would never use the WPF stuff, and trying to take it out is a lost battle, as the WinForms related stuff uses the WPF related stuff, and vice-versa. This just adds useless references to projects, and causes a lot of headaches.
You would think Microsoft would be smart enough to....... ummmm, never mind.
The Windows API Code Pack has WinForms and WPF stuff in the same assembly, requiring a WinForms application to reference the WindowsBase, PresentationFramework, etc libraries, even if they are not used by the application using the Windows API Code Pack!