Improve RID and `publish` UX
See original GitHub issueI’ve been defining several experiences that are intended to improve Runtime Identifier (RID) and/or publish
experiences. It makes sense to catalog those all in one place since its easy (including for me) to lose track of them.
Where is this all heading? There are two primary goals:
- Better differentiate
build
andpublish
and use them to better support common developer workflows. There are properties that you cannot put in project files today because they won’t do the right thing with eitherbuild
orpublish
since there is no good way to conditionalize them. - Reduce the degree to which developers have to use the RID syntax and the
-r
argument while at the same time runtime-specific apps are the best option in many cases.
Issue Analytics
- State:
- Created a year ago
- Reactions:12
- Comments:9 (9 by maintainers)
Top Results From Across the Web
[Megathread] Engineering Status of RID Improvements and ...
Improve RID and publish UX #26446. Open. Use the Implicit SDK RID for RID-Specific Apps by Default #26143.
Read more >6 Tips to Improve Your Product's End-User Experience
6 tips to improve your end-user experience · 1. Design for ease of use · 2. Be consistent and accessible · 3. Establish...
Read more >12 Tactics for Improving Your Website's UX in 2022
1. Consider Your Target Audience in All Design Decisions ... If you're selling a product or service online, hopefully, you're already thinking ...
Read more >10 Tips to Improve UX/UI Design of Web App
As a first step, conduct thorough user research, ask the right questions. Not how to improve user experience on a website or app...
Read more >Tips to Improve Your Site's UX in 2022
UX Tips for Improving Your Website · 1. Test · 2. Keep It Simple · 3. Use White Space Generously · 4. Get...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was thinking that maybe
RuntimeSpecific=false
could be the answer to point 1. Or put another way, I don’t think a RID should be the gesture. One of my underlying goals (across multiple features I’ve been working on) is to make specifying RIDs directly less common. They are confusing, even for folks that define them.Separately,
any
doesn’t quite do the right thing, at least per my experiments with it. I did that because @vitek-karas told that “any
doesn’t do what you think” and the experiments seemed to prove that out. My observation was thatany
resulted in less not more RID-specific NuGet assets restored/in my bin folder. I didn’t pursue why. Vitek would have more insight into why.I’ve already started talking to the VS Publish folks. I’ll setup a meeting for that so we can make some good decisions.
My preferred ordering:
PublishSelfContained
That would put us in a place where a project can default its publish behavior to practically any combination of configuration=Release, self-contained (for current RID), trimmed, single-file, etc.