You can download Release Management (RM) for Visual Studio 2013 from either your MSDN subscription or here:  http://www.microsoft.com/en-us/download/details.aspx?id=42671.  The Release Management for Visual Studio 2013 Installation guide and the Release Management for Visual Studio 2013 User Guide can help you get things set up and going.  There is also lots of information on MSDN: http://msdn.microsoft.com/en-us/library/dn217874.aspx. and in other blogs: http://nakedalm.com/category/install-and-configuration/.

What I wanted to cover is based on a usage scenario that one of my clients has when using RM.  They developed a sophisticated release process for deploying changes into their development teams’ environments.  They did these changes through RM and they treated the development teams’ environments as “Production”.  To build out the release pipeline and vet changes to their release process, they constructed a “Development” environment configured with its own RM server instance.

RM uses a client application to manage and construct the release pipeline, server connections, other administrative settings, etc.  Below is an example.

The problem that my client had (as currently configured by the installation process) was the inability to bring up two RM clients at the same time that pointed to the different Production and Development RM servers and compare setting across them.  Ideally, there should be some import/export mechanism to move release pipelines and other configuration across servers and this is in user voice: http://visualstudio.uservoice.com/forums/121579-visual-studio/category/66944-release-management.

In the meantime, there is a work around to allow this behavior.  First, the client is not particular about where it executes from since it does not rely on any assemblies being deployed to the GAC.  If you copy an installed client elsewhere on the same machine, it will still run.  You can then configure the two clients instance to point to different RM servers.  That will work great, but as you attempt to bring them both up at the same time, you will find that the last instance executed always wins by closing the other.

The way to bring up multiple clients is just a simple configuration change in the ReleaseManagementConsole.exe.config file located in C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\bin.  In the configuration file, you will see the following applicationSettings section:

<!-- Application Settings Configuration -->
  <applicationSettings>
    <Microsoft.VisualStudio.Release.Console.Properties.Settings>
      <setting name="AllowMultipleInstances" serializeAs="String">
        <value>False</value>
      </setting>
      <setting name="DisableSplashScreen" serializeAs="String">
        <value>False</value>
      </setting>
      <setting name="UseCustomCulture" serializeAs="String">
        <value>False</value>
      </setting>
      <setting name="CustomCulture" serializeAs="String">
        <value>en-US</value>
      </setting>
    </Microsoft.VisualStudio.Release.Console.Pro

The key here is the AllowMultipleInstances setting which is False by default.  Changing the setting to True in both of the  client instances will allow for each to be brought up at the same time and then you can dock them side by side and compare/verify/change settings as required. 

Hopefully this helps someone else with the same need.  Let me know if you have any questions…

