Oct 02, 2018 - 05:53 AM
There are two parts to Visual Studio
1) The Visual Studio Developer Tools bits (which was the L)
2) The MSDN bit which grants you rights to use Commerical Licensing in a dev environment plus a host of other benefits (which is the SA)
(Given its all together now and licensed as a subscription for both bits, this is slightly dated information)
It is licensed PER USER so in a similar way to licensing in a TS environment, any one who can access the Visual Studio Tools need a Visual Studio license, and anyone who accesses the MSDN covered commercial license (e.g. Windows/SQL Server) requires an MSDN license.
People accessing purely for the use of UAT do not require a license as they are covered by the the developers MSDN license.
Best practice is to keep your Dev within Dev, UAT within UAT and Prod within Prod - mixing and matching causes complications if you cannot show clear boundries and restrictions to access
Oct 08, 2018 - 09:01 AM
However, would you know of any different way to license Visual Studio for Production, or a license that the user could buy (instead of the current Visual Studio with MSDN). Could you use VS Code or Essentials instead? Are any of these viable, free alternatives for corporate use in Production? On AWS?
Any help much appreciated..
Source: Visio Studio Alternatives
Oct 08, 2018 - 09:16 AM
What is this SW that requires a develpment tool to make it run?