Publish to internal ADO feed to work around ADO lag (#307)

* Fix issue in VC versioning

* Publish to internal ADO feed to work around ADO lag

Author: yangpanMS

.pipelines/azure-pipelines-linux.yml

@@ -16,7 +16,7 @@ resources:
     options: --entrypoint=""
 
 variables:
-  VcVersion : 1.14.23
+  VcVersion : 1.14.24
   ROOT: $(Build.SourcesDirectory)
   CDP_DEFINITION_BUILD_COUNT: $[counter('', 0)] # needed for onebranch.pipeline.version task https://aka.ms/obpipelines/versioning
   ENABLE_PRS_DELAYSIGN: 1

.pipelines/azure-pipelines.yml

@@ -18,7 +18,7 @@ pool:
   vmImage: windows-latest
 
 variables:
-  VcVersion : 1.14.23
+  VcVersion : 1.14.24
   ROOT: $(Build.SourcesDirectory)
   CDP_DEFINITION_BUILD_COUNT: $[counter('', 0)] # needed for onebranch.pipeline.version task https://aka.ms/obpipelines/versioning
   ENABLE_PRS_DELAYSIGN: 1
@@ -86,5 +86,10 @@ steps:
     MaxConcurrency: '50'
     MaxRetryAttempts: '5'
 
+- script: dotnet nuget push $(Build.SourcesDirectory)\out\packages\*.nupkg --api-key $(ADOAPIKEY) --timeout 1200 --source https://msazure.pkgs.visualstudio.com/_packaging/CRC-VC/nuget/v3/index.json --skip-duplicate 
+  displayName: 'Publish NuGet to ADO Artifact Packages as temporary workaround to ADO lagging behind in package availability'
+
 - script: $(Build.SourcesDirectory)\upload-packages.cmd $(Build.SourcesDirectory)\out\packages $(NUGETORGAPIKEY)
   displayName: 'Publish NuGet Packages'
+
+