Campbell Lowitood – March 08, 2022

An Internal Error Occurred During: Refreshing Shelvesets. Download Url Must Not Be Null

Home / Making Developers More than Productive with Azure DevOps Server 2019

Overview

This lab is all about those "fit-and-finish" scenarios in Azure DevOps Server that will make developers more productive every bit they write code and collaborate with other team members. You'll acquire about integrated code reviews; the "My Piece of work" feel for managing your active tasks; and once you're "in the zone", Visual Studio will now help you stay focused on the chore at paw, no matter how much you're randomized, with a append/resume experience. Yous'll also larn how to work offline seamlessly, how the new merging experience works, and how you lot can more hands detect work items.

Prerequisites

In lodge to complete this lab y'all will demand the Azure DevOps Server 2019 virtual machine provided by Microsoft. Click the button beneath to launch the virtual machine on the Microsoft Easily-on-Labs portal.

Launch the virtual auto

Alternatively, you tin download the virtual machine from here.

About the Fabrikam Fiber Scenario

This set of hands-on-labs uses a fictional company, Fabrikam Fiber, as a properties to the scenarios you are learning nearly. Fabrikam Fiber provides cable television and related services to the United States. They are growing rapidly and accept embraced Windows Azure to scale their customer-facing web site directly to end-users to allow them to self-service tickets and runway technicians. They also utilise an on-premises ASP.NET MVC application for their client service representatives to administrate client orders.

In this set of easily-on labs, you will take part in a number of scenarios that involve the development and testing team at Fabrikam Fiber. The squad, which consists of viii-10 people has decided to employ Visual Studio application lifecycle direction tools to manage their source code, run their builds, test their web sites, and plan and runway the projection.

Exercise 1: Making Developers More Productive with Azure DevOps Server 2019

Chore i: Squad Explorer Overview

In this practise, you will see a high-level view of the changes made to Squad Explorer in this release and learn how to navigate the functionality that is made available there. If you are new to Azure DevOps Server, y'all tin can think of Team Explorer as the primary way in which a Visual Studio user accesses Azure DevOps Server functionality.

Log in every bit Sachin Raj (VSALM\Sachin). All user passwords are P2ssw0rd.
Launch Visual Studio from the taskbar.
Open the FabrikamFiber project listed on the Start Page.
The Team Explorer window provides a fundamental hub for common tasks that developers undertake when working on a projection, including source control, piece of work particular tracking, collaboration features such as lawmaking review and squad rooms, and fifty-fifty quick links to other resource found in the spider web portal such as task board.
Navigation inside Team Explorer operates similarly to a typical spider web awarding in that y'all follow links from the domicile screen, and can navigate backwards and frontwards or render home at whatever fourth dimension. We will put this navigation to apply in the next do, as well every bit drill into the various hubs and pages exposed within Squad Explorer. When this lab refers to the Dorsum or Home buttons, these are the ones.
Click Piece of work Items.
The Work Items view shows favorite queries for the logged-in user and the team, every bit well as provides the capability to add new queries and work items.
Click the Domicile push button.
Click Source Command Explorer. This provides a view into everything stored in source control, equally well every bit its local condition.
Click Settings to view the team project and team project collection options.
Click the Home button.
Click Builds to manage build definitions and view build history.
We will look at the new My Work functionality in the remaining exercises.

Chore two: My Piece of work

In this exercise, you will learn about the new My Piece of work experience for managing your active tasks.
Click the Home button.
In Team Explorer - Home, click My Piece of work.
The My Work node shows piece of work items in progress, available work items, and suspended and shelved piece of work for the currently logged in user. This workflow uses a chore-based development model to help keep team members in-sync with each other.
Click the Open Query hyperlink that is located in the Bachelor Piece of work Items section. This will open a new browser window to the query on Azure DevOps.
Select the Editor tab. You can review all of the details and flexibility available to customize any query.
Shut the query browser window without saving changes.
Permit's say that we want to work on i of our available work items. On the My Work folio in Team Explorer, right-click the item that starts with "Write code to get GPS location…" and cull the Add together to In Progress choice from the context carte. This communicates the current country of the work particular to our team.

Chore iii: Local Workspaces

In this practice, you will learn about local workspaces and how they ameliorate the offline development experience.
In Source Control Explorer, double-click on the FabrikamFiber.CallCenter.sln file in the Dev co-operative to open it.
Server-based workspaces used to be the only option available in Azure DevOps Server (prior to Squad Foundation Server 2012). With server workspaces, source command operations are performed exclusively on the server, so working in a disconnected, offline scenario can be slow. Local workspaces, which are at present default, improve the development experience for smaller teams and projects. They provide a more than client-centric workflow, a manner of version control often described as Modify-Merge-Commit.
As an aside, server-based workspaces, which are better suited for larger projects, can certainly still be used if desired. Load the Manage Workspaces window by typing 'workspaces' into the Quick Launch search box in the height-correct corner of Visual Studio and wait a second or two for the results to load. Select the Workspaces… control link.

Note: The Quick Launch search box can be used to observe near of the settings, tools, and windows bachelor in Visual Studio, no matter where they are constitute, saving yous precious time clicking through menus. Apply the Ctrl+Q key combination to avoid the mouse altogether.
In the Manage Workspaces window, click Add… to start creating a new workspace.
In the Add Workspace window, click Avant-garde to see all bachelor options.
Locate the Location workspace property. By default, new workspaces will apply local workspaces, merely you tin choose to create a server-based workspace if desired.
Shut the workspace windows by pressing the Esc key twice.
In Solution Explorer, expand the FabrikamFiber.Web\Content folder.
Select fullcalendar.css to view its contents. Note that the file is loaded in the CSS Source Editor as expected, but the tab for it is shown on the correct-hand side. This new tab type is called a preview tab - as you use the arrow keys to navigate between files or single-click on them, the preview tab will exist replaced with the most recent selection. Preview tabs help accost the problem where you tin can hands overwhelm your Visual Studio tab real manor with files that you lot only demand temporarily.

Note: There is a button on the preview tab itself that allows y'all promote information technology to a regular tab (see the arrow in the screenshot above).
Make an capricious change to the fullcalendar.css file by changing one of the mode properties. Visual Studio will indicate that the file has been checked out, merely go on in mind that this has only been done in the local workspace. Other team members volition not see that you are working on this file.
Ii of the major benefits of the local workspaces are that the disconnected, offline work scenario is greatly improved, and information technology is much easier to apply external tools to work with files in source control. To demonstrate both of these benefits in action, allow'southward proceed by stopping the Azure DevOps Server site in IIS. This will simulate a scenario where you are working offline, such as writing code from the embankment. In a real-world scenario, you would never write code from the beach - yous would exist enjoying your vacation.
Launch Internet Information Services (IIS) Manager.
In IIS Managing director, expand the VSALM server node and the Sites node to notice and select the Azure DevOps Server site. Right-click it and select Manage Website | Stop.
Render to Visual Studio, load the Source Control Explorer window, and click the refresh button. Annotation that the window is now in a disconnected land. You may likewise become an fault indicating the same, which you can dismiss.
Even though we are now in a asunder state with Azure DevOps Server, we can continue to do piece of work. Right-click the Content folder in Solution Explorer and select the Open up Folder in File Explorer selection.
Add together a new file into the Content folder by right-clicking in a blank surface area of the view and selecting New | Text Document from the context menu. Have the default proper name.

Notation: Nosotros will employ this file in a sit-in a piffling later - the contents are non important and can be left blank.
In the Explorer window, correct-click Site.css and select Open up With | Notepad from the context menu.
In Notepad, change the "body" fashion colour to "red".
In Notepad, save and close Site.css and return to Solution Explorer. Note that Visual Studio detected the modify to the file and that the file was non read-only as it would have been in the example of a server-based workspace.

Task four: Pending Changes

Click Dwelling house in Squad Explorer, then click Pending Changes.

Note: Yous should see an error message in the Pending Changes window nigh being unable to connect to the remote server, but you can simply ignore it. We purposefully stopped Azure DevOps Server during the previous do.
In the Pending Changes window, we can come across that the ii changes fabricated to existing files in the previous practise automatically show upward under the Included Changes department. Note that due to NuGet updates, you may encounter boosted changes detected.
In the Excluded Changes section, there is a detected alter that was non automatically marked as an included change. Note that there may be more adds detected due to NuGet references. Click the Detected link.
In the Promote Candidate Changes window, you tin can see the add-on of the new text document. If at that place are boosted items, uncheck all items using the header checkbox and so check just New Text Document.txt. Click Promote to move it to the fix of changes that we want to include in the next bank check-in.
You lot should now come across three included changes.
Although we could continue to piece of work on our project while offline, note that we can't perform a check-in at this time as the Check In push is currently disabled.
In the Internet Information Services (IIS) Manager window, correct-click the Azure DevOps Server site and select Manage Website | Starting time.
Return to Visual Studio and so click the refresh push button in the Team Explorer - Pending Changes window. We should now exist working in a connected state again with the Check In button enabled once again. Do not cheque in your changes yet.

Task 5: Append and Resume

Another common only unavoidable difficulty faced by developers is context switching between different tasks. In past versions of Azure DevOps Server, this was addressed with Shelvesets that would preserve your changes on the server even if you weren't gear up to check those into source command. In more contempo versions, this has been taken one step further with the Append and Resume features - in add-on to creating a shelveset of changes, some other data similar breakpoints and tool window positions are also saved locally.

We brainstorm this task in the state that nosotros concluded the previous exercise in - nosotros take a fix of pending changes to be made as part of the work that we have in progress. Load the My Work window in Team Explorer to view the work that is in progress.
As part of this scenario, imagine that we also take some other debugging tool windows open and a break point set as we debug lawmaking that we are writing. Open FabrikamFiber.Web\Controllers**HomeController.cs** and set a breakpoint to the first line in the HomeController constructor.
Open the Immediate window from Debug | Windows | Immediate.
Now imagine that your boss asks you to finish working on the current task, and work on a high-priority issues instead. We currently have a lot of time invested in getting Visual Studio debugging tools in identify, and nosotros would like to be able to render to this electric current context after the issues prepare is complete.
Press Ctrl+Shift+S to save all open files.
In Team Explorer, navigate to the My Work screen, select the Suspend driblet-down, and then click Append. Nosotros could alter the description, but since we are currently working on a piece of work item, it is pre-populated for us.
Clear out all breakpoints by pressing Ctrl+Shift+F9, and then click Yes to ostend the activity.
Close all certificate windows by selecting Window | Close All Documents from the principal menu.
Reset to the default window layout by selecting Window | Reset Window Layout from the chief menu. Click Yeah when asked to confirm the activeness.
At this point, yous should have a very clean looking workspace and the previous task that you were working on should be listed in the Suspended Work section of the My Work window.
Annotation the search box for work items at the pinnacle of the Team Explorer window. This will perform a search of all work items in the currently selected team projection. Blazon "Canadian" into the search box and printing the Enter cardinal to locate the loftier-priority problems that you have been asked to work on.

Notation: This quick search functionality searches the team project Title, Description, and Repro Steps fields by default for the keyword provided. You can also click the drop-down pointer to show your search history, and to add search parameters for metadata such as work item type, or whom the work item is assigned to.
Double-click the problems titled "Customers with Canadian addresses not displaying properly".
In the new browser window displaying the form for the bug, select the Links tab to view the linked work items. Note that in that location are 2 kid tasks.
Imagine that other team members are tackling these child tasks already, only that we know of some other problem related to the parent bug that also needs to exist fixed. Select Add link | New item to add a new task.
For the new linked work detail, select a Work particular blazon of Task, enter a Title of "Set up RegEx for Zip code property", and so click OK.
Assign the new task to Sachin Raj so click Relieve and shut.
Return to the Team Explorer - My Work window.
Y'all should at present meet the new task appear in the Available Piece of work Items section.
Correct-click the new task entitled "Fix RegEx for Zilch code property", and and so select Add to In Progress.
In Solution Explorer, open FabrikamFiber.DAL\Models\Address.cs.
The Zilch holding is currently using an incorrect regular expression information annotation, with the result being that users of the web application can enter invalid postal codes for Canadian addresses.
Permit'southward presume that the correct ready is to update the regular expression. Comment out the existing regular expression and so un-comment the other ane.
Press Ctrl+S to relieve the changes to the file.

Task half-dozen: Code Reviews

Now that the set has been made, let'due south ask Clemri to perform a code review on the changes to brand sure things look correct. In Team Explorer - My Work, click the Request Review link.
Type Clemri Steyn for the proper noun of the reviewer and then press the Enter key, type a description of "delight check my regular expression change", and so click Submit Request. You can dismiss any warnings.
Open a remote desktop session to VSALM and log in every bit VSALM\Clemri to perform the lawmaking review. The password for all users in this virtual machine is P2ssw0rd. Note that yous tin can then minimize and restore the session later on when switching betwixt accounts.
Launch Visual Studio and open FabrikamFiber.CallCenter.sln from the Start Folio.
Open Team Explorer, and navigate to My Work. The new lawmaking review asking is shown under the Lawmaking Reviews section at the lesser. Filter for Incoming Requests.
Double-click the code review asking to open the Code Review window. This view allows Clemri Steyn to see a lot of information regarding the request so that he is able to decide whether he volition accept or reject the task. He can view the entire shelveset of changes, run into the other reviewers or even add together someone to the reviewers list, see the related piece of work items, comments related to the lawmaking review request, and finally the ability to evidence a diff view for all of the inverse files with a unmarried click.
In the Code Review window, click the Accept link to starting time working on the code review.
Click Accost.cs from the comments section to open it with the inline diff tool.
We are now viewing the changes using the default side-by-side comparison mode. Red background colors represent changes in the old version (left) and green colors stand for changes in the new version (right). Note the fable available at the bottom of the comparison view.
In the Compare Files toolbar, select the compare mode drop down button to view the diverse display modes that the diff viewer tin can use. Try out a few of the unlike modes.

Notation: If the Compare Files toolbar is non open, open up information technology from View | Toolbars | Compare Files from the main carte in Visual Studio.
Allow'southward assume that nosotros hold that the changes are correct, and so let's ahead and add a review-level comment to that effect. Click the Reply link underneath Sachin's bulletin.
For the comment, enter "this looks good" and then click Salvage.
Note that the new comment has the text "Unsent" adjacent to it. The annotate will not be sent until Clemri is done with the review.
You tin also comment individual files and blocks of code with comments. In the unequal viewer, use the mouse to highlight the Cypher property name, correct-click, and select Add together Comment from the context carte du jour.
In the comment box, enter "Consider renaming to PostalCode" and so click Salve.
Click Send Comments virtually the top of the Code Review window to send the comments that we have batched upwardly so far. Having the ability to send comments back right away tin be benign for a code review that requires more work than this ane. If the reviewer finds an issue, the developer tin can immediately start fixing the issue rather than waiting for the reviewer to cease.
Select the Send & Finish drib downwards followed by the Looks Good option to end the code review.
Switch users back to Sachin in one case once more by minimizing the RDP session.
Return to Team Explorer - My Work and double-click the lawmaking review item to open it.
In Team Explorer - Code Review, note that Clemri finished his review and had comments.
For this scenario, let's say that we are washed with the lawmaking review process. Select Close Review | Consummate.
Now that we are confident that nosotros take fixed the loftier priority bug, we can cheque-in the changes. Click the Check In link to load the Pending Changes window and and so click the Check In button to consummate the task. Click Yes if asked to arrange check-in.
Now we can return to the code that nosotros were originally working on before we were interrupted by the issues fix. In the My Work window, right-click the job listed under the Suspended Work department, and then select the Resume selection from the context menu.
After the shelveset is opened and the task context is restored, you will notice that the certificate windows and tools windows, likewise as their positions, are restored to the state that nosotros left them in when we suspended this task. Although you won't notice this in a virtual auto, had you been using multiple monitors you lot would accept besides noticed that all of the tool windows would be opened on their respective monitors. This capability allows you to quickly arrive and out of tasks to help you bargain with the frequent interruptions that many of united states face on a daily basis.

Chore seven: Merging

You should still exist logged in as Sachin from the previous do.
In Team Explorer - Pending Changes, you should come across three changes listed nether the Included Changes section. Double-click Site.css to open it.
You may think that that nosotros previously changed the torso color holding to red. Now we will accept a expect at what happens if another user makes a unlike change to the same file and then checks it in.
Switch back to the Clemri Steyn RDP session.
From Solution Explorer, open FabrikamFiber.Web\Content\Site.css.
Permit'southward make a dissimilar alter than Sachin is going to make, so change the body font-size belongings from .9em to .5em.
Press Ctrl+Shift+South to save all documents.
In Team Explorer - Pending Changes, click Check In. If yous are prompted to ostend the check-in, please do then.
Switch users back to Sachin once once more.
In Solution Explorer, right-click Site.css and select Get Latest Version from the context menu.
In Site.css file, note that the torso font-size property has been updated with Clemri'south change, just that nosotros likewise still take our current change where we updated the colour belongings to blood-red. This demonstrates that, wherever possible, Azure DevOps Server and Visual Studio endeavour to auto-merge changes, rather than needing the user to be involved with the merge procedure. This tin save y'all several steps when compared to previous versions.
Switch users back to Clemri Steyn.
Allow'south create a alter that will forcefulness a manual merge procedure. In Site.css , modify the trunk color property to black.
Press Ctrl+Shift+S to save all documents.
Check in the pending modify.
Switch users dorsum to Sachin.
Imagine that Sachin is blissfully unaware that Clemri has changed the trunk color property to black. In Solution Explorer, right-click on Site.css and select Get Latest Version from the context menu. This will load the Resolve Conflicts window.
Click Merge Changes In Merge Tool to begin the manual merge process. If you are prompted to save and close Site.css, go ahead and click Yes to go on.
The new merge procedure also uses the integrated diff viewer. By default, the merge view uses a side-past-side view to show the changes. Notation that you can see that the server version (left) has the black color, the local version (correct) has the cerise color, and the result (below) currently shows the original colour.
Permit's go with server version. Select the checkbox to the left of the body color property pick that uses blackness (in the left pane).
In the Merge Toolbar, click the Have Merge button.

Job 8: Updating a Source Command Co-operative

Open the Source Control Explorer window by selecting the Source Command Explorer tile.
The Fabrikam Fiber projection contains a main code base of operations (under Principal), a development code base of operations (nether Dev), as well every bit release branches (nether Releases). Branches are fantabulous objects that are represented with their own icon in Source Control Explorer.
Expand the Releases node and right-click Release1 to select Advanced | Properties from the context card.
The Properties window provides full general details like version and description, hierarchical human relationship to other branches, and permissions.
Press Esc to return to Source Control Explorer.
Expand the Release1 branch node in the Releases binder and locate the FabrikamFiber.CallCenter.sln solution file in the FabrikamFiber.CallCenter binder. Double-click to open it.
Printing F5 to build and launch the Fabrikam Fiber intranet portal.
Imagine a scenario where the Release1 branch represents the lawmaking that is currently running on the product web server. Management has decided that the non-functional links under the profile section on the left side of the folio should be removed as soon equally possible. We take decided to "fast track" this modify past making the update directly to the Release1 co-operative. Later, you volition see how we can merge this modify back to the Dev co-operative and so that it becomes a part of the changes we're working on for the next release.
Close the Internet Explorer window and return to Visual Studio.
Our first task is to update the Release1 branch and deploy the changes to the production spider web server. From Solution Explorer, open up FabrikamFiber.Web\Views\Shared_Profile.cshtml.
Comment out the admin links section as shown below.
Press F5 to launch the website and verify that the not-functional links are no longer displayed. For the purposes of this demonstration, assume that at this point we take successfully deployed the updated modify to the production server.
Close the Cyberspace Explorer window and return to Visual Studio.
Open Team Explorer and navigate to Awaiting Changes.
Unremarkably yous would want to shelve other pending changes before taking on an out-of-ring update similar this. Still, it's easy to work around when yous don't. Under Included Changes, correct-click _Profile.cshtml and select Exclude Unselected to focus on only the change for the Release1 branch.
In the Comment field, enter "removed not-functional links from profile", verify only _Profile.cshtml is changed, and click Check In. Select Yeah if prompted to confirm check-in.
In the next job, we will merge the changes to the other branches.

Chore nine: Branching and Merging Visualization

In this task, you lot volition learn how to visualize and rail changesets while merging the changes that you made in the previous practice.

In Source Command Explorer, correct-click the Release1 branch and select View History from the context menu. Note that the items in your history may vary from the screenshot below.
Right-click the changeset that you merely checked in and select Track Changeset from the context menu.
In the Select Branches window, select Release1 as the Starting branch. Ensure Check all visible is selected and click Visualize to meet the current state of the changeset as information technology relates to the other branches.
This visualization shows u.s.a. that the changeset has been applied to Release1 just not to Dev. Information technology also makes it clear that in lodge to merge our changes into Dev nosotros will need to merge with the Main branch offset. Note that your changeset numbers may be unlike from those in the screenshots.
To perform the merge of this changeset and the Master branch, elevate and drib the green Release1 node onto the Main node. This volition load the Source Control Merge Wizard.
Ensure that the source co-operative to merge ends with "Release1" and the target branch ends with "Master". Select the Next push button to continue.
The next screen of the merge wizard specifies the version to merge. Past default, you should run across the changeset that you just checked in. Select the End push to perform the merge.
After the merge is complete, open Team Explorer and navigate to Pending Changes.
Notation that _Profile.cshtml inverse status for the Main lawmaking branch and is now "merge, edit". The merge process is complete, but nosotros still need to check in the changes.
Add a Annotate of "Merging fast-tracked changes from Release to Chief" and then click Cheque In to finalize the merge. Select Yes if asked to confirm the check-in.
In the Tracking Changeset window, select the Rerun button to generate an updated view.
Click Visualize again when the Select Branches window appears to see an updated visualization.
Next, merge the changeset from the Main co-operative with the Dev branch in the aforementioned fashion every bit before past dragging and dropping to load the Source Control Merge Wizard.
Select Next followed past Stop to perform the merge process.
In the Pending Changes window, enter a Comment of "Merged fast-tracked changes from Master to Dev".
Select the Cheque In button to finalize the merge with the Dev branch. Select Yeah if asked to confirm the check-in.
In the Tracking Changeset window, click Rerun to come across the updated view.
Another useful view is the Timeline Tracking view. Select the Timeline Tracking button to the left of the Bureaucracy Tracking push button to switch to this view. This shows the order in which the original changeset was merged with the other branches.
In Solution Explorer, navigate to and right-click _Profile.cshtml to select Source Control | Comment from the context menu.
Whorl to the bottom of the annotated _Profile.cshtml file and locate the HTML that you previously commented out.
In the annotation cavalcade on the left-mitt side, mouse over the recent changeset (information technology should bear witness the date of the guest virtual machine). Note that the changeset path and annotate refer to the Production co-operative where the original change was made.