Piece of @$#(*&!^ VS2015...
-
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
Given the choice between latest and greatest and older tried and true, when it comes to IDEs I always go with something a little older. The bugs have been worked out and it's in a more solid state.
-
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've ported a moderately-sized C++ project to it (a C++-only version of WinFract); it seems stable so far.
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
-
Given the choice between latest and greatest and older tried and true, when it comes to IDEs I always go with something a little older. The bugs have been worked out and it's in a more solid state.
-
Given the choice between latest and greatest and older tried and true, when it comes to IDEs I always go with something a little older. The bugs have been worked out and it's in a more solid state.
:thumbsup:
-
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 recently moved from VS2010 to VS2013 - I would recommend VS2013, so far I have had no problems and it is a big improvement on 2010. The beauty is that we can open 2010 projects in 2013 change them and then reopen them in 2010 if we want to(2013 does not 'convert' the project to 2013).
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
Given the choice between latest and greatest and older tried and true, when it comes to IDEs I always go with something a little older. The bugs have been worked out and it's in a more solid state.
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
-
I recently moved from VS2010 to VS2013 - I would recommend VS2013, so far I have had no problems and it is a big improvement on 2010. The beauty is that we can open 2010 projects in 2013 change them and then reopen them in 2010 if we want to(2013 does not 'convert' the project to 2013).
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
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
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?
-
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
