

O Develop web applications against a server identical to IIS O Test the same page, application, or site in a variety of browsers O Edit HTML, CSS, and JavaScript in their own editors O Use various tools to debug, optimize, and publish apps O Use default project templates that provide the files, resources, and structure for various kinds of Windows Store apps Develop mobile and web applications for use by your constituents and donors.Develop custom applications for use in your organisation.If you have software development experience, you can use Visual Studio to: This donation provides one license and a subscription to the Microsoft Developer Network (MSDN). This helps the community, keeps the forums tidy, and recognises useful contributions.Visual Studio 2012 Professional Edition is an integrated development environment (IDE) for individual developers and small teams who build applications that operate on Microsoft Windows, in Microsoft SharePoint, in the cloud, or on Microsoft's web and mobile-device platforms. This helps the community, keeps the forums tidy, and recognises useful contributions. (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. MSDN licensing terms for OS, are a little different to MSDN licensing terms for non-OS products, as stated in the MSDN licensing info (it is assumed that you already have an OS license for the hardware)

Win7Professional, via my VL MSDN, might be a VL channel product which accepts a VL MAK, but yours might only offer Win7Professional as a Retail channel product, which might not accept a VL MAK so you'd need to use your Retail MSDN Win7Pro key.Įither way, if you are using Win7Pro in compliance with the MSDN licensing terms, that's fine. The Retail subscription doesn't offer exactly the same product licensing channels, compared to the VL MSDN Subscription, so, MSDN Retail might not offer the VL channel product you want, which means that MAK (which is a VL key) might not work.Į.g. MSDN Subscriptions are available in two licensing channels: Retail, and Volume Licensing. In general, what you are *permitted* to do, and, the technical steps involved for *how* you do it, can be difficult to align. MSDN subscription licensing info is here: A good forum for MSDN subscription questions is here:
