I have installed Visual Studio 2013 community edition. However the links on Microsoft’s site always lead me to docs where there are references to Visual Studio 2015
https://visualstudiogallery.msdn.microsoft.com/20b80b8c-659b-45ef-96c1-437828fe7cf2
Most folks on Windows seem to prefer Visual-Studio over Mono. Some help on docs is requested.
/rk
Um… You asking Microsoft to improve their docs? Unity docs are online, and also installed with the editor.
From an end-user standpoint (a newbie at that ) either Unity or UnityVS (guess that would be Microsoft) should make docs less ambiguous.
I am not quite sure what kind of documentation you are looking for. But if it is only about getting UnitVS running take a look at this:
Can you highlight for me some Unity documentation which you find ambiguous. I’m still unclear what the issue is. (I own the docs, so want to help out.)
I use VS 2013 community edition. I was trying to make the UnityVS plugin (ver 1.9.9 ) work with Unity 5.0
I ended up at
https://visualstudiogallery.msdn.microsoft.com/20b80b8c-659b-45ef-96c1-437828fe7cf2
The only relevant link on this page appears to be
This in turn takes me to
which talks of “Visual Studio 2015 RC”.
So, I am suddenly left in the lurch. I have no interest in trying this out in “Visual Studio 2015 RC”. (RC probably means Release Candidate )
So, where are the docs for “VS 2013 community edition” ?
Okay, so this is definitely a Microsoft issue. I’ll move this thread into the “Editor and General Support” subforum, so more community members see your issue and should be able to contribute.
Thx.
UnityVS doesn’t really do that many things - it just makes VS and Unity talk nicely with each other. There isn’t that much to document. But the docs on the official site should have what you need to get everything working.
If you want to read about debugging, read up on debugging in Visual Studio in general - the only thing different from UnityVS debugging and “normal” debugging in Visual Studio is that it actually works with Unity.
Baste,
Thx for responding.
One small fix that can help a lot is to clarify if
applies to “VS Community Edition 2013” also.
I’m running it on community, so it works.
Community Edition is a pretty new thing - back when that page was written, you only had Express that didn’t support plugins, and Professional, that supported plugins and cost all the money to own.
Baste,
Thx for the confirmation !