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.
dotnet run ./path/to/project throws Object reference not set to an instance of an object.
See original GitHub issueSteps to reproduce
Steps fail on both Windows or OSX
clone https://github.com/NotMyself/coreapp
cd coreapp & dotnet restore
dotnet run ./src/UIMvc
dotnet test ./test/UIMvc.Tests
Expected behavior
web project should compile and run test project should compile and run
Actual behavior
web project throws Error: Object not set to an instance of an object. test project runs as expected
Environment data
dotnet --info output:
OSX via iTerm bash .NET Command Line Tools (1.0.0-preview1-002702)
Product Information: Version: 1.0.0-preview1-002702 Commit Sha: 6cde21225e
Runtime Environment: OS Name: Mac OS X OS Version: 10.11 OS Platform: Darwin RID: osx.10.11-x64
Windows via PowerShell .NET Command Line Tools (1.0.0-preview1-002702)
Product Information: Version: 1.0.0-preview1-002702 Commit Sha: 6cde21225e
Runtime Environment: OS Name: Windows OS Version: 10.0.14342 OS Platform: Windows RID: win10-x64
Issue Analytics
- State:
- Created 7 years ago
- Reactions:13
- Comments:12 (3 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
In general, I don’t think we should throw exceptions. 😄
Ofc. The discern could happen with a special token, e.g.
--or something like that, that would indicate others are to be passed down. Just a though.