Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Solution-level error when a RuntimeIdentifier is specified
See original GitHub issueRelated to a subset of #696 that won’t be fixed by #828.
If a solution build has a RID specified, it will fail.
This can be because (after #828) it double-builds a library (once with RID specified from the solution’s global properties, once with it removed):
Or, if nothing is done, this will fail when attempting to specify a RID on a project that doesn’t need one.
If VS and the CLI distributed a solution-extension target that ran before Build and errored when '$(RuntimeIdentifier)' != '', it would at least provide guiderails to nudge users back into the more supported scenarios. It could say something like Building a solution with a specific RuntimeIdentifier is not supported. If you would like to publish for a single RID, specifiy the RID at the individual project level instead.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@sfoslund If you’re looking for issues to tackle, this one is a candidate
I’ve split off my issues into the one linked above since it’s still happening regardless of a runtime id.