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.
Collapse netstd/framework packages
See original GitHub issueI know that we’re eventually going to move to a full csproj-based solution anyhow, but I wonder if we wouldn’t be better off collapsing the netstd projects so we have a single set of projects, not unlike xBehave.net and SelfInitializingFakes.
It may even make migrating to the new csprojs easier.
Update after discussion below, we’ve decided to wait until after we switch to VS2017’s new csproj format.
When we do make this switch, though, we may also want to
- generate a .net45 lib, which will
- allow event handlers whose event args don’t extend
EventArgs(#1008)
- allow event handlers whose event args don’t extend
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (9 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
I updated the description to refer to #1008. 👅
It may be better to wait for VS2017 RTM to bed-in a little, and make the switch to the new csproj, before doing this.