Piece of @$#(*&!^ VS2015...
-
Sander Rossel wrote:
Notepad++
Completely off topic, at the risk of hijacking a thread here, I tried this application once on the box I'm using to type this now, way back when ... and I recall the "copy/cut/paste" in-kind hijacked the clipboard functionality of numerous other apps that I ran side-by-side. Confirm? (oops) Confirm?
Never had troubles with cut/copy/paste and Notepad++...
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Usually I'd agree, but 2010 is a little too tried and true. I've worked with 2010 for five years and I love it, but I'm missing out on a lot of stuff that I'm using in 2013 (CE, privately). I expected some issues with 2015, but not a constant crashing while typing plain old HTML (currently even Notepad does it better than VS2015!)... I mean, this stuff was tested, right...?
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
Sander Rossel wrote:
I mean, this stuff was tested, right...?
:laugh: Good one! I'd only take a newer IDE IF there are things that I'm missing that I need, otherwise, it's just not worth dealing with other people's bugs. Let someone else find them.
-
Yes! One generation behind, always... that is safe. I don't waste time (money) debugging their stuff. I let the early adopters do that for me. I'd rather finish my project and go home on time.
:laugh: yep... I have enough work, I don't need to make more for myself
-
Sander Rossel wrote:
Notepad++
Completely off topic, at the risk of hijacking a thread here, I tried this application once on the box I'm using to type this now, way back when ... and I recall the "copy/cut/paste" in-kind hijacked the clipboard functionality of numerous other apps that I ran side-by-side. Confirm? (oops) Confirm?
I'm using it now... no issues with that.
-
So I started a new project at work. We're still running on VS2010, but we were planning to upgrade with VS2015. Just my luck that my project started pretty much on the release date of VS2015. I was given a choice, go with all the new tech in VS2015 or stay in the jurassic 2010. I choose 2015. Piece of crap crashes randomly when typing some HTML and Knockout (in a Razor file). I now find myself copy-pasting code to Notepad++, making my changes and copy-pasting it back into VS2015 :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Usually I'd agree, but 2010 is a little too tried and true. I've worked with 2010 for five years and I love it, but I'm missing out on a lot of stuff that I'm using in 2013 (CE, privately). I expected some issues with 2015, but not a constant crashing while typing plain old HTML (currently even Notepad does it better than VS2015!)... I mean, this stuff was tested, right...?
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
Sander Rossel wrote:
I mean, this stuff was tested, right
WTF do you think YOU are doing, haven't you reported the bug(s) yet, tcha you can't get good help these days!
Never underestimate the power of human stupidity RAH
-
I was thinking of VS2015, but decided to postpone the upgrade till the dust settles. Currently using VS2013 for both win/web dev and pretty much satisfied by its overall performance/features.
Life is 2short 2remove USB safely
Yeah, I wouldn't trade 2013 for 2015.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Yeah, I wouldn't trade 2013 for 2015.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Usually I'd agree, but 2010 is a little too tried and true. I've worked with 2010 for five years and I love it, but I'm missing out on a lot of stuff that I'm using in 2013 (CE, privately). I expected some issues with 2015, but not a constant crashing while typing plain old HTML (currently even Notepad does it better than VS2015!)... I mean, this stuff was tested, right...?
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
Sander Rossel wrote:
I mean, this stuff was tested, right...?
By 'tested', if you mean 'Works on My Machine', then, yes, it was 'tested'. ;)
I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone - Bjarne Stroustrup The world is going to laugh at you anyway, might as well crack the 1st joke! My code has no bugs, it runs exactly as it was written.
-
So I started a new project at work. We're still running on VS2010, but we were planning to upgrade with VS2015. Just my luck that my project started pretty much on the release date of VS2015. I was given a choice, go with all the new tech in VS2015 or stay in the jurassic 2010. I choose 2015. Piece of crap crashes randomly when typing some HTML and Knockout (in a Razor file). I now find myself copy-pasting code to Notepad++, making my changes and copy-pasting it back into VS2015 :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Yeah, 2013 is great. I use the Community Edition for private stuff. Unfortunately that wasn't an option at work, so I got to pick 2010 or 2015. 2010 was a bit to old for my taste. Been using it for five years and I love it, but I'm missing out on good stuff that's in 2013. So I decided to go for 2015, but I didn't expect it to fail as even a simple HTML editor...
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
So I started a new project at work. We're still running on VS2010, but we were planning to upgrade with VS2015. Just my luck that my project started pretty much on the release date of VS2015. I was given a choice, go with all the new tech in VS2015 or stay in the jurassic 2010. I choose 2015. Piece of crap crashes randomly when typing some HTML and Knockout (in a Razor file). I now find myself copy-pasting code to Notepad++, making my changes and copy-pasting it back into VS2015 :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
No surprises here. When was the last time they released something that wasn't a train wreck? I just installed windows 10 only to find out LiveMail is a flaming bag of *@#! too. Microsoft's sun is setting...they will soon be as irrelevant to software as IBM is to hardware. Bummer too (I based a career around these kids) :((
Jephre
-
Yes! One generation behind, always... that is safe. I don't waste time (money) debugging their stuff. I let the early adopters do that for me. I'd rather finish my project and go home on time.
-
So I started a new project at work. We're still running on VS2010, but we were planning to upgrade with VS2015. Just my luck that my project started pretty much on the release date of VS2015. I was given a choice, go with all the new tech in VS2015 or stay in the jurassic 2010. I choose 2015. Piece of crap crashes randomly when typing some HTML and Knockout (in a Razor file). I now find myself copy-pasting code to Notepad++, making my changes and copy-pasting it back into VS2015 :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
So I started a new project at work. We're still running on VS2010, but we were planning to upgrade with VS2015. Just my luck that my project started pretty much on the release date of VS2015. I was given a choice, go with all the new tech in VS2015 or stay in the jurassic 2010. I choose 2015. Piece of crap crashes randomly when typing some HTML and Knockout (in a Razor file). I now find myself copy-pasting code to Notepad++, making my changes and copy-pasting it back into VS2015 :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
I understand your pain... I have just posted an essay that describes my own experiences of simply trying to upgrade from VS 2013 SP3 to VS 2013 SP5. Please see... http://blackfalconsoftware.wordpress.com/ I believe you will find a kindred spirit...
Steve Naidamast Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
Sander Rossel wrote:
I mean, this stuff was tested, right
WTF do you think YOU are doing, haven't you reported the bug(s) yet, tcha you can't get good help these days!
Never underestimate the power of human stupidity RAH
This was a long time ago, but the last time I was on a team that reported a compiler(!) bug to Microsoft, it didn't get fixed. After chasing the support person for a while, they finally admitted that they'd been able to confirm the bug, but had been told by the developers to back off because they were too busy getting the next release out to worry about our compiler bug. We ended up having to work around their bug to get our release out. Every time I'm tempted to report a bug to MS I remember that experience, and refrain from wasting my time.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
In my experience, VS2015 has been pretty stable, most of the issues I encountered, even in 2013 could be attributed to extensions. Sander, what extensions do you have loaded?
Nothing, it's a clean install. I added some "packages" with NuGet, but that's mostly a bunch of JavaScript and CSS files in my solution. So nothing weird going on there.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
No surprises here. When was the last time they released something that wasn't a train wreck? I just installed windows 10 only to find out LiveMail is a flaming bag of *@#! too. Microsoft's sun is setting...they will soon be as irrelevant to software as IBM is to hardware. Bummer too (I based a career around these kids) :((
Jephre
Jfid wrote:
When was the last time they released something that wasn't a train wreck?
*Looks up the Windows 7 release date* 2009, so about 6 years ago ;)
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
What's the good stuff in 2013? I'm stuck with 2010 and haven't played with anything new in a while.
I couldn't say right from the top of my head. It's just a better overall experience. I guess intellisense for HTML and JavaScript is a lot better. Editor just works a bit better. There's a few new options. I'm sure you can find some articles comparing version x to version y though. Funny how I like 2013, but I can't really say why :laugh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
So I started a new project at work. We're still running on VS2010, but we were planning to upgrade with VS2015. Just my luck that my project started pretty much on the release date of VS2015. I was given a choice, go with all the new tech in VS2015 or stay in the jurassic 2010. I choose 2015. Piece of crap crashes randomly when typing some HTML and Knockout (in a Razor file). I now find myself copy-pasting code to Notepad++, making my changes and copy-pasting it back into VS2015 :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
I had similar experience. I downloaded VS2015 and tried it for a couple of days, faced its sluggish performance, some random crashes, and some weirdnesses of the JS editor, so I reverted back to VS2013. A disappointing experience it was.
