-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Make Visual Studio 2019 a prerequisite to building this repo #7005
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Marked as "wip" because we haven't validated this yet on our VSTS agent pools. |
We need a plan for https://github.com/aspnet/AspNetCore-Internal/issues/1764 as part of this. |
/AzurePipelines run AspNetCore-ci |
Agreed. I believe the plan is to keep running tests on TeamCity until Helix comes online (wip right now -> #6728 ). I'm updating this PR to remove the ANCM build jobs for now. I believe the core-eng team is rolling out the updated VS2019 agents today, so we should be unblocked on this now. I'd like to merge soon, so PTAL, reviewers. |
Build fails with an new error. I can't tell for sure, but my guess is it's a problem building the Blazor VSIX. @SteveSandersonMS @rynowak @ajaybhargavb have you seen this before?
|
Resolved the git.exe problem by redirecting stderr to stdout and filtering the warning messages. I believe this is ready for final review and ready to merge (pending CI checks, of course). |
…e tasks and targets (#935) Part of dotnet/aspnetcore#7005. Resolves #881 Due to the large amount of breaking changes between MSBuild 15 and 16 (VS 2017 and VS 2019), I've decided to remove tasks broken by the upgrade instead of port them to a higher version. Changes: * Remove tasks related to dependency flow (replaced by Arcade) * Remove tasks which push and pack NuGet packages (replaced by Azure Pipelines and pack tasks in Microsoft.NET.Sdk) * Remove tasks for enabling/disabling strong name verification in .NET Framework (this was added as a workaround for bad builds from corefx which haven't happened in a long time) * Remove tasks related to running KoreBuild inside a Docker container (replaced by the `dockerbuild.sh` script in aspnet/AspNetCore`) * Remove unzip/zip tasks - there is now a version built-in to MSBuild itself which should be used instead
A bunch of test failures. It looks like they fall into 3 categories:
|
@natemcmaster - HttpSys - No, nothing should have changed here. The thing most likely to destabilize those tests it is changing the OS version. |
Yeah, that might be it. I've updated to make windows RIDs in test consistent across all projects. |
All required checks passed. |
@@ -0,0 +1,20 @@ | |||
<!-- Use this file to workaround issues. List the issue tracking the item to fix so we can remove the workaround when the issue is resolved. --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks a'ight to me!
"The version of the selected solution is higher than the solution version supported by this Visual Studio release. Please try downloading the latest service pack for this Visual Studio release, or opening in a more recent version of Visual Studio, if available." Hosting.sln
Microsoft Visual Studio Enterprise 2019 Preview Installed Version: Enterprise |
Hmm, setting a specific build number of VS worked in P2. I wonder if something changed in P3. I'll reset the .sln files to 16.0.0.0. |
|
Hi. What is the status here? I dont see any cpprestsdk.v142 nuget package. Edit: Sorry! I seems to have commented on the wrong project here. I meant to comment on cpprestsdk. So please forget my comment. |
@Pilchie. Sorry, I commented on the wrong project. So no need to answer me. Thanks |
No worries. |
…aspnetcore#7005) Changes: * Make Visual Studio 2019 a prerequisite for building this repo * Update .sln files * Update Windows SDK to 17134 * Update developer docs * Disable ANCM tests * Update to .NET Core SDK 3.0 Preview 2 * Use Microsoft.NET.Sdk.Razor as a package consistently accross the repo * React to changes in metadata from Microsoft.NETCore.App * React to changes in .NET Core SDK * Attempt to workaround CodeCheck.ps1 failure which doesn't repro locally or on different agents. Possibly due to differences in the version of the PowerShell task? * Remove dead YML file * Rename usages of win7-{x64,x86} to win-{x64,x86} * Update KoreBuild to 3.0.0-build-20190219.1 Commit migrated from dotnet/aspnetcore@85ae18c723a2
…e tasks and targets (#935) Part of dotnet/aspnetcore#7005. Resolves aspnet/BuildTools#881 Due to the large amount of breaking changes between MSBuild 15 and 16 (VS 2017 and VS 2019), I've decided to remove tasks broken by the upgrade instead of port them to a higher version. Changes: * Remove tasks related to dependency flow (replaced by Arcade) * Remove tasks which push and pack NuGet packages (replaced by Azure Pipelines and pack tasks in Microsoft.NET.Sdk) * Remove tasks for enabling/disabling strong name verification in .NET Framework (this was added as a workaround for bad builds from corefx which haven't happened in a long time) * Remove tasks related to running KoreBuild inside a Docker container (replaced by the `dockerbuild.sh` script in aspnet/AspNetCore`) * Remove unzip/zip tasks - there is now a version built-in to MSBuild itself which should be used instead
We're preparing to consume some changes soon which will require Visual Studio 2019 (C# 8, updated .NET Core 3 SDKs, etc.)
Changes: