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” Which has this link to a spreadsheet that lists the software: \_Studio\_by\_Subscription\_Level.Visual Studio subscriptions are licensed Per User with each licensed user able to use: I do want to figure out what MSDN/Technet program I would need to join in order to continue doing things on-premise. Currently I do this by bringing my VM with me using VMware Workstation Player. Is it time to just start using cloud VMs? What are the pros and cons? I know that a big pro would be the ability to work from anywhere. My local machine is really just a host for my "desktop" and "development" VMs. but then realized that the first question that should consider is whether local compute makes sense as a developer.
Got down into the weeds about Intel vs AMD, etc. Today, for the first time, I started thinking about it's replacement.
My current desktop (on-premise, on my desk) machine is serving me well, but It's going on five years old.
I just searched for and joined this sub to ask the same question.
0 kommentar(er)
