Wow, VS2015 is *HORRIBLE*
-
I do C# and WPF work. I don't know what they did to the XAML parser in VS2015, but it flat out stinks. It blue squiggles pretty much everything intermittently, gives random / incorrect errors intermittently, etc. There are a few other nitpicks in the general environment, but this is pretty much unusable. Very disappointed. Any other WPF people seeing the same thing?
You know - WPF is dead! So why support it?!
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
I still use 2010
If it's not broken, fix it until it is
I converted to VS 2013 recently(from 2010). It is well worth the upgrade.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
What has changed (major changes) between VS2012 and VS2015 which will force anyone to move to it? I am not talking about release notes but from a regular user point of view.
From my point of view, the integrated XAML debugging was something that was badly missing in earlier VS editions - I raised the original Connect request for this as a vNext feature back in 2008. Given how horrible and slow the 2015 experience is, I will continue to wait to use this feature.
-
It works well and doesn't look like MS DOS 3.1
If it's not broken, fix it until it is
If you like VS 2010 then 2013 is fine with the blue theme. I hated the default grey. But now I love VS 2013. I've installed VS 2015 but not really used it yet besides running a Hello World console app. I always do that as a sanity check after an install.
Kevin
-
I converted to VS 2013 recently(from 2010). It is well worth the upgrade.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
Ditto.
Kevin
-
I do C# and WPF work. I don't know what they did to the XAML parser in VS2015, but it flat out stinks. It blue squiggles pretty much everything intermittently, gives random / incorrect errors intermittently, etc. There are a few other nitpicks in the general environment, but this is pretty much unusable. Very disappointed. Any other WPF people seeing the same thing?
The Fix: buy the next ridiculously priced machine with the new super duper CPU and (also new super duper) bus which requires unobtainable memory.
-
I still use 2010
If it's not broken, fix it until it is
-
Kevin Marois wrote:
I still use 2010
I developed my final year project in VS2010, it really works well. Using VS2012 these days on work place, VS12 too is cool Ain't intend to use VS2015 in future
Brittle1618 wrote:
Ain't intend
I don't intend... Sorry, but that was bad. ;)
-
Brittle1618 wrote:
Ain't intend
I don't intend... Sorry, but that was bad. ;)
Oh thats perfectly alright thanks for correction :)
-
I do C# and WPF work. I don't know what they did to the XAML parser in VS2015, but it flat out stinks. It blue squiggles pretty much everything intermittently, gives random / incorrect errors intermittently, etc. There are a few other nitpicks in the general environment, but this is pretty much unusable. Very disappointed. Any other WPF people seeing the same thing?
You aren't by chance using Resharper are you? I had a similar experience once I turned off Resharper all was fine. I think the latest version of Resharper has eliminated the issues. Brad
Brad
-
So how do you feel about this guy[^] now? :laugh:
GeoGame for Windows Phone | The Longue Explained In 5 Minutes
That he is still batshit crazy.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
