As a long time Microsoft developer, I find MSDN to be an invaluable resource.

However, when tinkering at home I am not able to play with the best latest technologies and the different offerings coming from Microsoft as I cannot justify paying such a hefty price for what is essentially a pastime.

The Express editions are great, but fall flat when trying to use the more advanced feature I am used to from the versions I use at work. I cannot get the latest betas and play with the new offerings, not legally, anyway.

Apart from getting an MVP, how would one go about getting an MSDN subscription for an acceptable price for a non-professional environment?

I am aware of the Empower program, but I thought it was geared towards getting commercial software to market. If this is not the case, it appears like the way for me to go. Thanks!

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
If this question can be reworded to fit the rules in the help center, please edit the question.

2

MVP is generally not just something you get it is awarded to professionals who add exceptional value to the developer community and is generally a lot of work to achieve MVP status
–
Chris McGrathOct 22 '13 at 18:11

MSDN subscriptions are per user rather than per device so as long as you're the only person using them I think you should be free to use them at home. I'm not aware of any differentiation being applied to the workplace, unless of course your workplace itself lays down such a rule.

MSDN Subscriptions are licensed to
individuals who may install the
provided software without restriction.
Software provided through MSDN
Subscriptions is licensed for design,
development, test and demonstration of
your applications.

So how does that work when you do things that are not for the design/development/testing/demonstration of your applications? What if you work on a personal project on that copy of Windows or Visual Studio you decided to install at home?
–
jcmNov 18 '09 at 23:48

This is not legal. I just checked msdn.microsoft.com/en-us/subscriptions/cc150618.aspx and according to paragraph 5, you must also purchase a license for any use that is not related to the development of your work's products. So unless you intend to use this PURELY for business at home, it is not legal.
–
jcmNov 18 '09 at 23:56

4

That's not actually what it says. The paragraph is making the point that you cannot use MSDN license for non-development purposes. It does not make a distinction between "work" and "home". If you used an MSDN Windows license for your home PC for games, videos etc, that would be illegal. If you use Visual Studio to write software on your home PC then you're covered. The question related to "playing with the best technologies" at home, so MSDN is usable in this situation.
–
Luke BennettNov 19 '09 at 9:06

2

To clarify, if you use an MSDN Windows license for your work machine which you also send/receive email, prepare spreadsheets etc on, then you are again not covered. Like I say, the distinction isn't between work and home use, but between development and non-development use, whatever context that might be.
–
Luke BennettNov 19 '09 at 9:13

What I gather from reading the MSDN licensing whitepaper is that you are licensed to use the software at home as long as you employed at the company. Granted, if the company chooses to continue to extend to you the MSDN license after you leave (perhaps if you're still going to be doing contract work), you would still be licensed to use the software at home.
–
Ben McCormackSep 2 '10 at 1:07

In agreement with comments already made - get an Empower subscription, it's geared up towards people like yourself. As I recall, you have 2 years to bring a product/solution to market (where market is very loosely defined) that uses some element of MS technology (again, where this is quite loosely defined). In return for quite a modest outlay, you get MSDN, a bunch of OS licenses and access to development tools and end-user application programs (XP, Vista, Office being obvious examples).

For instance, I develop in Delphi but write code to run on SQL Express 2005 and full-blown SQL Server 2005+, and this entitles me to purchase an Empower agreement. I get all the goodies, plus things like Visual Studio, SQL Server, Office and OS licenses. If you don't bring a solution to market in the time allocated, you can pay to extend your agreement or... well, I must admit I'm not sure. It's hard to see what bad thing can befall you if you try to produce something but ultimately fail - it's the American dream, right? You have to stop using the software at the end of the period, etc. :-)

If you want to develop for desktop Windows you really need some level of MSDN access, or a good broadband connection and some patience while you access the online materials. Empower is a fairly pain-free method of getting your hands on all the best tools for very little outlay indeed - you end up with a large pile of DVDs and CDs, and a few updates during the year. I'd say it was an essential purchase - particularly if this is viewed as a career investment, or some element of training or progression. It's not a lot of money at all (I speak as an ISV - everything I have to pay out truly comes from my pocket!).

You may want to talk to your boss about your opportunities to join MSDN for free. I work at a company using all Microsoft Software, and I get a free subscription, which comes with access to almost all of microsoft's software.

Even with just one licence you can get MSDN Under a Volume Licence. This is cheaper and (depending on exactly which VL program) can allow the cost to be spread across the VL period (once fully paid the licences become permanent).

Also means you get the VL builds and keys for Office/Windows rather than just the retail.

Good assumption, however, I am a contractor, so benefits that permanent employees get do not apply.
–
Oded♦Oct 25 '08 at 21:11

Don't make that assumption without checking. Lots of times things like this aren't a benefit for W2 employees (in a US context), they're for the use of the people working on the code. Employment status isn't relevant.
–
James MooreJul 8 '11 at 16:29