VS broke project
-
Opening an existing vb.net winforms solution and out of nowhere is generating over a hundred errors, most of which are like BC30456 'Black' is not a member of 'Color, or 'SelectedIndex' is not a member of 'VisualStyleElement.ComboBox'. Normal elements. Also a smattering of some BC30311 Value of type 'TextBox' cannot be converted to 'VisualStyleElement.TextBox'. Seemingly hit and miss errors in some 10k lines of code. Updated, built, and published on Saturday with no issues. Anyone else seen anything like this?
-
Opening an existing vb.net winforms solution and out of nowhere is generating over a hundred errors, most of which are like BC30456 'Black' is not a member of 'Color, or 'SelectedIndex' is not a member of 'VisualStyleElement.ComboBox'. Normal elements. Also a smattering of some BC30311 Value of type 'TextBox' cannot be converted to 'VisualStyleElement.TextBox'. Seemingly hit and miss errors in some 10k lines of code. Updated, built, and published on Saturday with no issues. Anyone else seen anything like this?
Are you getting errors on Using statements at the top of the code files? You're probably missing a reference to a library, like System.Windows.Forms.dll.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
Are you getting errors on Using statements at the top of the code files? You're probably missing a reference to a library, like System.Windows.Forms.dll.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave KreskowiakHey Dave, You're a lifesaver :) VS had self-added (???) these to the main form: Imports MS.Internal Imports System.Windows.Forms.VisualStyles.VisualStyleElement Libraries in this haven't changed in two years, so I never thought to give this a look. Those two were responsible for all the errors. Where they came from? My only guess is that on Saturday, that computer was in 'update hell'; meaning it had downloaded an update but needed a reboot and I didn't notice it. For unrelated reasons, it runs 24/7. It took three times to get the update flag cleared, and I'm pretty sure I opened the project after the first update said it was done. I should have known better, since I know VS doesn't use the in-memory loaded libraries in update hell, but was doing a few different things on different computers so I missed it. Though in the past, I've never seen it add libraries on its own; it normally throws "missing" errors. Thanks again for the clue. Mike