How did Visual Studio 2015 get released?
-
I've now been using Visual Studio 2015 release for over a day. I love many of the new features, but I'm finding a serious bug about every half hour, including the IDE crashing due to a cut and paste. I was willing to put up with all of this, but Native Unit Tests now take a really long time to discover and then run. Just now, it took fifteen minutes to run, modify and run a single unit test three times. I finally gave up and went back to Visual Studio 2013. How did this product ever get released? If this is any indication of the quality of the upcoming Windows 10 release, I'll give a pass on it as well.
I went from 2008 to 2015 cause of that 64bit E&C. What a slow over bloated - oh my gosh. I wasn't part of the slow creep of bloat so I was shocked. What'ya mean "preparing to start"? I have elephanting work to do. And it won't load on XP but my product project does so: Back to 08
-
I went from 2008 to 2015 cause of that 64bit E&C. What a slow over bloated - oh my gosh. I wasn't part of the slow creep of bloat so I was shocked. What'ya mean "preparing to start"? I have elephanting work to do. And it won't load on XP but my product project does so: Back to 08
2008 is a speedboat compared to 2010 and later cruise ships. The latter will get you there in comfort, but take a while to do so. Right now, though, 2015 is looking more like the Costa Concordia.
-
2008 is a speedboat compared to 2010 and later cruise ships. The latter will get you there in comfort, but take a while to do so. Right now, though, 2015 is looking more like the Costa Concordia.
That's a good analogy. I felt like I was floating on a sea of .NET? or Java? It a real nice text editor and compiler for cryin' out loud.
-
I've now been using Visual Studio 2015 release for over a day. I love many of the new features, but I'm finding a serious bug about every half hour, including the IDE crashing due to a cut and paste. I was willing to put up with all of this, but Native Unit Tests now take a really long time to discover and then run. Just now, it took fifteen minutes to run, modify and run a single unit test three times. I finally gave up and went back to Visual Studio 2013. How did this product ever get released? If this is any indication of the quality of the upcoming Windows 10 release, I'll give a pass on it as well.
-
I've now been using Visual Studio 2015 release for over a day. I love many of the new features, but I'm finding a serious bug about every half hour, including the IDE crashing due to a cut and paste. I was willing to put up with all of this, but Native Unit Tests now take a really long time to discover and then run. Just now, it took fifteen minutes to run, modify and run a single unit test three times. I finally gave up and went back to Visual Studio 2013. How did this product ever get released? If this is any indication of the quality of the upcoming Windows 10 release, I'll give a pass on it as well.
Welcome to the Wonderful World of Microsoft Product Testing. The rules are simple: 1) Ignore existing bug reports - added features are much more profitable. It costs money to fix bugs! 2) Ignore beta tester comments - they didn't pay for the product, so what do they know? 3) All release categories are at least one step to the left of those in the rest of the world.
MS Name Real world name
Beta It compiles!
RC Alpha
RTM Beta
SP1 RTMIt's been this way since the DOS days, and they never listen. :sigh: I sometimes think their QA department consists of two copies of ELIZA and a tree sloth...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I've now been using Visual Studio 2015 release for over a day. I love many of the new features, but I'm finding a serious bug about every half hour, including the IDE crashing due to a cut and paste. I was willing to put up with all of this, but Native Unit Tests now take a really long time to discover and then run. Just now, it took fifteen minutes to run, modify and run a single unit test three times. I finally gave up and went back to Visual Studio 2013. How did this product ever get released? If this is any indication of the quality of the upcoming Windows 10 release, I'll give a pass on it as well.
Joe Woodbury wrote:
How did this product ever get released?
It got released so that some people could test for any remaining bugs and feed this back to Microsoft so that the wise ones who wait six months get a product with very few bugs. I just upgraded to 2013 a few days back and it's a great product now that the bugs have been ironed out.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
I've now been using Visual Studio 2015 release for over a day. I love many of the new features, but I'm finding a serious bug about every half hour, including the IDE crashing due to a cut and paste. I was willing to put up with all of this, but Native Unit Tests now take a really long time to discover and then run. Just now, it took fifteen minutes to run, modify and run a single unit test three times. I finally gave up and went back to Visual Studio 2013. How did this product ever get released? If this is any indication of the quality of the upcoming Windows 10 release, I'll give a pass on it as well.
Don'T you dare frighten me guy, just wanted to download the VS 2015 to check how it is, now im not sure what to do... instructions unclear
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
} -
Welcome to the Wonderful World of Microsoft Product Testing. The rules are simple: 1) Ignore existing bug reports - added features are much more profitable. It costs money to fix bugs! 2) Ignore beta tester comments - they didn't pay for the product, so what do they know? 3) All release categories are at least one step to the left of those in the rest of the world.
MS Name Real world name
Beta It compiles!
RC Alpha
RTM Beta
SP1 RTMIt's been this way since the DOS days, and they never listen. :sigh: I sometimes think their QA department consists of two copies of ELIZA and a tree sloth...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
[Re MS QA department] What does the tree sloth do?
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
-
[Re MS QA department] What does the tree sloth do?
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
Hits "Reset" when ELIZA crashes.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Hits "Reset" when ELIZA crashes.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
:) :thumbsup:
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
-
Don'T you dare frighten me guy, just wanted to download the VS 2015 to check how it is, now im not sure what to do... instructions unclear
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}Download and install side-by-side with your current VS installation. No biggie. I've been playing with VS2015 fro a few days (C++/MFC) and found no real issues other than the compiler being a lot better and generating a lot more warning. We cannot use it for production yet, because our 3rd party libraries do not yet support VS2015; and their headers barfs our warning with the new compiler.
I'd rather be phishing!
-
I've now been using Visual Studio 2015 release for over a day. I love many of the new features, but I'm finding a serious bug about every half hour, including the IDE crashing due to a cut and paste. I was willing to put up with all of this, but Native Unit Tests now take a really long time to discover and then run. Just now, it took fifteen minutes to run, modify and run a single unit test three times. I finally gave up and went back to Visual Studio 2013. How did this product ever get released? If this is any indication of the quality of the upcoming Windows 10 release, I'll give a pass on it as well.
Just try to program in Delphi XE8 for a few hours. You'll go running and screaming back to VS2015 before you're even able to get your project to compile. :laugh:
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