To get started, I wanted to share the some information I provided one of my clients that wanted to understand how to use the capabilities inside of Visual Studio 2013 Ultimate for load testing SharePoint 2013 sites. The current MSDN documentation on the subject is located at Web performance and load testing SharePoint 2010 and 2013 applications (http://msdn.microsoft.com/en-us/library/jj710162.aspx).  However, the examples are all in terms of testing SharePoint 2010 sites.  I developed the demonstrations for them and discovered some differences that you need to be aware of when testing SharePoint 2013 sites.  So today, I want to start on a series of posts that cover how to use Visual Studio 2013 Ultimate to do performance and load testing against SharePoint 2013 and discuss some of the differences. Specifically, I will walk you through a series of standard use cases in SharePoint (upload files, download files, etc.) and show how you:

1. Record the web performance tests
2. Make the web performance test ready for playback
   • Extraction and validation rules
   • Data source for data driving test
3. Author a load test using the web performance test

The first scenario that we are going to cover is how to create a web performance test for uploading a file to one or more SharePoint Site Collections with one or more Document Libraries. To make it easy for you to follow along, I’ve created a PowerShell script that will create a base set of Site Collections and Document Libraries (see at end of post).  Below is an image of the LTDEmo1 site collection that I created with the standard Shared Documents library (Documents) and an additional five document libraries named DocLib1 - DocLib5.  There is a second LTDemo2 collection with the same set of document libraries that will be used for making sure that the web performance test covers multiple sites and multiple document libraries.

You first start out by selecting a web and performance load test project in Visual studio 2013 Ultimate by File->New Project and selecting the Test node under your language of choice (Visual C# or Visual Basic).  The language choice is really only important if you decide to generated code from your recorded tests.  For all the normal types of operations, Visual Studio provides you with a declarative approach to building out the test, 

You give the project a name such as SPWebAndLoadTestProject, browse to a location to store the project on disk (optional), and then click the OK button.  After a brief interval, you will be presented with a project with a default test named WebTest1.webtest.

At this point, you click on the red record button as shown below

and this will bring up Internet Explorer with the Web Test Recorder visible.

Then walk through the following steps to record a file upload in the DocLib1 document library.

1. Enter the address of your site collection into the browser address bar.  This was http://demo1/sites/LTDemo1 for the test case I created here.
2. Select the link for the DocLib1 document library.  This will bring up the AllItems.aspx page.
3. On the AllItems page, click the new document link to bring up a a web dialog to select a file to upload.
4. Browse to the file you want to upload and save it.  When the file is uploaded, your browser will look similar to below.

Click the Stop button in the Web Test Recorder to complete the test and have Visual Studio start automatically removing noise requests and searching for dynamic parameters that need to be accounted for with extraction rules.

Accept the Dynamic Parameters listed in the Promote Dynamic Parameters to Web Test Parameters dialog – _REQUESTDIGEST, _VIEWSTATE, _EVENTVALIDATION.  You will then have an initial Web Performance test with the HTTP requests that mirrored your user interaction with the browser to upload the file to the DocLib1 document library. See the image below where  I have also renamed the test to Upload to better distinguish it.

The first thing you want to deal with is the SiteName1 and SiteName2 context parameters.  The test has them as the extracted values of the site collection and document library used in recording the test.  The webtest will substitute these values where these context parameters appear in the HTTP request.  For example, http://demo1/sites/{{SiteName1}}/{{SiteName2}}/Home.aspx becomes http://demo1/sites/LTDemo1/DocLib1/Home.aspx.  Fixing this requires that we add a data source to the test.  This is easily done in the test window by selecting the database symbol with a plus on it or right-clicking on the test name an selecting Add Data Source.  When you do so, the New Test Data Source  Wizard dialog displays giving you the opportunity toe name the data source and to select from three different data source types – Database, CSV File and XML File.  See Add a data source to a web performance test for more information.

I used a CSV file that contained the following information based on my earlier experiments.  You notice that I have an additional column beyond the two expected sets of values for site and list name  that I will discuss later.  I’ve also encoded the “space” using “%20” in the Shared Documents list name so that I remove any potential issues.

Using this data source, I will have 12 different combinations of site collection and document library (2 site collections x 6 document libraries).  If I want to test that all of my data source combinations work correctly before load testing, I am going to add a loop counter to the web test so that I can verify all of the combinations are exercised and determine if there will be any issues in running the tests.  To add a loop, you simply right-click on the top-level web test node and select Add Loop … which will bring up a list of loop types.  I want to run through 12 data values so I select a Counting Loop.

In the Counting Loop, I configure the Advance Data Cursor to true.  If I did not do so, I would take the first data value from the data source for each iteration of the loop.  I will show you an example of what is looks like when you don’t set the cursor update to true a bit below.  Next, I set the Number of Iterations to 12 for the 12 data values in the data source.  Then I finish be choosing the first and last item corresponding to my requests that will represent the requests to be looped through.  When I click the OK button, I have the loop added t the web test as shown below.

The last step is to now to substitute the values in the data source for the correct parameters in the web test.  Again, we make this pretty simple by right-clicking on the web test and selecting the Find and Replace in Request menu item.This will bring up a dialog box for you to specify what to find and what to replace it with.

Here we are first going to replace the SiteName1 parameter.  In the web requests you will notice that it is enclosed in double curly braces -- {{ }}.  All substitutable parameters in a web test are enclosed in double curly braces.  What we want to do is replace this value with the corresponding value in our data source.  We use dot notation to get to the correct value in the data source file – <Data Source Name>.<Data Source File Name>.<Data Source Field Name>.  We use the SiteName filed in the SiteAndListNames  csv file associated with the SitesAndListNames data source for the values we want to substitute for the SiteName1 parameter.

In a similar manner, we use the ListName field in the data source to substitute for the SiteName2 parameter that corresponds to the document library.

At this point, I can run the test and observer the responses for each of the requests. Here I notice that everything passes but upon closer inspection, I find that I was uploading the same file (SharePoint Load Test Demo.docx) to the same site and document library.  I had forgotten to advance the data cursor when I first ran this.

However, no errors occurred due to prompting for uploading an already existing file.  As I look at the actual documents in the document library, I see that each has a different file name that is a GUID prefix to the original document name.  That explains why there were not errors, but how did that happen?

To understand what happened, we need to examine the web test Form Post parameter for the UploadEx.aspx page where the actual file upload operation takes place.  If we scroll down and look at the properties of the File Upload Parameter, we see that the Unique Name  property has been automagically set for us so that unique names will be generated and they will be prefixed by GUIDs (the other option that cab be chose is large random integer values).

So, correcting my data cursor to advance and rerunning the test again, we get the following results.  There are failures in 10 of the 12 iterations.

As I start troubleshooting the test, I look at the Details tab of the AllItems.aspx page request and observe that the Extraction rule was looking for the DocLib1 string in the ctx.ListTitle context parameter.  Well that only happens twice in the data source which explains why only two of the iterations passed.

What I need to do to fix the issue is to go into the properties of the SharePoint – Extract WebParts ListView Values rule of the AllItems.aspx page request and

change the List Title value to that third column value in the data source – ListTitle.  Remember, I mentioned we would need this later?

Now, when I rerun the test, the extraction rule finds the correct List Title and puts in the correct context parameter value. 

All 12 loop iterations pass and documents with GUID prefixed file names have been uploaded to Shared Documents and DocLib1..5 document libraries.  Below is a view of the two different site collections populated for two document libraries with the DocLib2 name.

Now that I know that my data source values will be iterated through correctly, I can remove the loop so that I have my first baseline file upload web test for use when I construct my load test. 

That concludes this post.  The next post in the series will walk through recording and debugging a web test that uploads a file to a SharePoint 2013 document library.  Let me know if you have any questions…

Team Foundation Server 2012 introduces a number of new features.  One highlight is the redesigned Web Access which includes new Agile Planning tools.   See these products in action here!

Note that the standard, updated Web Access is part of TFS 2012 and licensed via the TFS CAL (just as it was in earlier versions of TFS).  However, the new Backlog/Spring Management features, located on the updated Web Access site, require an additional license.  Once you have the appropriate license, the features can be enabled via TFS user permission settings, which are not enabled by default.

More specifically, with a TFS CAL you can access/use any part of the Web Access interface EXCEPT the “Product Backlog Tab” where backlog management and Agile planning is done.  To use these features, you personally must be licensed with VS Test Professional ($), VS Premium ($$) or VS Ultimate ($$$).

So, these screens/features DO require one of the additional VS licenses above, in addition to a CAL:

Again, See these products in action here.

This shows some new features in TFS 2012 that require ONLY A TFS CAL (i.e. no additional VS license).  These are in addition to the standard TFS functionality like viewing/editing Work-Items, browsing source, etc:

 For more info, go here.

 Another way to think of it... TFS 2012 Web Access now has 3 levels of user permissions that tie to three license options: 

• Limited   (no TFS CAL required)
• View My Work Items

• Standard   (TFS CAL required)
• View My Work Items
• View All Work Items
• Standard Features
• Agile Boards (second part of above)

• Full   (VS Ult, Prem or TestPro with MSDN required (TFS CAL is included in MSDN by default)
• View My Work Items
• View All Work Items
• Standard Features
• Agile Boards  (second part of above)
• Backlog and Sprint Planning Tools  (first part of above)
• Request and Manage Feedback  (first part of above)

For more on TFS licensing concepts see this previous post. 

Team Foundation Server (TFS) is an excellent code version control tool AND the hub of Microsoft’s App Lifecycle Mgt. (ALM) solution. Learn more here.

Now, let’s attempt to demystify some of the aspects of licensing of TFS for enterprise use now:

As illustrated in the below graphic, TFS is licensed on a Server/CAL model. Thus, you need 1 Server license for the TFS server and 1 TFS CAL (client access license) for each user that will use TFS features. That TFS CAL covers the usage no matter how the user accesses TFS (i.e. Visual Studio, Eclipse, Web Access client, Excel, MSProject, 3rd party tool, ect, etc).

 The two ways to acquire TFS CALs are:

   1) Purchase a TFS User CAL   (sku: 126-00196)

   2) 1 TFS CAL (and 1 TFS Server license) is included in each Visual Studio/MSDN subscription. Thus, anyone who has an active MSDN subscription assigned to them is covered with a TFS CAL.

*CLICK TO EXPAND IMAGE* 

Finally, there is one exception to the TFS User CAL.   To enable organizations to have an enterprise/central way to capture enhancements requests & bugs from the user population, TFS provides a Work-Item only version of the Team Web Interface.  There are also additional non-CAL capablities around viewing reports coming for TFS 2012.

To read more specfics on all VS/TFS/MSDN licensing... check out the Visual Studio & MSDN Licensing WhitePaper.

MSDN Subscriptions are purchased as an add-on to Visual Studio Professional, Premium or Ultimate.  While the MSDN Subscription provides a whole list of benefits, this post specifically explores the software for dev/test use benefit.

An MSDN subscription license gives a single user the ability to access/use any Microsoft Enterprise product for Dev/Test purposes (i.e. WinServer, SQL Server, BizTalk, SharePoint, Dynamics, etc, etc, etc).  The list of software titles included depends on the level of your subscription.  For example, VS Professional with MSDN only includes SQL Server & Windows only.  Compare here.

Beyond giving a single developer a bunch of cool software… providing an MSDN subscription for all of the Developer and QA team provides an efficient, per-user, license model for your entire Dev & Test environments.  Adopting this model means you do not have to purchase any stand-alone Microsoft products for pre-production.    The MSDN Subscription licenses each user for unlimited installs and instances of the products on their local, shared and virtualized
environments.

Expand this graphic for an illustration of the model:

 -CLICK TO EXPAND IMAGE-

Once you understand that concept, the next question is generally…  Which MSDN Subscription level (Pro, Prem, Ult) do I need?    The answer
to that is fairly simple with these two questions…

 1)     Does the Dev/Test environment only contain Windows and SQL Server?    If yes, Professional is sufficient.

