Getting ready

Ensure that you have a shared location accessible to all developers in your organization. This can be anywhere your network administrator has provided for shared file access. You will probably want to restrict the access of these packages to developers only. A nice solution is to create a storage account on Azure to share the NuGet packages to. This is the approach I followed here using a fictitious company I have called Acme Corporation.

I will not go through setting up a storage account on Azure, but I will talk about accessing it from your local machine.

I encourage you and your organization to consider using Azure. I will not expand much on the benefits of using Azure other than to say that it is an incredible time-saver. If I want to test a specific feature of an application on a particular OS, within minutes I am able to spin up a VM and connect to it via a remote desktop. It is immediately ready to use.

After you have created your storage account on Azure, you will find the access keys on the Access keys tab.

  1. Make a note of the keys and the Storage account name.
  1. I also just created a File service called packages. To get here, click on Overview. Then, under the Services heading, click on Files. On the File service window, select packages and view the property information for the file share.
Your storage account might differ from the examples in this book, depending on what you called it.
  1. Make a note of the URL specified in the properties. Using the URL, map a network drive by changing the https:// part to \ and any subsequent / to  in the path.
  1. Add this path to the Folder textbox and ensure that you have checked Connect using different credentials.

Use the storage account name as the username and one of the keys as the password. You now have a network drive mapped to your Azure Storage account.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.118.140.204