Build Server Licensing Question
We get a lot of questions from customers at the events we run, the answers to which I'm sure will be of interest to others as well. I'm going to publish questions (and answers) that I get and I've asked my team to do the same. Hopefully that way many more of you will see the answers to the great questions we get at these events. I've also considered whether we should perhaps create a separate team blog for this puropose or incorporate an event Q&A section on our local MSDN Website. I'm not sure what the best mechanism is but rather than delay further I've opted to publish in individual blogs and see how it goes.
So, to my first question. We hosted an event on Visual Studio Team System in London last Friday. One of the questions that came up revolved around MSBuild and having a dedicated build lab:
If I'm building an application that has a dependency on say, CMS or BizTalk being installed on my build server, how do I license it?
No point starting with an easy one eh? Unfortunately it's not possible to give complete answers to licensing questions without full details of the specific scenario but these are some general guidelines relating to software development:
- If you are using a product in a production environment then you need a full licence and pay for what you use at the point of install. Thus if you install SQL Server, you need to pay for it regardless of whether it is active or switched on.
- If you are using a product for development (including a build lab) then you need a developer licence. This may be from an MSDN subscription, developer copies of product (eg BizTalk has a developer version) or a licence as part of the Certified Partner Programme.
In addition, the following are some useful links regarding MSDN and licensing in general:
I hope some of you found that useful. I'd be very interested in your feedback - are you interested in seeing these types of questions and answers?