2)     Does the Dev/Test environment contain additional Microsoft products beyond Windows and SQL Server (i.e. SharePoint, Dynamics, Biztalk, Visio, MSProject, etc)?    If yes, you need Premium or Ultimate.

I hope you found our sessions on various Microsoft Development topics at FOSE informative and we thank you for attending.    As promised, here are links to download the slides and a few other items worth checking out!

Download the Slides:

• Beyond Source Control – App Lifecycle Management
• Introducing Visual Studio and TFS 11 (Beta)
• Got TFS? - Bring the QA team into the fold with Microsoft Test Professional.
• Take the Windows 8 Metro: An introduction to app dev in Windows 8
• SharePoint as a Development Platform in Federal Government
• Applications Under Attack – Secure Development Lifecycle
• Agile development in the Government/Waterfall world.

 Documentation:

• Visual Studio ALM
• Visual Studio 11
• GovDev for TFS Accelerator
• Download VS-TFS Virtual Machines
• Secure Development Lifecycle (SDL)

 Purchase Promotions through June:

• Current Discounts Page
• Contact me about 15-30% discounts on VS Step-ups

Please contact me with any questions.

Thanks!

Brian Hurst
Developer/ALM Specialist
Microsoft Federal
bhurst@microsoft.com
703-489-2635

