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?
-
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?
Installed it last weekend, not sure I even want to fire it up based on the early feedback. I want to use it for the Xamarin integration but 99% of my work is in WPF **shudder**
Never underestimate the power of human stupidity RAH
-
Installed it last weekend, not sure I even want to fire it up based on the early feedback. I want to use it for the Xamarin integration but 99% of my work is in WPF **shudder**
Never underestimate the power of human stupidity RAH
I still use 2010
If it's not broken, fix it until it is
-
Installed it last weekend, not sure I even want to fire it up based on the early feedback. I want to use it for the Xamarin integration but 99% of my work is in WPF **shudder**
Never underestimate the power of human stupidity RAH
I'm just using it on my personal side project, so I probably use it maybe 3 hrs a week tops. If I had to use it 8 hrs a day for my work (especially if it was 99% WPF), I'd be hatin'... From one WPF guy to another, I would not use this in a professional environment right now. Too buggy still. I do like the runtime "Spy++" type tool that can hyperlink to the element in the XAML... kind of cool, but also kind of kludge to use with the weird focus behavior. Switching properties at runtime? I guess if you're debugging something that's hard to repro... I would call VS2013 "rock solid"... if that is the basis for a "10", I'd give this a 2 or 3 in the **WPF areas**.
-
I still use 2010
If it's not broken, fix it until it is
Luddite :laugh:
Never underestimate the power of human stupidity RAH
-
I'm just using it on my personal side project, so I probably use it maybe 3 hrs a week tops. If I had to use it 8 hrs a day for my work (especially if it was 99% WPF), I'd be hatin'... From one WPF guy to another, I would not use this in a professional environment right now. Too buggy still. I do like the runtime "Spy++" type tool that can hyperlink to the element in the XAML... kind of cool, but also kind of kludge to use with the weird focus behavior. Switching properties at runtime? I guess if you're debugging something that's hard to repro... I would call VS2013 "rock solid"... if that is the basis for a "10", I'd give this a 2 or 3 in the **WPF areas**.
SledgeHammer01 wrote:
I would not use this in a professional environment right now
That is certainly not going to happen, EVERY tool goes through evaluation before it is allowed into the selected product list and they have no sense of urgency on any product.
Never underestimate the power of human stupidity RAH
-
Luddite :laugh:
Never underestimate the power of human stupidity RAH
It works well and doesn't look like MS DOS 3.1
If it's not broken, fix it until it is
-
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?
So how do you feel about this guy[^] now? :laugh:
GeoGame for Windows Phone | The Longue Explained In 5 Minutes
-
I still use 2010
If it's not broken, fix it until it is
I will keep using Windows 7, Office 2010, and VS2010 until Microsoft makes something better, but I am beginning to think that I will have to wait quite a long time... :(
-
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?
-
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
-
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.
I was looking forward to the support for C++11 in the C++ compiler. Given that it is developed by a different team, I hope that it's better than the C#/WPF stuff.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
-
So how do you feel about this guy[^] now? :laugh:
GeoGame for Windows Phone | The Longue Explained In 5 Minutes
-
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 common difference between, lets say, Visual Studio 2013 and Visual Studio 2015 is new language and frameworks support. C# 6, ASP.NET 5, ASP.NET MVC 6 etc are the new things added to Visual Studio. I am not sure what happened to WPF, I am also a fan of WPF but I also use Visual Studio 2013 until now. :laugh: The only thing that I love of Visual Studio 2015, is the debugger and debugging tools. Provides a great set of tools and resources for working while debugging. :-) Hey, if designing is your major field, why don't you try Blend? Creating a UI by using Blend for Visual Studio[^] :-)
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
-
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.
