VS2013 First impressions
-
Using VS2013 for the first time in anger .. and I mean "anger" if I see the 'Waiting for required operation ...' dialog once more (this last timeI was copying 24 lines of code to the clipboard and, while I didn't time it, it was long enough for me to open the browser, come to CP, and enter most of this message!) I have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added - leaving red squiggles a-plenty even though it would build clean. And this is in a small project - god knows what I'm going to experience when I open the main project in it! Dis-a-pointed!
I've actually been pleasantly surprised in working with VS2013 versus 08, 10, or 12. I do, however, have to restart VS (both 12 and 13) more than once in a while because it doesn't recognize that I removed a class and so decides that it won't compile anymore.
-
Mycroft Holmes wrote:
All version of VS have had their shortcomings
Except version 6, that was the sweet spot as a c++ programmer before all the dot net stuff came along.
really? Even over VS2008 with SP1?
-
Using VS2013 for the first time in anger .. and I mean "anger" if I see the 'Waiting for required operation ...' dialog once more (this last timeI was copying 24 lines of code to the clipboard and, while I didn't time it, it was long enough for me to open the browser, come to CP, and enter most of this message!) I have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added - leaving red squiggles a-plenty even though it would build clean. And this is in a small project - god knows what I'm going to experience when I open the main project in it! Dis-a-pointed!
Everybody in the office gets sick of me shouting out "Win-Doze!". I'm running 2010 on a crappy, Business Systems-loaded XP machine. The hardware is Core2Duo with plenty of RAM, which should be hot to trot, but no. It goes to sleep more often than a geriatric Llama. Yesterday, for a new project, I had the joy of installing VS2012 on a 7 machine, Core i5, plenty of RAM. The situation is slightly improved, but now I have the new, 'antique newspaper' interface. And while you can make 2012 install through a proxy(with complaints of course), updating the windows itself proves impossible once you update the updater. And of course I just loved watching all the branded MS features install, and going 'WTF is that?' Never mind. My pirate friends have obtained the old Edward Woodward series '1990' for me, and I can at least escape from 'Dogs Win Prizes From Simon Cowell's Haircut' for a few hours.:cool:
-
I tried installing it at home as I was playing with some c# stuff. It requires the latest version of IE which fails to install for some obscure reason on my home machine. Real men code in vim.
It did require the latest IE but now it doesn't. They updated it in November so you should try downloading it again. Even after that some things were a bit flaky with IE < 10 but they fixed that in Update 1. Visual Studio and Team Explorer 2013 no longer require IE 10 for installation[^]
Regards Nelviticus
-
Using VS2013 for the first time in anger .. and I mean "anger" if I see the 'Waiting for required operation ...' dialog once more (this last timeI was copying 24 lines of code to the clipboard and, while I didn't time it, it was long enough for me to open the browser, come to CP, and enter most of this message!) I have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added - leaving red squiggles a-plenty even though it would build clean. And this is in a small project - god knows what I'm going to experience when I open the main project in it! Dis-a-pointed!
In my case 2013 works pretty well. It is slower than 2010 to open a project and for the first compiles... but after every "Lazy<T>" is loaded it works fine. In fact, when using 2010 for javascript it crashed a lot (or it tooks hours to do something stupid and I forced it to close before that). 2013 works much better for that.
-
Using VS2013 for the first time in anger .. and I mean "anger" if I see the 'Waiting for required operation ...' dialog once more (this last timeI was copying 24 lines of code to the clipboard and, while I didn't time it, it was long enough for me to open the browser, come to CP, and enter most of this message!) I have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added - leaving red squiggles a-plenty even though it would build clean. And this is in a small project - god knows what I'm going to experience when I open the main project in it! Dis-a-pointed!
_Maxxx_ wrote:
have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added
Ya, intellisense is pretty buggy. Helps to close all the code windows, exit, restart, and wait wait wait until intellisense is done grinding on a core rebuilding its database.
_Maxxx_ wrote:
'Waiting for required operation ...'
Running it in a virtual machine? or on a system with little memory? Only time I've seen similar behavior is from someone running windows in a virtual machine that isn't configured to be overloaded with RAM. Its not spinning on the CPU when it does that, so we suspect it's thrashing memory. If you can get past those issues, it's really quite nice to use.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
Using VS2013 for the first time in anger .. and I mean "anger" if I see the 'Waiting for required operation ...' dialog once more (this last timeI was copying 24 lines of code to the clipboard and, while I didn't time it, it was long enough for me to open the browser, come to CP, and enter most of this message!) I have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added - leaving red squiggles a-plenty even though it would build clean. And this is in a small project - god knows what I'm going to experience when I open the main project in it! Dis-a-pointed!
Strange, I have a good experience with Visual Studio 2013, except, when programming on C++, but I can live with it. Your problems seems related to low memory (or slow HDD).
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
_Maxxx_ wrote:
have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added
Ya, intellisense is pretty buggy. Helps to close all the code windows, exit, restart, and wait wait wait until intellisense is done grinding on a core rebuilding its database.
_Maxxx_ wrote:
'Waiting for required operation ...'
Running it in a virtual machine? or on a system with little memory? Only time I've seen similar behavior is from someone running windows in a virtual machine that isn't configured to be overloaded with RAM. Its not spinning on the CPU when it does that, so we suspect it's thrashing memory. If you can get past those issues, it's really quite nice to use.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
Using VS2013 for the first time in anger .. and I mean "anger" if I see the 'Waiting for required operation ...' dialog once more (this last timeI was copying 24 lines of code to the clipboard and, while I didn't time it, it was long enough for me to open the browser, come to CP, and enter most of this message!) I have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added - leaving red squiggles a-plenty even though it would build clean. And this is in a small project - god knows what I'm going to experience when I open the main project in it! Dis-a-pointed!
_Maxxx_ wrote:
I have also had to close it and re-open once as the intellisense refused to pick up some new classes that had been added - leaving red squiggles a-plenty even though it would build clean.
If you are always getting latest from source control when opening a project, disable that, or you can write a batch file to delete your *.suo files before you open a solution (though of course you'll lose your startup project and open files and who knows what other conveniences). Kind of sucks, but that was MSFT's response to our company's complaint about the squiggles (apparently the async loading fails), as opposed to, I don't know, fixing the bug. Our situation was for Silverlight projects, so YMMV.
-
I tried installing it at home as I was playing with some c# stuff. It requires the latest version of IE which fails to install for some obscure reason on my home machine. Real men code in vim.