If you're interested in learning more about the new open-source GovDev for TFS Accelerator, please join us for an upcoming live Webcast…

 To download the free GovDev for TFS Accelerator, visit http://govdevfortfs.codeplex.com

Microsoft Team Foundation Server (TFS) 2010 is the collaboration platform at the core of Microsoft’s application lifecycle management solution. In addition to core features like source control, build automation and work-item tracking, TFS enables teams to align projects with industry processes such as Agile, Scrum and CMMi via the use of customable XML Process Templates.  

Since 2005, TFS has been a welcomed addition to the Microsoft developer tool line-up by Government Agencies of all sizes and missions.  However, many government development teams consistently struggle with leveraging an iterative development process all while providing the structure, visibility and status reporting that is required by many Government, waterfall-centric, project methodologies.

The open-source, GovDev for TFS Accelerator contains a TFS Process Template that combines the formality of CMMi/Waterfall with the flexibility of Agile/Iterative: 

The GovDev for TFS Accelerator also implements two new custom reports to support the customized process and provide the real-time visibility across the lifecycle with full traceability and drill down to tasks, tests and code:

Finally, due to the heavy use of contractors within Government projects, the need for new ways to understand work contribution are always needed.   Here is a new one:

To download the free GovDev for TFS 2010 Accelerator, please visit:   http://govdevfortfs.codeplex.com

To watch a 45min demo of GovDev, visit:  https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032508359&culture=en-us

GovDevTFS-Overview-V1beta.pptx

All of the scheduled Webcasts have been completed.  For a full list of upcoming Webcasts and recommended On-Demand resources see:

GovDev Montly Calendar Blog

and/or

The Microsoft Public Sector Developers Blog

Thanks!

An MSDN Subscription often is the source of confusion for both IT Professionals and IT Purchasing folks, so this post will attempt “Demystify the MSDN Subscription” into terms that all parties can understand.  Here we go…

1)      Visual Studio’s Software Assurance- MSDN is only purchased as an add-on to a Visual Studio license.  Having an active MSDN Subscription with Visual Studio means that you have access to all past & future versions of Visual Studio (i.e. 2003-2005-2008-2010-20??) *Note that Software Assurance is a requirement for all purchases on a Microsoft Enterprise Agreement (EA), thus MSDN is a requirement for all Visual Studio licenses purchased on an EA.

2)      Dev/Test Environment licenses- MSDN gives the user the ability to access/use any Microsoft Enterprise product for Dev/Test purposes (i.e. WinServer, SQL Server, BizTalk, SharePoint, Dynamics, Visio, MSProject, Office, etc).   This allows you to build out robust dev/test environments without having to pay for any of the individual software… Rather just give each of the Developers/Testers an MSDN Subscription and you’re fully covered for any products.  Explore this in more detail here!

3)      Team Foundation Server (TFS) – As of April 2010… a full TFS license AND TFS CAL is now included within all levels of MSDN Subscriptions.  Thus if you are purchasing MSDN with Visual Studio, everyone is licensed for TFS.   For folks on the SDLC team that do not have MSDN subs (i.e. PMs, Bus Analysts, etc), you can still buy stand-alone CALs for TFS.  More here.

4)    Team Foundation Service - Launched in October 2012, TF-Service is full Team Foundation Server 2012 functionality delivered via the cloud.  Full licensing for the service is provided in Vs/MSDN Premium & Ultimate.  Learn more and start a new project here.

5)      eLearning Classes – User gets approx. 20-40 Hours of online training per calendar year.  (~$3500 value)

6)      Tech Support Calls - Each MSDN includes 2-4 tech support incidents. ($250 each value)

7)      Azure Development: Wana get on the Cloud?  MSDN includes a monthly allowance of Azure compute and storage.

So as you can see, there is a lot there!   The value of point #2 is almost impossible to quantify because there are literally thousands of software titles available, not to mention, early access to new products and tools. 

Finally, the Visual Studio & MSDN Licensing WhitePaper is a great resource for answering many of your licensing questions.   To understand the difference between MSDN and TechNet, see here.