Nullref in .targets file
See original GitHub issueDescription
paket update
with Suave’s faulty spec https://github.com/SuaveIO/suave/issues/638 causes paket to assume .net core, despite framework: net461
being a given constraint in paket.dependencies
. This in turn causes, “Object reference not set to an instance of an object” to be thrown and the build to fail when running xbuild Project.sln
.
Expected behavior
Not to throw null ref exceptions. Not to add .Net core dependencies when the framework target is constrained.
Actual behavior
Throwing null ref.
Known workarounds
Manually remove the paket.targets import that was added.
Issue Analytics
- State:
- Created 6 years ago
- Comments:74 (69 by maintainers)
Top Results From Across the Web
Detecting what the target object is when ...
The most you can hope for is to trap the file and line number where the exception occurred. If you're having problems identifying...
Read more >System.NullReferenceException message in creating ...
Hi everyone, I created a localdb sql server file(School.mdf) in the App_Data folder in an MVC project using .Net Framework 4.8.
Read more >Null reference exception in build
ProductionManager.CheckProduction is throwing a NullReferenceException somewhere inside of it. It's caused by the event system calling ItemSlot.
Read more >Null Reference Exceptions
A NullReferenceException happens when you try to access a reference variable that isn't referencing any object. If a reference variable isn't referencing an ......
Read more >NullReferenceException in C#. What is it and how to fix it?
A NullReferenceException (NRE) is a type of .NET exception. It occurs when a developer tries to dereference a null reference.
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 FreeTop 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
Top GitHub Comments
If this https://github.com/haf/expecto/pull/175 merges, I’ll be moving all my projects to FAKE.
Yes exactly
You can use
strategy: min
I mean yes we could prefer pcl in that case (and add some option around it) but I don’t think that is a good idea going forward. I still don’t get why netstandard dlls wouldn’t work at runtime. There might be a different issue here than paket adding some hacks to prevent netstandard dlls.