Skip to content

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

Merged
merged 86 commits into from
Feb 20, 2019

Conversation

natemcmaster
Copy link
Contributor

@natemcmaster natemcmaster commented Jan 25, 2019

We're preparing to consume some changes soon which will require Visual Studio 2019 (C# 8, updated .NET Core 3 SDKs, etc.)

Changes:

  • Updated documentation in aspnet/AspNetCore
  • Updated InstallVisualStudio.ps1 scripts
  • Updated .sln files to require VS >= 16
  • Updated CI config to use agents with VS 2019 installed

@natemcmaster
Copy link
Contributor Author

Marked as "wip" because we haven't validated this yet on our VSTS agent pools.

@Eilon Eilon added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Jan 25, 2019
@natemcmaster
Copy link
Contributor Author

@natemcmaster natemcmaster added the blocked The work on this issue is blocked due to some dependency label Feb 1, 2019
@pakrym
Copy link
Contributor

pakrym commented Feb 4, 2019

We need a plan for https://github.com/aspnet/AspNetCore-Internal/issues/1764 as part of this.

@natemcmaster
Copy link
Contributor Author

/AzurePipelines run AspNetCore-ci

@natemcmaster natemcmaster removed the blocked The work on this issue is blocked due to some dependency label Feb 5, 2019
@natemcmaster natemcmaster changed the title wip: Make Visual Studio 2019 a prerequisite to building this repo Make Visual Studio 2019 a prerequisite to building this repo Feb 5, 2019
@natemcmaster
Copy link
Contributor Author

We need a plan for aspnet/AspNetCore-Internal#1764 as part of this.

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.

@natemcmaster
Copy link
Contributor Author

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?

2019-02-05T23:03:00.8270212Z Unhandled Exception: System.Runtime.Serialization.SerializationException: Unable to find assembly 'Microsoft.VisualStudio.CodeAnalysis, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
2019-02-05T23:03:00.8272220Z    at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
2019-02-05T23:03:00.8273711Z    at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
2019-02-05T23:03:00.8280961Z    at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
2019-02-05T23:03:00.8288479Z    at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)

https://dev.azure.com/dnceng/public/_build/results?buildId=88221&view=logs&jobId=f31c9f97-4411-58e7-49ac-fc73f645e6b6&taskId=6eab48b9-b4ce-58d4-7c0f-2d2ef2bbc0bd&lineStart=2937&lineEnd=2943&colStart=1&colEnd=103

@natemcmaster natemcmaster added the blocked The work on this issue is blocked due to some dependency label Feb 6, 2019
@natemcmaster natemcmaster removed the blocked The work on this issue is blocked due to some dependency label Feb 19, 2019
@natemcmaster natemcmaster dismissed dougbu’s stale review February 19, 2019 20:54

PR has changed significantly

@natemcmaster
Copy link
Contributor Author

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).

natemcmaster added a commit to aspnet/BuildTools that referenced this pull request Feb 19, 2019
…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
@natemcmaster
Copy link
Contributor Author

A bunch of test failures. It looks like they fall into 3 categories:

  • HttpSys response caching is broken (cc @Tratcher any ideas?)
  • MusicStore - running dotnet publish fails, but not error is present in logs
  • MusicStore - some tests timeout trying to update the database

@Tratcher
Copy link
Member

@natemcmaster - HttpSys - No, nothing should have changed here. The thing most likely to destabilize those tests it is changing the OS version.

@natemcmaster
Copy link
Contributor Author

Yeah, that might be it. I've updated to make windows RIDs in test consistent across all projects.

@natemcmaster
Copy link
Contributor Author

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. -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Copy link
Member

@Eilon Eilon left a 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!

@natemcmaster natemcmaster merged commit 85ae18c into dotnet:master Feb 20, 2019
@natemcmaster natemcmaster deleted the vs2019 branch February 20, 2019 17:53
@Tratcher
Copy link
Member

"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 Solution File, Format Version 12.00
# Visual Studio Version 16
VisualStudioVersion = 16.0.0.0
MinimumVisualStudioVersion = 16.0.28608.199

Microsoft Visual Studio Enterprise 2019 Preview
Version 16.0.0 Preview 3.0
VisualStudio.16.Preview/16.0.0-pre.3.0+28608.199
Microsoft .NET Framework
Version 4.7.03190

Installed Version: Enterprise

@natemcmaster
Copy link
Contributor Author

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.

@Tratcher
Copy link
Member

MinimumVisualStudioVersion = 16.0.28606.0 seems to be the highest value that works.

@petke
Copy link

petke commented Oct 7, 2019

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
Copy link
Member

Pilchie commented Oct 7, 2019

@jkotalik - Can you answer @petke's question?

@petke
Copy link

petke commented Oct 7, 2019

@Pilchie. Sorry, I commented on the wrong project. So no need to answer me. Thanks

@jkotalik
Copy link
Contributor

jkotalik commented Oct 7, 2019

No worries.

dougbu pushed a commit to dougbu/razor-compiler that referenced this pull request Nov 17, 2021
…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
DotDeveloper95 added a commit to DotDeveloper95/BuildTools that referenced this pull request Sep 4, 2023
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.