Versiones Visual Studio 2010

7/29/2019 Versiones Visual Studio 2010

1/29


2/29

Professional

Premium

Ultimate


3/29

MSDN Subscriptions are the most convenient way tocost-effectively develop applications on the Microsoft

platform with a simple licensing model.

Subscriptions include access to specified* resources like Team Foundation Server (including one CAL)! Development and test use of certain Microsoft tools, servers, and

clients on as many machines as you need* Unlimited software downloads Technical support E-Learning New and old version rights And more

*Specific MSDN resources depend on the level of Visual Studio 2010 purchased


4/29

Software for Production Use Visual Studio 2010Ultimate with MSDN

Visual Studio 2010Premium with MSDN

Visual Studio 2010Professional with MSDN

Visual Studio Test Prof2010 with MSDN

Visual Studio Team Foundation Server 2010

Visual Studio Team Foundation Server 2010 CAL1 1 1 1

Microsoft Expression Studio 3

Microsoft Office 2007 Ultimate, Communicator

2007, Project 2007 Standard, Visio 2007Professional, SharePoint Designer 2007

Software for Development and Test Use Visual Studio 2010Ultimate with MSDN




Windows Azure

Windows (client and server)

Microsoft SQL Server

Toolkits, Software Development Kits, DriverDevelopment Kits

Microsoft Office

Microsoft Dynamics

All other servers

Windows Embedded operating systems

Other key MSDN Subscription benefits Visual Studio 2010Ultimate with MSDN




Microsoft

Learning Collections 2 2 1 1

Online Concierge

Technical support incidents 4 4 2 2

Priority support in MSDN Forums See the Visual Studio 2010 Feature Matrix for a comp


5/29


6/29

Volume Licensing (VL)Volume licensing of software makes it easier and more affordable to run software on multiple compwithin a single purchasing organization. For larger numbers of licenses (5 or more), organizations typurchase through one of several Microsoft Volume Licensing programs.

Open Value. All Visual Studio 2010 client edition products licensed in the Open Valprogram can only be licensed with an MSDN subscription.

Open License. All Visual Studio 2010 client edition products can be licensed with or an MSDN subscription.

Select. All Visual Studio 2010 client edition products can be licensed with or without

MSDN subscription. Enterprise Agreement. All Visual Studio 2010 client edition products licensed in th

Enterprise Agreement program can only be licensed with an MSDN subscription. (ThMSDN Operating Systems subscription is not available through an Enterprise Agree

All Visual Studio 2010 server products are available through all Volume Licensing programs, as are all additional licenses.

More information on Volume Licensing and the above programs can be found at: www.microsoft.com/licensing

Use rights for software licenses and MSDN subscriptions purchased through a Volume Licensing Program are governed bVolume Licensing Program Agreement under which the licenses are acquired together with the Microsoft Licensing ProdRights (PUR) (Windows Embedded operating system products are always governed by the in-product EULA, even when othrough Volume Licensing programs.)
http://www.microsoft.com/licensinghttp://www.microsoftvolumelicensing.com/userights/PUR.aspxhttp://www.microsoftvolumelicensing.com/userights/PUR.aspxhttp://www.microsoftvolumelicensing.com/userights/PUR.aspxhttp://www.microsoftvolumelicensing.com/userights/PUR.aspxhttp://www.microsoftvolumelicensing.com/userights/PUR.aspxhttp://www.microsoftvolumelicensing.com/userights/PUR.aspxhttp://www.microsoft.com/licensing


7/29

With the introduction of Visual Studio 2010, Microsoftmade significant changes to simplify decision-making focustomers and make products more accessible, includin Reduction in the number of client products (the Visua

Studio IDE) from seven versions to three.

Changes to MSDN subscriptions to align with new

client products. Introduction of new products for software testers and

management.

Improvements to licensing terms for Team Foundatio

Server and load testing


8/29

Client Products

Microsoft Visual Studio2010 Ultimate withMSDN

Microsoft Visual Studio2010 Premium withMSDN

Microsoft Visual Studio

2010 Professional withMSDN

Microsoft Visual StudioTest Professional 2010with MSDN

This product line offering is licensed according tothe Microsoft Developer Tools licensing modelfor purchases made through Microsoft VolumeLicensing programs, or according to the RetailSoftware License Terms for retail purchases. Thespecific level of MSDN subscription benefitscorresponds to the Ultimate, Premium, orProfessional designation in the Visual Studio2010 product name.

Server Products

Microsoft VisualStudio TeamFoundation Server2010

Microsoft VisualStudio LabManagement 2010

Team Foundation Server is licensedaccording to the Microsoft Server/CAL(Client Access License) licensing model forVolume Licensing and according to the

Retail Software License Terms for retailpurchases. Lab Management is licensedaccording to the Microsoft Server/Per-processor licensing model for VolumeLicensing, and according to the RetailSoftware License Terms for retail purchases.

Additional Tools

Microsoft VisuaTeam FoundatioServer 2010 CA

Microsoft VisuaLoad Test VirtuaPack 2010

Microsoft Visua

Team FoundatioServer 2010 ExtConnector Licen


9/29

Visual Studio 2010 Client Edition Licensing

All Visual Studio 2010 client editions (Ultimate, PremiumProfessional, and Test Professional) and other softwareprovided under MSDN subscriptions are licensed on a puser basis. Each licensed user may install and use the software on as ma

devices as they wish for purposes of designing, developing,testing, and demonstrating applications.

Each additional person who uses the software on those

devices must have his or her own product license and/oMSDN subscription.


10/29

Visual Studio 2010 Client Edition-Only Licensing

Visual Studio 2010 products can be purchased without aMSDN subscription in certain channels: Open Value

Select

The user can install and use the Visual Studio client

software on as many devices as they like. The products are licensed on a per-user basis, however

that is, only the licensed user can use the software.


11/29

Visual Studio 2010 Client Edition with MSDN Licensing

MSDN subscriptions provide a convenient and costeffective blanket licensing mechanism for development test environments, with limited overhead and a conveniper head acquisition model.

Importance/Relevance: Customers are required to license evecopy of every Microsoft product they deploy, including allphysical and virtual instances. As such, licensing a developmeand test environment can be expensiveand challenging tomanage as new servers are set up and others are torn down.


12/29

Visual Studio 2010 Client Edition with MSDN Licensing

Licensed per person, MSDN subscriptions are assets that are acquby an organization, assigned to team members, and enable those tmembers to deploy and use specified Microsoft software on anynumber of devices and/or virtual machines for purposes of design,development, test, and demonstration. The specific Microsoft software covered (and other benefits provided) u

an MSDN subscription depend on which specific MSDN subscription islicensed.

As long as every person touching that software has an appropriate MSsubscription, no additional licensing or reporting is required.

When a team member leaves the team, the MSDN subscription is reclaiand can be assigned to someone else (with the caveat that MSDNsubscription licenses can only be reassigned at most once every 90 dayMicrosoft Volume Licensing programs).


13/29

Microsoft licenses Team Foundation Server under theServer/Client Access License (CAL) licensing modelis, organizations must have a license for each runninginstance of Team Foundation Server and, with certainexceptions, a Team Foundation Server 2010 CAL for e

user or device that accesses Team Foundation Server


14/29


15/29

Client Licensing Scenarios Per-User Licensing

Assigning MSDN Subscription Licenses to External Contractors

Multiple Devices

Virtual Environments

Previous, Prerelease and Trial Versions of Software

Perpetual User Rights

Demonstration Using Terminal Services User Acceptance Testing

Distribution of MSDN Software as Part of an Installation Image

Distribution of Microsoft Software Components within an Application

Product Keys and Installation Software

Team Foundation Server CALs (Client Access Licenses) Team Foundation Server and SQL Server Restricted-Use Licenses


16/29

Scenario 1:

A development team consistsof 6 software developers, 1architect/developer, 3 testers,and 1 configuration/supportperson. The team is buildingan in-house Web-basedaccounting system, andwants to use MSDN softwareto setup a test environmentrunning Windows Server2008 and Microsoft SQLServer 2008. If all 11 teammembers will be touchingthe test environment, theneach will require an MDSN

subscription.

Scenario 2:

An organization has twodevelopment teamsonebased in Seattle and theother in Singapore.Because of the timedifference, the two teamsare never working at the

same time. However, thisdoes not mean that MSDNsubscription licenses canbe shared. Each teammember in each locationmust have his or her ownMSDN subscriptionlicense.

Scenario 3:

A member of a deveteam is taking a sabba month and will nothis or her MSDN sublicense during that tiBecause an MSDNsubscription license

be reassigned from oindividual to anotherevery 90 days, the tereplacement team mcannot use the MSDsubscription license to the person on sabInstead, the replacem

must have his or her license.


17/29

Scenario:

An external contractor is to work temporarily within an organizationsdevelopment team. Each development team member in the organization a Visual Studio Premium with MSDN subscription.

If the contractor has a Premium subscription too then, like the existing teamembers, the contractor can use the software in the developmentenvironment.

If the contractor does not have an MSDN Subscription license, or has anMSDN Subscription at a lower level that does not cover all of the softwarethey will be using, then either: The contractor must obtain an appropriate (higher-level) MSDN Subscription license.

The organization must assign one of their spare (unallocated) MSDN Subscription licenses tcontractor for the duration of the contract.


18/29

Multiple Devices:

Any team member can install and useMSDN software on as many devices asthey like. However, each user of thatMSDN software must have an appropriateMSDN subscription license.

Example:A developer with an MSDN subscriptionuses MSDN software at work during the day, but

occasionally needs to develop at home as well, using adifferent computer. From a licensing perspective, there isno difference between a PC at work and a home PC; thehome PC is just another device on which the developer isentitled use the MSDN software.

However, the restrictions for the MSDN software runningon the developers home PC remain the same as in thework environment: the MSDN software installed on thehome PC must only be used for design, developmentand testing purposes; and only other users with anappropriate MSDN subscription can use the software.

Virtual Environments:

If a physical machine running one or mvirtual machines is used entirely fordevelopment and test, then the operatsystem used on the physical host systebe MSDN software. However, if the phmachine or any of the VMs hosted on physical system are used for productiopurposes or assigned a production licethen both the operating system withinVM and the operating system for the phost must be licensed separately. The sholds true for other software used on systemfor example, Microsoft SQL Sobtained as MSDN software can only bto support design, development, test,

demonstration scenarios.


19/29

Previous, Prerelease and Trial Versions:

MSDN subscriptions include access toprevious, current, prerelease and trialversions of Microsoft software products.No differentiation is made between theseversions; if the software is made availableas part of the users MSDN subscription,then it can be installed and used on anynumber of devices.

However, prerelease and trial versions ofsoftware provided via MSDN are subject tothe terms of the in-product EULA.

Perpetual User Rights:

Some MSDN subscriptions provide perpetual use riallow subscribers to continue using certain softwarobtained through an active subscription after thesubscription has expired. However, subscribers areentitled to updates for that software after the subshas expired, nor do they continue to have access toor product keys through MSDN Subscriber Downloother subscription services that are a benefit of havactive subscription. If a subscribers subscription exMSDN software requiring new MSDN product keys

active/running will stop working. If a MSDN subsctransferred or sold, any perpetual use rights are trato the new party and the seller can no longer use tsoftware.

Generally, MSDN subscriptions that do notprovideuser rights include: MSDN subscriptions purchased through Enterprise Ag

Subscription, Open Value Subscription, or other subscVolume Licensing programs

MSDN subscriptions offered through the Microsoft ParNetwork including the Empower for ISVs program

In the above cases, subscribers can no longer use anyprovided through the MSDN subscription after it expir


20/29

Demonstration Using TerminalServices:

MSDN subscriptions permit the use ofthe Windows Server Terminal Servicesor Remote Desktop Services to supportup to 200 simultaneous, anonymoususers for purposes of demonstratingapplications. These anonymous users

do not need an MSDN subscriptionlicense.

User Acceptance Testing:

At the end of a software development projend users (or team members acting as profor end users) typically review an applicatiodetermine whether it meets the necessary for releasea process sometimes called usacceptance testing or UAT. MSDN softwarebe accessed by end users who do not have

MSDN subscriptions for purposes of acceptesting, provided that the use of the softwaotherwise complies with all MSDN licensinterms.

Under MSDN subscription licenses, useracceptance testing must not use live produdata. If a copyof any live production data i

then that copy of the data must be discardafter the testing is complete and cannot beincorporated back into the live production


21/29

Distribution of MSDN Software as Part of an Installation Image:

Physical or virtual machine images provide a quick and convenient way to set up client or server maHowever, when MSDN software is used to create images and the MSDN subscription through whichsoftware is licensed was purchased through a retail channel, then those installation images cannot bdistributed to others. This restriction holds true even if the target users that will install and/or use thimage also have appropriate MSDN subscriptions for the MSDN software contained within the instaimage. These users can, of course, download the software from MSDN directly and create their owninstallation image.

If the MSDN subscription was obtained by an organization through a Volume Licensing program, th

installation image may be distributed amongst users licensed for the appropriate MSDN subscriptiowithin the same organization only. Redistribution of MSDN software to third-parties is not allowed iform, including physical and virtual machine images, DVD and ISO files.

Example: Company A subcontracts with Company B. Part of the work involves creating an imaginstalling machines in a test server environment. Because individuals from Company B cannotdistribute Microsoft software to individuals in Company A the only options for Company B todistribute the resulting image back to Company A are:

Company A assigns spare (unallocated) MSDN subscription licenses to the individuals in Company B that will be creating the imenables the software to be transferred within the same organization (and thus is not a distribution of Microsoft software to a 3rd

Company B provides instructions for building the image to Company A, which then builds the image internally.


22/29

Distribution of Microsoft Software Components within an Application:

Some software included with Visual Studio 2010 client editions and/or MSDN subscriptions (such asMicrosoft .NET Framework) can be distributed.

Components of software products covered by MSDN subscriptions that can be distributed (either wapplication or as separate files) without royalty are identified in the REDIST.TXT file associated with tproduct. Components that can be distributed to non-Microsoft platforms are identified in the OTHEDIST.TXT file associated with the product. Code identified as distributable that has the extension .libbe directly distributed; it must be linked into the application. However, the resulting output can bedistributed.

You may also: Modify and distribute source code and objects for code marked as sample or Code Snippet.

Distribute the unmodified output of Microsoft Merge Modules for use with an application's .msi file.

Distribute the MDAC_TYP.EXE file containing core data access components (such as the Microsoft SQL ServDB provider and ODBC driver).

Distribute the object version of C++ libraries (Microsoft Foundation Classes, Active Template Libraries, and runtimes).

For a complete list of components that can be distributed and the restrictions that apply, see Distrib

Code in the Universal License Terms section of the Microsoft Licensing Product Use Rights (PUR) or Distributable Code section of the Microsoft End User License Agreement (EULA) for MSDN subscrip
http://www.microsoftvolumelicensing.com/userights/PUR.aspxhttp://www.microsoft.com/about/legal/useterms/default.aspxhttp://www.microsoft.com/about/legal/useterms/default.aspxhttp://www.microsoftvolumelicensing.com/userights/PUR.aspxhttp://www.microsoft.com/about/legal/useterms/default.aspxhttp://www.microsoft.com/about/legal/useterms/default.aspxhttp://www.microsoftvolumelicensing.com/userights/PUR.aspx


23/29

Product Keys andInstallation Software :

MSDN subscribers can use anyinstallation software as long asthat software is from anauthorized source (such asMSDN Subscriber Downloads,Volume License Service Center,or official Microsoft DVDs) andthe software product is covered

under the users MSDNsubscription license. For example,an MSDN subscriber couldchoose to use his organizationsVolume Licensing media forinstalling Windows in a test lab,which may be more convenientdue to the Volume Licensing

build of the software havinghigher activation limits than thebuild made available throughMSDN Subscriber Downloads.

Team Foundation ServerCALs (Client Access

Licenses):

Most MSDN subscriptions(specifically Visual StudioUltimate with MSDN, VisualStudio Premium with MSDN,Visual Studio Professional withMSDN, and Visual Studio TestProfessional with MSDN) includeone Visual Studio TeamFoundation Server 2010 CAL(Client Access License), which isrequired to enter or modify datain Visual Studio Team FoundationServer 2010.

More information on TeamFoundation Server CALs isprovided later in this paper, underthe section on Visual Studio TeamFoundation Server 2010.

Team Foundationand SQL Server

Restricted-Use LThese same MSDNSubscriptions also plicense to deploy oninstance of Visual StTeam Foundation Se2010 into productiodevice, as well as a luse license to use MSQL Server 2008 StaEdition only in suppthat deployment.

More information oServer 2008 Standarrestricted use licenseprovided later in this

under the section onStudio Team FoundaServer 2010.


24/29


25/29

MSDN subscriptions that are due to expire can be

renewed cost effectively.

Renewal pricing is considerably lower than purchasinnew MSDN Subscription because the customer only p

for the ongoing right to receive new versions of thesoftware, reissuance of product keys plus other expiriMSDN services, and not the new license for the VisuaStudio client edition product, which the customer alrehas.


26/29

Retail Renewal Retail MSDN Subscriptions must be renewed annually. The renewal grace

periodthat is, the period from when the MSDN subscription expires to tpoint where the customer loses the option to renew at the renewal pricedays for Retail Licenses.

Volume Licensing Renewals

MSDN subscriptions purchased under most Volume Licensing Programs avalid until the Volume License Agreement or Enrollment terminates. Howethe Select Plus Agreement (which does not expire) is an exception. Purchaunder Select Plus last for 3 years from the date of purchase and there are options for aligning the subscription term end date with an Agreementanniversary date.

For all Volume Licensing Programs, MSDN subscription must be renewed renewing Software Assurance before the current MSDN subscription expir


27/29

Step-up LicensesStep-up Licenses enable organizations to upgrade to higher level Visual Studio 2010 cli

edition products with MSDN. Step-up Licenses are available for products purchased thrall channels exceptretail and Open License.

Step-up options include:

Upgrading from MSDN Operating Systems to Visual Studio 2010 Professional with

Upgrading from Visual Studio 2010 Professional with MSDN or Visual Studio 2010Professional with MSDN Embedded to Visual Studio 2010 Premium with MSDN.

Upgrading from Visual Studio 2010 Premium with MSDN or Visual Studio Test

Professional 2010 with MSDN to Visual Studio 2010 Ultimate with MSDN.

The cost of a Step-up License depends on when it is acquired. For example, a Step-up License that is acquired dthe second year of a three-year agreement will cost more than a Step-up License that is acquired during the thof the agreement.

A Step-up License can be acquired at any time; however, the price is the same for any point in time within a giveof an agreement. For example, a Step-up License that is acquired four months into the second year of a three-yagreement will cost the same as a Step-up License that is acquired at the beginning of the agreements second

This is a function of how Microsoft Volume Licensing works rather than anything specific to MSDN subscription Note: Open License customers who are not eligible for Step-Up Licenses within that program can still take advaStep-Up Licenses by renewing within Open Value and immediately buying Step-Up Licenses.


28/29

Renewing DownCustomers may renew down from a Visual Studio client edition with MSDN to a loweVisual Studio client edition with MSDNeffectively trading one license for another. In dso, the customer forfeits all perpetual use rights associated with the old Visual Studio pand must immediately discontinue using it. The customer also forfeits any perpetual usrights associated with other MSDN software that is not covered under the new MSDNsubscription, and must immediately discontinue using that MSDN software.

Example: An organization has been using Visual Studio Team System 2008 Developme

Edition with MSDN Premium. The organization decides to renew down to Visual StudioProfessional with MSDN Premium because they know that Microsoft will upgrade themVisual Studio 2008 Professional with MSDN Premium to Visual Studio 2010 Premium wMSDN when the product launches. When the organization renews down, it must immediscontinue using and uninstall Development Editionand thus can no longer useDevelopment Edition features such as code coverage, code metrics, profiling, and databunit testing.


29/29

Date post:	03-Apr-2018
Category:	Documents
Upload:	miguel-angel-chirinos
View:	234 times
Download:	0 times

Versiones Visual Studio 2010

Documents