-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Build 3.0 site extension #17758
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
Build 3.0 site extension #17758
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
| PackagePath="$(_BasePackagePath)\shared\Microsoft.AspNetCore.App\$(MicrosoftAspNetCoreAppPackageVersion)\" | ||
| PackagePath="$(_BasePackagePath)\shared\Microsoft.AspNetCore.App\$(AspNetCoreMajorMinorVersion).0\" | ||
| /> | ||
| <!-- Always use Major.Minor.0 so that if we have to produce a new SiteExtension during a patch build it will still work for non-patch runtimes. i.e. 3.0.0 dotnet will search for 3.0.0 and below and wouldn't find a 3.0.1 folder path --> |
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.
👍
|
@BrennanConroy are you able to get to this fairly soon? Personally I'd prefer to get this into the next patch available. |
|
As far as I'm aware this is building correctly and effectively good to go. We need to decide whether we are building it for 3.0 or skipping. And then figure out how to get the 3.0 bits into a 3.1 build. |
The Site Extension itself is "versionless" (i.e. users should always install the latest). I'd like us to build one out of |
Yeah, we need to build and "release" the 3.0 one first. Then we can reference the 3.0 one in a 3.1 build. |
|
Got it. Let's get this PR ready to take in March. |
84c05f4 to
2278e77
Compare
|
Closing in favor of #18568 |
Start of #15381