Visual Studio 2015
-
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 have VS 2015 installed on my Win 10 home PC - 3 Ghz quad core Athlon with 12 Gb RAM and it runs fine. Can't recall ever having any crashes. Also had it shoe-horned onto a low-end tablet (also Win 10 - 1Gb RAM and 16Gb storeage...) and, while slow(ish) I was somewhat surprised to find it was perfectly usable when partnered with a USB keyboard. I wouldn't voluntarily choose to go back to VS 2013. But then, I'm just a hobbyist tinkerer.. :-D
-
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 got one of those Windows 10 development environment VMs which include VS2015. Get a Windows 10 development environment - Windows app development[^] I used Hyper-V. I've been using VS2013 for a good while and had no problem opening and woking on my solutions using VS2015 in the VM. It's still too early for me to completely move to VS2015 for daily development though.
-
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 -
I use 2013 at home at at work, the only problems I have had with it are that occasionally intellisense stops functioning(a restart of VS2013 fixes it) - so I would go with VS2013.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
I cant tell if the first 2013 is a typo - else i read this as - 2013 intellisense breaks - so use 2013.
You read it correctly - no typo and I did basically say that 2013 breaks, however from what I have read it breaks less frequently than 2015 so with the restart option I am okay with that.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
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, 2013VS2015 has ASP.Net 5 and MVC 6 (unless these can these can be loading in vs2013??) - which offer some benefits to previous version - mainly for me - build times reduced by new why server side code compiled. and Web API Controller + MVC Controller merged into one controller.
-
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