Why Visual Studio 2012 sucks today
-
It's been a while since I've noticed one of these, so, since VS Express 2012 is acting up on me this afternoon, I thought why not? What the heck is with the IDE suddenly deciding that certain items in a resource dictionary in my App.xaml file don't exist, even though it hasn't been changed and the items it is complaining about haven't been exchanged (and most certainly do exist)? Nothing like that to foul up my afternoon plans. Please note that this is not a programming question, since my app builds, deploys, and runs just fine. Actually, it's only a rhetorical question anyway since I don't truly expect an answer (other than the standard funny ones provided in the Lounge). All right, rant over, desire to punch display fading, so it's time to get back to it. :)
-
It's been a while since I've noticed one of these, so, since VS Express 2012 is acting up on me this afternoon, I thought why not? What the heck is with the IDE suddenly deciding that certain items in a resource dictionary in my App.xaml file don't exist, even though it hasn't been changed and the items it is complaining about haven't been exchanged (and most certainly do exist)? Nothing like that to foul up my afternoon plans. Please note that this is not a programming question, since my app builds, deploys, and runs just fine. Actually, it's only a rhetorical question anyway since I don't truly expect an answer (other than the standard funny ones provided in the Lounge). All right, rant over, desire to punch display fading, so it's time to get back to it. :)
The other day, Visual Studio decided an extension method I wrote didn't exist. Then I compiled a few times and then it decided it did exist. Just Visual Studio's wonky build engine acting up, I suppose.
-
The other day, Visual Studio decided an extension method I wrote didn't exist. Then I compiled a few times and then it decided it did exist. Just Visual Studio's wonky build engine acting up, I suppose.
I suppose so. Fortunately I'm basically done with page design or I'd be seriously hurting since the breakage seems to have killed off the property pages for all of my XAML work. All this because it's decided that three value converters I have in the project aren't really there. :rolleyes: I'm glad I'm not the only one who's seen this.
-
It's been a while since I've noticed one of these, so, since VS Express 2012 is acting up on me this afternoon, I thought why not? What the heck is with the IDE suddenly deciding that certain items in a resource dictionary in my App.xaml file don't exist, even though it hasn't been changed and the items it is complaining about haven't been exchanged (and most certainly do exist)? Nothing like that to foul up my afternoon plans. Please note that this is not a programming question, since my app builds, deploys, and runs just fine. Actually, it's only a rhetorical question anyway since I don't truly expect an answer (other than the standard funny ones provided in the Lounge). All right, rant over, desire to punch display fading, so it's time to get back to it. :)
If you used class names like "Exploder", it's possible they were confiscated by the security forces.
I wanna be a eunuchs developer! Pass me a bread knife!
-
If you used class names like "Exploder", it's possible they were confiscated by the security forces.
I wanna be a eunuchs developer! Pass me a bread knife!
Hmm, maybe because the word "Grams" is part of the name, the NSA passed it along to the DEA and they broke it. :-D