Thursday, May 15, 2014

Visual Studio 2013 and MSDN Licensing Whitepaper

Microsoft Downloads - Visual Studio and MSDN Licensing White Paper

This white paper provides an overview of the Visual Studio product line, including MSDN subscriptions, and the licensing requirements for those products in common deployment scenarios.

Version: 1.0

Date Published: 5/12/2014

File Name:

Visual Studio 2013 and MSDN Licensing Whitepaper - May-2014.docx

Visual Studio 2013 and MSDN Licensing Whitepaper - May-2014.pdf

Visual Studio 2013 and MSDN Licensing Whitepaper - May-2014.xps

This white paper provides an overview of the Visual Studio product line and the licensing requirements for those products in common deployment scenarios. For a definitive guide to licensing terms and conditions for products licensed through Microsoft Volume Licensing, see the Microsoft Licensing Product Use Rights (PUR) document and applicable licensing agreements. For retail customers the license terms are specified in the End User Licensing Agreement (EULA) included with your product or with your MSDN subscription.

The MSDN licensing question seems to come up, well seems like every time we get someone new. What with the RTM release up VS 2013.2 seems like a good time to cache this here for a future, "I blogged about it..." email... :)

imageimage

imageimageimage

 

Related Past Post XRef:
"Visual Studio 2012 and MSDN Licensing White Paper"
Visual Studio 2010 and MSDN Licensing Whitepaper Updated
Visual Studio 2010 Licensing White Paper (includes Team Foundation Server, Lab Management and IntelliTrace)

No comments:

Post a Comment

NOTE: Anonymous Commenting has been turned off for a while... The comment spammers are just killing me...

ALL comments are moderated. I will review every comment before it will appear on the blog.

Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...

I reserve, and will use, the right to not approve ANY comment for ANY reason. I will not usually, but if it's off topic, spam (or even close to spam-like), inflammatory, mean, etc, etc, well... then...

Please see my comment policy for more information if you are interested.

Thanks,
Greg

PS. I am proactively moderating comments. Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...