|
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
|
|
|
|
|
I've had no problems with VS2015 Community or Pro. Both work fine on one old and one new machine.
|
|
|
|
|
Same experience from my side.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Yes, but you're a robot. u.u
|
|
|
|
|
I have no issues with VS 2015, everything was/is perfect.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
I don't have any issues with it.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Even after Update 1 it's got problems.
It does prefer to crash every once in a while. I just started it, messed around with a small C++ project and just left it sit for a couple of hours. Came back and unlocked the machine, tried to go back to the VS window and it crashed.
Little things like that on my home Win10 machine and at work on Win8.1. A day doesn't go by where VS2015 hasn't crashed on me at least once.
|
|
|
|
|
Your PC should be a machine with big RAM and fast processor - if you dont like starring at "loading windows" 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
I have just set up a new, slightly more powerful home development machine. I installed Windows 7 on it and then went ahead and installed VS 2015 Community Edition with no apparent issues.
I am now debating whether that was a good idea and if I should have put VS 2013 on it, as I have on my old dev machine, since 2013 doesn't bug me about that darned cloud thingy all the time! ...and I had just got used the poor visual-quality of the UI only to have it get worse!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I'd love to give you some relevant information but my office machine (the first 64bit dev machine in the building) has so much crap on it I can't identify the source of the problems. I do have constant lock ups that last around 90 seconds and this weird cmd.exe window keeps appearing!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I 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.. 
|
|
|
|
|
I 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.
|
|
|
|
|
Doesn't work with Bitbucket (unless there is a workaround I can't find).
|
|
|
|
|
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.
|
|
|
|
|
VS2015 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.
|
|
|
|
|
Hell, 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.
|
|
|
|
|
I 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....
|
|
|
|
|
wish id stuck with VS2010
|
|
|
|
|
Only issue I had with VS2015 was that Blend 2015 doesn't support importing Photoshop PSD files; VS2013's Blend did ... so I'll keep both versions for now.
Other than that I frequently run 4 or more instances with no issues (12GB; 3.4Ghz; quad core)
|
|
|
|
|
I 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.
|
|
|
|
|
Just because of the speed issue, I stick with 2013....
|
|
|
|
|
Did I mentioned, that I hate those ISO inspections?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
As long as you do what's in The Book, you're fine.
Which is why when I had to write one many years ago, I included things I actually did instead of should do. Hence the "Dogs inward procedures" as well as "Goods inward procedures" and so forth...
Code inspections can serve a genuinely useful purpose if they are used right, ISO inspections generally don't.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
