Install .NET Core 3.1 SDK on Windows to support Track 1 SDK#35151
Install .NET Core 3.1 SDK on Windows to support Track 1 SDK#35151live1206 merged 8 commits intoAzure:mainfrom
Conversation
|
@weshaggard Could you help to review this? Thanks! |
jsquire
left a comment
There was a problem hiding this comment.
Blocking merge until the scenario is understood.
|
@live1206 I thought we were rolling forward to the latest .NET when running the code generation so why would we still need this? Is there something else that needs it? Looking at your link it appears as though there are still some test projects targeting .NET Core 3.1. We should instead update those test projects to .NET 7.0 as .NET 3.1 is out support. |
|
If this is indeed not necessary, I have a PR to remove the step entirely as we don't need to be wasting time on windows jobs installing it: #35174 |
Tried with a draft PR #35178, it takes more effort than expected. |
There's a difference between building with the .NET 7 SDK and changing the target frameworks for libraries. We need to do the former, we do not want to do the latter. @live1206 - would you please help us understand what problem you're trying to solve? What behavior are you seeing that requires changes? |
|
@jsquire As I mentioned in the description, the CI is failing for Track 1 .NET SDK PR: https://github.com/Azure/azure-sdk-for-net/pull/35148/checks?check_run_id=12290486264, it is blocking Track 1 .NET SDK release. The reason the Track 1 CI failure is the Track 1 tests are requiring .NET core 3.1 during the run. |
What should change here is the SDK in use; these should be compiled using the .NET 7 SDK. We do not want to install/use the .NET Core 3.1 SDK, as it has reached end-of-life. |
As I explained in #35178 (comment), it's not an easy fix to upgrade the target .NET to latest. |
Dismissing block as a path forward has been agreed upon to unblock the release and address the underlying dependency issue in the longer term.
|
/azp run net - mgmt |
|
No pipelines are associated with this pull request. |
|
I'd like to make sure we get a test run of the mgmt pipeline as well to ensure this change works as expected. |
|
/azp run net - mgmt - ci |
|
Azure Pipelines failed to run 1 pipeline(s). |
|
/azp run net - mgmt - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…rEnabled in SDK (#35466) * Generated SDK and Added test * Install .NET Core 3.1 SDK on Windows to support Track 1 SDK (#35151) * Install .NET Core 3.1 SDK on Windows to support Track 1 * Comment * Install dotnet with tasks instead of template * Install .net core 3.1 for Track 1 .NET SDK * Remove condition * Install .net core 3.1 for test as well --------- Co-authored-by: Wei Hu <live1206@gmail.com>
* generated with 2023-03-01 tag * update version * new recordings for all tests * sanitize key * last test recording * Add test for VMSS Reapply (#34738) * Add test for VMSS Reapply * Record test * Adding $expand query param as part of ListAll VMs in RG and Subscription (#34878) * Adding $expand query param as part of ListAll VMs in RG and Subscription * Record new test --------- Co-authored-by: Theodore Chang <thchan@microsoft.com> * Add VM property (#34842) (#34938) Co-authored-by: payalguptapg <126145083+payalguptapg@users.noreply.github.com> Co-authored-by: Theodore Chang <theodore.l.chang@gmail.com> * Remove <br> syntax from most CRP swagger descriptions (#35016) * br cleanup for net * Update AutomaticOSUpgradePolicy.cs * Update AutomaticOSUpgradePolicy.cs * Add Compute SecurityPosture SDK for 2023-03-01 (#35345) * Adding Restore Point Encryption, HyperVGeneration and WriteAcceleratorEnabled in SDK (#35466) * Generated SDK and Added test * Install .NET Core 3.1 SDK on Windows to support Track 1 SDK (#35151) * Install .NET Core 3.1 SDK on Windows to support Track 1 * Comment * Install dotnet with tasks instead of template * Install .net core 3.1 for Track 1 .NET SDK * Remove condition * Install .net core 3.1 for test as well --------- Co-authored-by: Wei Hu <live1206@gmail.com> * Add sdk support for vmss deallocate hibernate optional parameter (#35335) * dedicated host Resize (#35197) Co-authored-by: Theodore Chang <thchan@microsoft.com> * Adding missing property for VirtualMachineExtension and VMSSExtension (#35233) * adding property * Adding provisionedAfterExtensions in VirtualMachineExtension * reverting the commit * VMSSExtension * added scenario test and record * Reverting back files related to VirtualMachineScaleSetExtension. Changes in VirtualMachineScaleSetVMExtension including adding scenario tests and record. --------- Co-authored-by: Younghyun Kim <younghyunkim@microsoft.com> * regenerated, metatags * customizations * sanitized SAS recordings for compliance CI * finish customization. resolve build failure --------- Co-authored-by: Theodore Chang <theodore.l.chang@gmail.com> Co-authored-by: Anshul Verma <88476874+AnshulVermaa@users.noreply.github.com> Co-authored-by: Kartik Gupta <31189137+Kartik-715@users.noreply.github.com> Co-authored-by: payalguptapg <126145083+payalguptapg@users.noreply.github.com> Co-authored-by: Adam Sandor <adsandor@microsoft.com> Co-authored-by: mabhard <52765900+mabhard@users.noreply.github.com> Co-authored-by: Linu George <127192938+linugeorgeofficial@users.noreply.github.com> Co-authored-by: Wei Hu <live1206@gmail.com> Co-authored-by: vatsan28 <vatsan9228@gmail.com> Co-authored-by: cakarata <47228825+cakarata@users.noreply.github.com> Co-authored-by: younghyun5756 <102988755+younghyun5756@users.noreply.github.com> Co-authored-by: Younghyun Kim <younghyunkim@microsoft.com>
.NET Core 3.1 SDK does not exist on Windows hosted machine anymore, we still need it for Track 1 SDK
https://github.com/Azure/azure-sdk-for-net/pull/35148/checks?check_run_id=12290486264
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.