-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Enable implicit RID with --sc
#21405
Comments
@richlander I moved this to 6.0.2xx since we're closing down on 1xx. I don't see it as a breaking change to enable this in 2xx since it's loosening the limitations of the CLI. Let me know if you disagree. |
It'd be really nice to get this in .100 to make it easier for folks to deal with NETSDK1179. They go together very nicely. We're also not done with NET1179 #21560 That said, if we cannot make it, .200 is fine. Yes, you are right. It isn't breaking. I was wrong about that. |
@richlander looking at this more closely, the error you're seeing here is NETSDK1031, not NETSDK1179. We plan on enabling implicit RIDs for the Further, the actual change to enable implicit RIDs will be simple if we're not differentiating between the long and shorthand options, but it would get significantly more complex to only have this behavior for the shorthand option. |
Fair enough. Let's make the change in .NET 7 as you say. I changed the milestone. |
The new
--sc
syntax works for self-contained apps, per #19681.It still requires a RID. Let's enable it to work with the implicit SDK RID so that we don't create a breaking change in .NET 7. This argument is new. It also will enable users to get around the new warning with
-r
.This change is some really nice fit-and-finish for .NET 6. This behavior is the original intent of #19576.
This is the behavior with RC2.
The text was updated successfully, but these errors were encountered: