Stuck on an issue?

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.

Null ref error while publishing with Runtime identifier set as win7-x64

See original GitHub issue

Call stack:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.NETCore.Build.Tasks.LockFileExtensions.IsPortable(LockFileTarget lockFileTarget)
   at Microsoft.NETCore.Build.Tasks.ResolvePublishAssemblies.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
        Done executing task "ResolvePublishAssemblies" -- FAILED.

Log attached: Publish_RID_NullRef.txt

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

eerhardtcommented, Oct 11, 2016

Can we call the restore target directly and pass the RID?

Calling restore from another target inside of MSBuild doesn’t work. Calling restore will can bring down different .props/.targets files. These .props/.targets files won’t be loaded by MSBuild because it has already imported all the .props/.targets files.

One thing you could do is define $(RuntimeIdentifier) or $(RuntimeIdentifiers) in your project. Then when restore is run, it will automatically restore for those RIDs, since those properties are set.

@rainersigwald @AndyGerlicher @emgarten @rrelyea @nguerrera

0reactions

vijayrkncommented, Oct 11, 2016

Can we call the restore target directly and pass the RID?