-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Update SDK #41798
Conversation
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.
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
@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. |
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❔
or
The strange thing is the errors occur while we're building w/ desktop |
/ping on Doug's message above. Does anyone have context in the area? |
@agocke - do you have any C++ contacts that might understand the above? Is this related to the Default Interface Methods changes maybe? |
I've never seen anything like this before. Maybe @tgani-msft might have an idea |
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 |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@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).
|
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Looks like the newer SDK version has the same C++ linker issue. @tgani-msft do you have any ideas? |
@MackinnonBuck did this PR run its validation before or after you merged #41866❔ That may have included a fix for the C++ problem |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Bumped the SDK version again, let's see |
@dougbu @MackinnonBuck seems that the fix didn't flow through just yet. |
When this PR gets in, lets make sure we also trigger #41494 as it should contain the fix we need. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
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. |
Actually, that comment was too specific.
|
Trying the installer version
Co-authored-by: Doug Bunting <[email protected]>
fc213f1
to
a94f421
Compare
<VCProjectVersion>15.0</VCProjectVersion> | ||
<Keyword>Win32Proj</Keyword> | ||
<Platform Condition="'$(Platform)' == ''">x64</Platform> | ||
<PlatformToolsetVersion>v143</PlatformToolsetVersion> |
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.
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 😉
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
src/Servers/IIS/AspNetCoreModuleV2/CommonLibTests/CommonLibTests.vcxproj
Show resolved
Hide resolved
A month to get this in is ugly but it's in 🎉 |
Regular build-ops update