Visual Studio 2015
-
Update 1 ruined VS2015 for me. Constant crashes, windows that wouldn't open, etc. After uninstalling Update 1 everything was fine (again). The only problem I have with VS2015 is that it is slooooooow. Let me rephrase that: It's SLOOOOOOOOOOOOOOOOW!!! In case you didn't get the message, it's really very very very very very very very very SLOW. Oh, yeah, it's also slow.
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
-
Well, I'm about to install Visual Studio on my restored win7 install. Is there anything about vs15 (community edition) I should know about? Should I bother installing VS2013 "just in case"?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Hell, I use VS2008 and VC++ 6.0. Yeah I have 2013 & 2015 installed, but jeez they are huge and I spend more time arguing with VS then coding.
-
Update 1 ruined VS2015 for me. Constant crashes, windows that wouldn't open, etc. After uninstalling Update 1 everything was fine (again). The only problem I have with VS2015 is that it is slooooooow. Let me rephrase that: It's SLOOOOOOOOOOOOOOOOW!!! In case you didn't get the message, it's really very very very very very very very very SLOW. Oh, yeah, it's also slow.
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
-
It does, you have to create a local Git repository first. Add solution to source control > Git > Commit Create bitbucket project on their website. Click Sync > Paste in remote bitbucket URI from "I have an existing project" > Commit
-
Well, I'm about to install Visual Studio on my restored win7 install. Is there anything about vs15 (community edition) I should know about? Should I bother installing VS2013 "just in case"?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I moved from VS2010 to VS2015 Community. Running on my Windows7 machines Home and work. I have had no problems at all. It has productivity tools available that I had not seen before and are extremely helpful. I am not sure about the slowness issue but I do not find it that way.
It's not the years... It's the miles.... Never trust a dog with red eyebrows....
-
Update 1 ruined VS2015 for me. Constant crashes, windows that wouldn't open, etc. After uninstalling Update 1 everything was fine (again). The only problem I have with VS2015 is that it is slooooooow. Let me rephrase that: It's SLOOOOOOOOOOOOOOOOW!!! In case you didn't get the message, it's really very very very very very very very very SLOW. Oh, yeah, it's also slow.
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
Agreed. It is slow. Also, like 2013, there is an issue with the cursor not being where you expect it to be. Not a show stopper but flaming annoying.
I may not last forever but the mess I leave behind certainly will.
-
Well, I'm about to install Visual Studio on my restored win7 install. Is there anything about vs15 (community edition) I should know about? Should I bother installing VS2013 "just in case"?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Be warned - the install takes for bloody ever... I've twice installed it and twice uninstalled it (and, btw, uninstalling takes just as long...) - and am sticking to 2012 for now. It's ok, I guess, I just don't like the way it seems to push you towards the cloud all the time. Once it wouldn't even load because it said it couldn't connect to my Microsoft account... even though that resolved itself in the end, that was the final straw for me.
I agree .I had terrible problems with visual studio 2015 and a lot of compatibility issues.I had projects in VS 2010 and VS 2012 and I was getting so many errors cause of compatibility.I think VS 2012 is the most mature.
-
Well, I'm about to install Visual Studio on my restored win7 install. Is there anything about vs15 (community edition) I should know about? Should I bother installing VS2013 "just in case"?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Well, I'm about to install Visual Studio on my restored win7 install. Is there anything about vs15 (community edition) I should know about? Should I bother installing VS2013 "just in case"?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I had a lot of stability problems pre "update 1", and with 3rd party addins loaded. Removing the addins and applying update 1 fixed almost all my issues. The only real paint point I have is that it's much slower for alot of things (refactoring/smart tags etc) than VS2013 was. When I say much, it probably isn't a lot in terms of actual time - but it's everytime you use those features, so it seems painful. Other than that, I quite like it now.
-
Well, I'm about to install Visual Studio on my restored win7 install. Is there anything about vs15 (community edition) I should know about? Should I bother installing VS2013 "just in case"?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Just because of the speed issue, I stick with 2013....
-
It does, you have to create a local Git repository first. Add solution to source control > Git > Commit Create bitbucket project on their website. Click Sync > Paste in remote bitbucket URI from "I have an existing project" > Commit
Thanks very much for that! I was previously using Git Extensions in VS2010 and couldn't get that to work in VS2015. This site: BitBucket in VS 2015?[^] indicated that it wasn't supported so I didn't delve to much further until I read your post. Now I have it working using Git GUI instead. Not quite as integrated as my previous method but indeed it does work.
-
I've had no problems with VS2015 Community or Pro. Both work fine on one old and one new machine.
Yes, but you're a robot. u.u
