Are you a professional developer? Do you get an MSDN from your organisation? Did you know that you can use it at home on both commercial and open source projects of your own!
MSDN subscriptions are licensed on a per-user basis. One person can use the software to design, develop, test, or demonstrate his or her programs on any number of devices. Each person who uses the software this way needs a license.
-MSDN Licencing
That’s right, the MSDN that you company bought you entitles you to run Windows, Office & Visual Studio in production at home. Its a licence for YOU and not just for them.
Figure: Over 11 terabytes of data on MSDN
I was talking to Mark Groves at the MVP Summit and I had a double-take when he mentioned that most developers don’t know that you get a take-home licence with you MSDN. I was surprise because I have know and taken advantage of this for the better part of 8 years, and I was even more surprised when he mentioned that Scott Hanselman was also unaware of this. This is an awesome benefit to being a Microsoft developer and I can’t believe that it is not more well known.
Figure: You get Azure time as well
On top of that you get a number of other benefits. You get the Azure time above and you also get the ability to run an almost limitless number of development boxes as well. Basically for a developer with MSDN you can almost run “whatever” at home and be fully licenced and I have never encountered anyone who has maxed out their instances.
The thing that I tend to find that is not done is the assignment of MSDN licences that a company has bough to the individuals that are using it. What companies really don’t understand is that no matter how many MSDN licences that they own, they are not licenced to use any of it unless they are assigned to individual Live ID’s.
MSDN subscriptions are only offered per individual, there are no “team” subscriptions or sharing of subscription benefits.
-MSDN Licencing
In most companies that I do work for the operations team hoards the MSDN’s so those pesky developers can’t download on the network. But this, my dear ops guys means that you are using software illegally within your company, so get over it and assign those MSDN subscription to those that they were bought for!
Did you EVER have an MSDN? Another of those little known things about an MSDN is that it is perpetual. That is that you can use forever the software that became available when you received your MSDN.
In most cases, MSDN subscriptions come with “perpetual” use rights, the ability to continue using the software after the subscription has expired, even though the ability to download software and product keys ends when the subscription expires.
-MSDN Licencing
You just don’t get anything new ![]()
And just in case you were worries about buying licences for your business acceptance testing (BAT) then:
When software development projects are nearing completion, an MSDN subscription license also allows your end users to access the software to perform acceptance tests on your programs.
-MSDN Licencing
MSDN has one of the most flexible licencing terms in the industry and you should be using it to its full potential and not leaving it on a shelf! It will make some of your developers more valuable if they can exercise the tools in their spare time and the others just will not take advantage of it.
What to read next
An adoption strategy for testing with Visual Studio 2010
Guidance on adopting Visual Studio 2010 test tools, including Microsoft Test Manager, hands-on labs, and agile training to improve …
Visual Studio 2013 and TFS 2013 are released, get yours now! Oh and Windows 8.1…
Visual Studio 2013, Team Foundation Server 2013, and Windows 8.1 are now available, offering new ALM features, upgrade options, and …
The benefits of Visual Studio Online for the Enterprise
Explains how Visual Studio Online streamlines enterprise software development with cloud-based tools, continuous updates, scalability, …
Unlocking Engineering Excellence: How Azure DevOps Transforms Traceability, Transparency, and the Developer Experience
Unlock engineering excellence with Azure DevOps, boost traceability, transparency, and developer experience for agile, high-performing …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …