Did you know you can download a specific set of docs as a PDF without it taking gigabytes of space, enabling you to take it anywhere with you on your desktop or mobile device.
Simply go to the particular docs you’re interested in, for example the Azure Application Architecture Guide and then below table of contents on the left side you will see a Download PDF button.
Clicking the Download PDF button will open up the latest version of the docs for this topic in a browser and from here you can click to save.
As you can see it downloaded a 73 page PDF document with all the content found online.
As content is changed online, clicking the Download PDF will result in getting the latest version of this document.
To follow up and learn about other updates to the Microsoft Docs site, follow their blog at https://docs.microsoft.com/en-us/teamblog/.
If you’ve been using Git from within Visual Studio 2017 you might be aware of the fact that when performing a fetch it would not automatically prune your local list of branches that no longer exist on the server. Typically you would have to open up a Command Prompt and run the following command to cleanup your list of branches that exist on the remote:
> git remote prune origin
Well now with Visual Studio 2017 Update 5 you can now configure your global and repository settings to prune your local list of branches on every fetch. Let’s take a look at how you can configure this.
First download and install Visual Studio 2017 Update 5. You can do this from within Visual Studio under the Tools menu:
Once you have Visual Studio 2017 Update 5 installed, go to the Team Explorer pane and click on Settings where you can configure your default behavior for your Global and/or Repository Settings:
Now you can change the setting to prune remote branches on every fetch. In my opinion this should be the default value.
Another nice addition to the Git settings in Visual Studio 2017 Update 5 is the ability to Rebase your changes when you pull. I’ll explore that in a future post.
In summary when enabling the prune on every fetch, this means your local list of branches is always up-to-date with the remote. Pruning will cleanup and remove your local tracking branches that no longer exist on the server.
Git Configuration: Configure your default behavior