Skip to content

Conversation

@jkotalik
Copy link
Contributor

@jkotalik jkotalik commented Dec 5, 2018

  • Removes all PackageLineup code (dead due to mondo repo)
  • Use full msbuild on Windows
  • Fix invalid reference to internal.aspnetcore.sdk in 2.1.x (@muratg this will require a rebuild)
  • Fix shared folder references for PackageArchive task.

Copy link
Contributor

@natemcmaster natemcmaster left a comment

Choose a reason for hiding this comment

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

I love deleting obsolete code. :)

Also get @muratg or @Eilon's approval since this is a change to release/2.1.

@natemcmaster
Copy link
Contributor

Build passes 🎉.

@natemcmaster natemcmaster merged commit 0588b13 into release/2.1 Dec 6, 2018
@natemcmaster natemcmaster deleted the jkotalik/21FullMsbuild branch December 6, 2018 01:01
"Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
"Microsoft.VisualStudio.Component.VC.ATL",
"Microsoft.VisualStudio.Component.Windows10SDK.15063.Desktop"
]
Copy link
Member

@halter73 halter73 Dec 10, 2018

Choose a reason for hiding this comment

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

@jkotalik @natemcmaster How necessary is this requirement on Windows? I don't have any of these workloads installed, and I don't want to install them. Even .\build.cmd /t:restore is broken since KoreBuild complains I don't have a compatible version of MSBuild.

Can't we just skip building IISIntegration and any other projects that need these special VS workloads on Windows machines that don't have these workloads installed? We have to do this for non-Windows platforms anyway, right?

Copy link
Contributor

Choose a reason for hiding this comment

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

Can't we just skip building IISIntegration and any other projects that need these special VS workloads on Windows machines that don't have these workloads installed?

We discussed this in build triage, and consensus was that we'd rather have build.cmd fail fast than fail later with mysterious errors. We'll work on improving error messages to make it more obvious how to install VS with the required workloads. Tracking issue: https://github.com/aspnet/AspNetCore-Internal/issues/1505

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants