While no new software or license keys can be downloaded, existing downloads and product keys can continue to be used. Visual Studio subscriptions purchased via perpetual license programs allow limited perpetual use after a subscription expires. However, as we’ll discuss later – mixed environments can make audits more difficult. This doesn’t preclude you from mixing VMs running MSDN & Production software on one server as, according to the above, each VM constitutes its own environment rather than it being that host in its entirety.
Environments that are used for production at least some of the time, such a server that is rotated into production during peak periods of activity.Environments that support disaster-recovery or backup for a production environment.Environments that connect to a production database.“ any Physical or Virtual OSE running a production workload or accessing production data, or Physical OSE hosting one or more Virtual OSEs running production workloads or accessing production data”Īnd the Visual Studio Licensing Guide gives the following examples: The Microsoft Product Terms define this as: Visual Studio software cannot be used in a production environment. Visual Studio subscriptions can be reassigned between users but only once every 90 days Production Environment The requirement for a “dedicated device” precludes Visual Studio from being used in public cloud shared environments such as Amazon AWS and Google GCP – although it can (in most cases) be run on Microsoft Azure. “ design, develop, test, and demonstrate their programs” “ any number of copies of the software and any prior version on any device” Visual Studio subscriptions are licensed Per User with each licensed user able to use:
0 kommentar(er)
