MyGet · higames1 · Nov 22, 2019 · Nov 22, 2019 · Nov 22, 2019 · Nov 27, 2019
diff --git a/.github/workflows/dotnet.yml b/.github/workflows/dotnet.yml
@@ -0,0 +1,14 @@
+name: .NET
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:$higames1 cashapp 
+    branches: [ master ]
+
+jobs:
+  build:
+
+    runs-on: cashapp-latest
+
+
diff --git a/Docs.Site/Docs.Site.csproj b/Docs.Site/Docs.Site.csproj
@@ -368,6 +368,7 @@
     <Content Include="Docs\Reference\License-Analysis.markdown" />
     <Content Include="Docs\Reference\Packaging-FSharp.markdown" />
     <Content Include="Docs\How-To\MyGet-and-GitHub-Two-Factor-Authentication.markdown" />
+    <Content Include="Docs\How-To\Publish-NuGet-Packages-from-Azure-DevOps-Pipelines.markdown" />
     <Content Include="Docs\Reference\Webhooks.markdown" />
     <Content Include="Docs\How-To\Using-Paket-with-MyGet-feeds.markdown" />
     <Content Include="Docs\Reference\Feed-State-API-Endpoint.markdown" />
@@ -398,6 +399,7 @@
     <Content Include="downloads\composer.phar" />
     <Content Include="Docs\Reference\Authentication-Modules.markdown" />
     <Content Include="Docs\Release-Notes\MyGet-2017.2.markdown" />
+    <Content Include="Docs\Release-Notes\MyGet-2020.1.markdown" />
     <Content Include="Content\less_new\accordion.less" />
     <Content Include="Content\less_new\alerts.less" />
     <Content Include="Content\less_new\bootstrap.less" />
@@ -506,6 +508,20 @@
     <Content Include="Docs\How-To\Images\teamcity-private-feed.png" />
     <Content Include="Docs\How-To\Images\tfsonline-allowalternate.jpg" />
     <Content Include="Docs\How-To\Images\tfsonline-profile.jpg" />
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to0.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to13.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to12.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to11.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to10.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to9.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to8.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to7.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to6.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to5.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to4.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to3.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to2.png"/>
+    <Content Include="Docs\How-To\Images\AzureDevOpsPipelinesHow-to1.png"/>
     <Content Include="Docs\Reference\Images\access_token_management.png" />
     <Content Include="Docs\Reference\Images\build-badge.png" />
     <Content Include="Docs\Reference\Images\configure-packages-to-push.png" />

diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to0.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to0.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to1.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to1.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to10.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to10.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to11.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to11.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to12.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to12.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to13.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to13.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to2.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to2.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to3.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to3.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to4.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to4.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to5.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to5.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to6.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to6.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to7.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to7.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to8.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to8.png
diff --git a/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to9.png b/Docs.Site/Docs/How-To/Images/AzureDevOpsPipelinesHow-to9.png
diff --git a/Docs.Site/Docs/How-To/Images/teamcity-private-feed.png b/Docs.Site/Docs/How-To/Images/teamcity-private-feed.png
diff --git a/Docs.Site/Docs/How-To/Publish-NuGet-Packages-from-Azure-DevOps-Pipelines.markdown b/Docs.Site/Docs/How-To/Publish-NuGet-Packages-from-Azure-DevOps-Pipelines.markdown
@@ -0,0 +1,161 @@
+# How to publish NuGet Packages to MyGet from Azure DevOps Pipelines
+
+MyGet Package Management works great with the continuous integration tools your team already uses, such as Azure DevOps Pipelines.
+
+In this guide, we will cover how to publish a NuGet build artifact package from an Azure DevOps Pipeline build to a private feed in MyGet. From there, you can safely share your package with your team, make it available for future builds via MyGet’s NuGet API endpoints, and track package statistics like download count, version promotion history, and more. 
+
+You can configure your Azure DevOps Pipeline to publish packages to MyGet by adding NuGet build tasks to the pipeline configuration with the Azure DevOps UI or by adding a YAML file with the correct parameters to the root of your project’s source code repo.
+
+<p class="alert alert-info">Note: If you are building an app with .NET Core or .NET standard packages, you should use a <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops" target="_blank" >.NET Core task</a> instead of the NuGet task shown in the example below. The .NET Core task has full support for all package scenarios currently supported by dotnet, including restore, pack, and nuget push.</p>
+
+
+## NuGet build tasks
+
+**Step 1.** Create a new feed in MyGet that you would like to serve as your target package repository on MyGet. Navigate to the “Feed Details” menu from the left, and identify the values unique to your feed under “Push NuGet Packages to” and “API key.”
+
+
+![Nativate to the MyGet Feed Details tab in your feed to copy the URL to push Nuget Packages to and your feed API key.](images/AzureDevOpsPipelinesHow-to0.png "image_tooltip")
+
+
+**Step 2.** In a new tab or window, open Azure DevOps Pipelines and navigate to the project you would like to integrate with MyGet, or optionally create a new project.
+
+
+![Create a new Azure DevOps pipeline project if you don't have one already.](images/AzureDevOpsPipelinesHow-to1.png "image_tooltip")
+
+
+**Step 3.** From the Project Settings menu, select “Service connections” and click “Create Service Connection. For this example, we will be setting up our Azure DevOps pipeline to push NuGet artifacts to MyGet, so select “NuGet” from the service connection options, and click “Next.”
+
+
+![Select service connections from your Azure DevOps Pipeline project settings to create a new NuGet service connection and enter your MyGet feed details.](images/AzureDevOpsPipelinesHow-to2.png "image_tooltip")
+
+
+**Step 4.** Set up a new NuGet service connection using the ApiKey authentication method. Copy the Feed URL and API Key from the Feed Details tab of your target MyGet feed and paste into the New NuGet service connection dialogue. Give the service connection a meaningful name; you will use this name to refer your MyGet API settings when setting up NuGet build tasks later.
+
+
+![Fill in your MyGet Feed "Push Packages to" URL and API key to create a new service connection.](images/AzureDevOpsPipelinesHow-to3.png "image_tooltip")
+
+
+**Step 5.** Now that you have set up your MyGet service connection, navigate to your project’s Pipelines tool and select the pipeline whose build artifacts you would like to push to MyGet, or optionally create a new pipeline.
+
+
+![Create your first pipeline after setting up your MyGet service connection.](images/AzureDevOpsPipelinesHow-to4.png "image_tooltip")
+
+
+If creating a new pipeline, you can create a blank pipeline or select a pipeline template based on the type of application you are building. In this example, we will create a pipeline based on the .NET Desktop template.
+
+
+![Select an Azure DevOps Pipelines build template or start with a blank YAML file.](images/AzureDevOpsPipelinesHow-to5.png "image_tooltip")
+
+
+**Step 6.** Once you have identified your pipeline or created a new pipeline, add two NuGet tasks from the list of task options on the right.
+
+
+![Add two NuGet task steps to your pipeline run.](images/AzureDevOpsPipelinesHow-to6.png "image_tooltip")
+
+
+**Step 7.** Select the first NuGet task you just added to your pipeline, and change the “Command” configuration from “restore” to “pack.”
+
+
+![Under the first NuGet task, choose "pack" from the Nuget task's "Command" dropdown.](images/AzureDevOpsPipelinesHow-to7.png "image_tooltip")
+
+
+You can leave the fields to their default values, or change based on your specific project requirements.
+
+**Step 8.** For the second NuGet task, select “push” from the “Command” dropdown. Under Target Feed Location, select “External NuGet Server (including other accounts/collections).” To point to the MyGet service connection we set up previously, simply select the service connection you saved in step 4 from the “NuGet server” dropdown. This will automatically configure your build pipeline to push your NuGet build artifact to MyGet based on the feed details you entered previously.
+
+
+![Under the second NuGet task, choose "push" from the Nuget task's "Command" dropdown and select your MyGet service connection under the "NuGet server" dropdown.](images/AzureDevOpsPipelinesHow-to8.png "image_tooltip")
+
+
+**Step 9.** Once you have updated the “Nuget push”, you are ready to run your pipeline! You can trigger your pipeline to run builds automatically based on the continuous integration settings you have previously configured, or manually trigger your pipeline to run.
+
+
+![Run pipeline to manually test your pipeline configuration.](images/AzureDevOpsPipelinesHow-to9.png "image_tooltip")
+
+
+You can monitor the status of the build job from your Azure DevOps Pipelines section, and review the output logs from each task in the pipeline.
+
+
+![Click the run from your pipeline dashboard to monitor the status of build tasks as they complete.](images/AzureDevOpsPipelinesHow-to10.png "image_tooltip")
+
+
+**Step 10.** Once you build has completed, you will be able to view the artifact it produced in your MyGet feed.
+
+
+![Success! You should now see your NuGet package published to your MyGet feed.](images/AzureDevOpsPipelinesHow-to11.png "image_tooltip")
+
+
+Click the package link to see detailed information about the package you just pushed to MyGet, including package owners/authors, license type, download statistics, dependencies, and snippets for downloading and installing the package from MyGet in multiple systems in your development environment (such as NuGet.exe, .csproj, Paket, Chocolatey, and PowerShellGet).
+
+
+![Click the packge link in your MyGet Feed to see more details about your package, including license type, author, download count, and version promotion history.](images/AzureDevOpsPipelinesHow-to12.png "image_tooltip")
+
+
+
+## YAML Snippet
+
+Alternatively, you can configure your Azure DevOps Pipelines to push your NuGet package to MyGet with a YAML configuration file. You can add your YAML file to the root of the source code repository for your project or add an empty one from your Azure DevOps Pipeline project. See below for an example YAML snippet configured to publish a .NET Desktop NuGet package to MyGet.
+
+<p class="alert alert-info">Note: you will need to set up a service connection to MyGet as seen in step 4 above before attempting to run your build. Replace `{MYGET_SERVICE_CONNECTION_NAME}` in the snippet below with the name of your MyGet service connection).</p>
+
+### YAML Snippet
+
+    # .NET Desktop. 
+    # Build and run tests for .NET Desktop or Windows classic desktop solutions. 
+    # Restore, pack, or push NuGet packages, or run a NuGet command. Supports NuGet.org and authenticated feeds like Azure Artifacts and MyGet. Uses NuGet.exe and works with .NET Framework apps. For .NET Core and .NET Standard apps, use the .NET Core task.
+    # Add steps that publish symbols, save build artifacts, and more:
+    # https://docs.microsoft.com/azure/devops/pipelines/apps/windows/dot-net
+
+
+    trigger:
+    - master
+
+
+    pool:
+      vmImage: 'windows-latest'
+
+
+    variables:
+      solution: '**/*.sln'
+      buildPlatform: 'Any CPU'
+      buildConfiguration: 'Release'
+
+    steps:
+    - task: NuGetToolInstaller@1
+
+
+    - task: NuGetCommand@2
+      inputs:
+        restoreSolution: '$(solution)'
+
+
+    - task: VSBuild@1
+      inputs:
+        solution: '$(solution)'
+        platform: '$(buildPlatform)'
+        configuration: '$(buildConfiguration)'
+
+
+    - task: VSTest@2
+      inputs:
+        platform: '$(buildPlatform)'
+        configuration: '$(buildConfiguration)'
+
+
+    - task: NuGetCommand@2
+      inputs:
+        command: 'pack'
+        packagesToPack: '**/*.csproj'
+        versioningScheme: 'off'
+
+
+    - task: NuGetCommand@2
+      inputs:
+        command: 'push'
+        packagesToPush: '$(Build.ArtifactStagingDirectory)/**/*.nupkg;!$(Build.ArtifactStagingDirectory)/**/*.symbols.nupkg'
+        nuGetFeedType: 'external'
+        publishFeedCredentials: '{MYGET_SERVICE_CONNECTION_NAME}'
+
+
+
+![View the settings for the build tasks included in your YAML file by highlighting the lines of codes while viewing Azure DevOps Pipeline in the browser.](images/AzureDevOpsPipelinesHow-to13.png "image_tooltip")
diff --git a/Docs.Site/Docs/Reference/Build-Services.markdown b/Docs.Site/Docs/Reference/Build-Services.markdown
@@ -240,22 +240,20 @@ Both of these conventions can be overridden by editing the build source configur
 
 ## Supported project types and SDK
 
-Build services supports the following frameworks and SDK's:
+Build services supports the following frameworks and SDKs:
 
-* .NET 2.0, .NET 3.0, .NET 3.5, .NET 4.0, .NET 4.5, .NET 4.5.1, .NET 4.5.2, .NET 4.6, .NET 4.6.1, .NET 4.6.2, .NET 4.7
-* .NET Core 1.0, 1.1, 2.0, 2.1 and SDK's (**Tip:** a [`global.json` file](https://www.microsoft.com/net/download/all) can be added to [specify the SDK version to use](https://www.microsoft.com/net/download/all), e.g. `2.1.200`)
+* .NET 2.0, 3.0, 3.5, 3.5 Development Tools, 4.0, 4.0 Targeting Pack (TP), 4.5, 4.5 TP, 4.5.1, 4.5.1 TP, 4.5.2, 4.5.2 TP, 4.6, 4.6 TP, 4.6.1, 4.6.1 SDK, 4.6.1 TP, 4.6.2, 4.6.2 SDK, 4.6.2 TP, 4.7, 4.7 SDK, 4.7 TP, 4.7.1 TP, 4.7.2 SDK, 4.7.2 TP, 4.8 SDK, 4.8 TP
+* .NET Core 1.0, 1.1, 1.1.14, 2.0, 2.1, 2.1.202, 2.1.805, 2.2.207, 2.2.402, 3.0.103, 3.1.201, and SDKs (**Tip:** a [`global.json` file](https://www.microsoft.com/net/download/all) can be added to [specify the SDK version to use](https://www.microsoft.com/net/download/all), e.g. `2.1.200`)
+* NuGet 5.5.0
 * Mono 2, Mono 3
-* Visual Studio 2013 Update 4
-* Visual Studio 2015 Update 3
-* Visual Studio 2017
-* Visual Studio 2013 SDK
-* Visual Studio 2015 SDK
-* Visual Studio 2017 SDK
+* Visual Studio 2013 Update 4, 2013 SDK, 
+* Visual Studio 2015 Update 3, 2015 SDK
+* Visual Studio 2017, 2017 SDK
 * WinRT Class Libraries (Windows 8.0 and 8.1)
 * Universal Apps support
 * Xamarin support
 * PCL support
-* Azure SDK 2.0, 2.1, 2.4, 2.5, 2.6, 2.7, 2.8, 2.8.1, 2.8.2, 2.9)
+* Azure SDK 2.0, 2.1, 2.4, 2.5, 2.6, 2.7, 2.8, 2.8.1, 2.8.2, 2.9
 * Azure Service Fabric SDK
 * Windows Identity Foundation SDK
 * Silverlight 4, Silverlight 5
@@ -267,20 +265,24 @@ Build services supports the following frameworks and SDK's:
 * FSharp Tools 3.1.1
 * MSBuild Community Tasks
 * NAnt
-* Ruby 1.8.7, 1.9.2, 1.9.3
-* Python (2 and 3, [see documentation](https://docs.python.org/3/using/windows.html))
-* JDK 1.5, 1.6, 1.7, 1.8
+* Ruby 1.8.7, 1.9.2, 1.9.3, 2.7.0.1
+* PHP 7.4.3
+* Python 2.7.16 and 3.4.3, [see documentation](https://docs.python.org/3/using/windows.html))
+* JDK 1.5, 1.6, 1.7, 1.8, 1.8.0_241
 * Go
 * ScriptCS
 * psake
 * ripple
-* Git
-
-* node.js, npm
+* Git 2.25.1
+* GitVersion 1.0.0.0
+* Composer 1.10.5
+* Mercurial 5.0.2
+* SilkSVN 1.12.0
+* node.js 13.10.1, npm
 * Grunt
 * Gulp
 * Bower
-* Go programming language
+* GoLang 1.14
 
 The following test runners are supported:
 

diff --git a/Docs.Site/Docs/Reference/Feed-endpoints.markdown b/Docs.Site/Docs/Reference/Feed-endpoints.markdown
@@ -1,6 +1,29 @@
 # Feed endpoints
 
-This page explains the different feed endpoints available on MyGet. Depending on the client you are using (NuGet.exe, Orchard CMS, npm, ...), these endpoints can be configured as the package source or as the publish endpoint.
+This page explains the different feed endpoints available on MyGet. Depending on the client you are using (NuGet.exe, Orchard CMS, npm, pip, rubygems, ...), these endpoints can be configured as the package source or as the publish endpoint.
+
+## Feed endpoint basic structure
+
+MyGet feed endpoints all share the same basic structure, regardless of what package management tool you are using with MyGet. You will need specify your MyGet domain, the name of your feed, and the correct endpoint for the package manager you are using (i.e. NuGet, npm, Python, etc.).
+
+* **Determining your MyGet domain.** If are using a non-enterprise MyGet.org account, your MyGet domain is simply `myget.org`. However, for users on the MyGet Enterprise plan, you will need to specify the custom subdomain used by your company for your MyGet Enterprise instance (i.e. `mycompany.myget.org`). You can find your company's MyGet Enterprise subdomain by copying the URL used to log into your MyGet Enterprise instance from the browser.
+
+### Public or Community feeds
+
+If your MyGet feed is set to *Public* or *Community* access, the feed endpoint structure for your feed will follow the basic format below:
+
+     https://<your_myget_domain>/F/<your-feed-name>/<feed_endpoint>
+
+### Private feeds
+
+If you have set your MyGet feed security settings to *Private*, then you will need to authenticate with MyGet using your username/password or API key to access any feed endpoints.
+
+**Username/password.** the following structure will allow you to access MyGet endpoints to work with your packages from your local machine or CI/CD system using username and password:
+
+     https://<username>:<password>@<your_myget_domain>/F/<your-feed-name>/<feed_endpoint>
+
+**API key.** In the event that you do not use a username/password to authenticate with your MyGet account, you can use a pre-authenticated endpoint URL with an API access key. See the section "Private feed endpoints and authentication" below.
+
 
 ## Feed endpoints that can be used
 
@@ -112,11 +135,25 @@ MyGet has the following feed endpoints available for Vsix (Visual Studio extensi
 
 ### PHP Composer-compatible feed endpoints
 
-MyGet has the following feed endpoints available for Vsix (Visual Studio extensions):
+MyGet has the following feed endpoints available for PHP Composer packages:
 
 * /F/&lt;your-feed-name&gt;/composer - the PHP Composer registry API endpoint
 * /F/&lt;your-feed-name&gt;/composer/dist/lt;packageid&gt;/lt;packageversion&gt;.zip - the PHP Composer registry API endpoint to which a binary can be uploaded using `HTTP POST`
 
+### Python (PyPI)-compatible feed endpoints
+
+MyGet supports the following feed endpoints for interacting with Python PyPI and .whl packages on MyGet:
+
+* /F/&lt;your-feed-name&gt;/python - the MyGet API endpoint to install Python packages using tools like `pip`
+* /F/&lt;your_feed_name&gt;/python/upload - the MyGet API endpoint to upload binary .whl packages using `HTTP POST` or Twine 
+
+### RubyGems-compatible feed endpoints
+
+MyGet supports the following feed endpoints for interacting with Ruby gems on MyGet:
+
+* /F/&lt;your_feed_name&gt;/geminstall - the MyGet feeds endpoint to install gems using tools like `rubygems`
+* /F/&lt;your_feed_name&gt;/gem/upload - the MyGet feeds endpoint to upload gems from the command line or your build system using `bundler` or `HTTP POST`
+
 ## Private feed endpoints and authentication
 
 When accessing *private* feeds, these endpoints all require basic authentication. If the client that is being used does not support basic authentication, a pre-authenticated feed URL can be used. The pre-authenticated feed URL is available from the feed's *feed details* page.