Skip to content

Update SDK #41798

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 25 commits into from
Jun 24, 2022
Merged

Update SDK #41798

merged 25 commits into from
Jun 24, 2022

Conversation

SteveSandersonMS
Copy link
Member

Regular build-ops update

@SteveSandersonMS SteveSandersonMS requested review from a team, dougbu and wtgodbe as code owners May 23, 2022 12:23
@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label May 23, 2022
Copy link
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

This looks fine and matches my understanding of the current SDK version. But it appears none of the build jobs could find the archives. Retrying and if that doesn't work, please contact First Responders @SteveSandersonMS

@SteveSandersonMS
Copy link
Member Author

@dougbu I've retried, and tried updating to an even newer SDK that's now available, which also fails with the same error. I've sent a message to First Responders.

@dougbu
Copy link
Contributor

dougbu commented May 24, 2022

The error has changed, meaning we're passed the missing SDK problem. New issues look like breaking changes in the C++ linker. @marcpopMSFT does the following look familiar and who would have more information on the way forward❔

LINK : fatal error C1900: Il mismatch between 'P1' version '20211117' and 'P2' version '20210202' [D:\a\_work\1\s\src\Servers\IIS\AspNetCoreModuleV2\AspNetCore\AspNetCore.vcxproj]
LINK : fatal error LNK1257: code generation failed [D:\a\_work\1\s\src\Servers\IIS\AspNetCoreModuleV2\AspNetCore\AspNetCore.vcxproj]

or

LINK : fatal error C1900: Il mismatch between 'P1' version '20211117' and 'P2' version '20210202' [D:\a\_work\1\s\src\Servers\IIS\AspNetCoreModuleV2\AspNetCore\AspNetCore.vcxproj]
LINK : fatal error LNK1257: code generation failed [D:\a\_work\1\s\src\Servers\IIS\AspNetCoreModuleV2\AspNetCore\AspNetCore.vcxproj]

The strange thing is the errors occur while we're building w/ desktop msbuild. We get that program from the VS installation on the build agents and that tends to change only on Wednesdays. How is .NET SDK get involved here❔

@TanayParikh
Copy link
Contributor

/ping on Doug's message above. Does anyone have context in the area?

@Pilchie
Copy link
Member

Pilchie commented May 26, 2022

@agocke - do you have any C++ contacts that might understand the above? Is this related to the Default Interface Methods changes maybe?

@agocke
Copy link
Member

agocke commented May 26, 2022

I've never seen anything like this before. Maybe @tgani-msft might have an idea

@dougbu
Copy link
Contributor

dougbu commented May 27, 2022

Perhaps we should try yet-another (newer) SDK version❔

@TanayParikh
Copy link
Contributor

Perhaps we should try yet-another (newer) SDK version❔

Just tried to do an update, but turned into a downgrade. I pulled the latest SDK from dotnet/installer and it was only 7.0.100-preview.5.22273.27.

@MackinnonBuck
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@TanayParikh
Copy link
Contributor

TanayParikh commented May 27, 2022

@MackinnonBuck I believe you'll have to try a different SDK version. The one I updated to last night doesn't seem to exist for some reason (despite acquiring it directly from dotnet/installer).

(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) Failed to install dotnet SDK from any of the specified locations.

@MackinnonBuck
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@MackinnonBuck
Copy link
Member

Looks like the newer SDK version has the same C++ linker issue. @tgani-msft do you have any ideas?

@dougbu
Copy link
Contributor

dougbu commented Jun 1, 2022

@MackinnonBuck did this PR run its validation before or after you merged #41866❔ That may have included a fix for the C++ problem

@MackinnonBuck
Copy link
Member

@dougbu That was before #41866 was merged. I'll start another build to see if the problem is fixed.

@MackinnonBuck
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@javiercn
Copy link
Member

javiercn commented Jun 2, 2022

Bumped the SDK version again, let's see

@javiercn
Copy link
Member

javiercn commented Jun 2, 2022

@dougbu @MackinnonBuck seems that the fix didn't flow through just yet.

@javiercn
Copy link
Member

javiercn commented Jun 2, 2022

When this PR gets in, lets make sure we also trigger #41494 as it should contain the fix we need.

@dougbu
Copy link
Contributor

dougbu commented Jun 5, 2022

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@dougbu
Copy link
Contributor

dougbu commented Jun 7, 2022

Problems holding this one up seem to require completion of #41999. Once that's in, will dependencies need to flow all the way through dotnet/installer before this PR can pass validation❔ I saw some comments somewhere about how we choose the compiler but am not sure whether anyone took action.

@MackinnonBuck @javiercn❔❔

@dougbu
Copy link
Contributor

dougbu commented Jun 7, 2022

Actually, that comment was too specific.

  1. Where exactly was the fix for the C++ compiler / linker problems❔
  2. Do we need to wait for anything or just update the SDK version again❔

@javiercn javiercn force-pushed the stevesa/update-sdk-2022-may branch from fc213f1 to a94f421 Compare June 23, 2022 12:03
<VCProjectVersion>15.0</VCProjectVersion>
<Keyword>Win32Proj</Keyword>
<Platform Condition="'$(Platform)' == ''">x64</Platform>
<PlatformToolsetVersion>v143</PlatformToolsetVersion>
Copy link
Member

Choose a reason for hiding this comment

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

FYI @HaoK
I moved the toolset and windows versions to our common Cpp props and removed them from IIS and Installers. So in case you notice them missing from IIS in the future this is why 😉

@BrennanConroy
Copy link
Member

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@HaoK HaoK merged commit df9a5d4 into main Jun 24, 2022
@HaoK HaoK deleted the stevesa/update-sdk-2022-may branch June 24, 2022 01:11
@ghost ghost added this to the 7.0-preview7 milestone Jun 24, 2022
@dougbu
Copy link
Contributor

dougbu commented Jun 24, 2022

A month to get this in is ugly but it's in 🎉

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.