Build/Test Issues

.NET Core unit tests for project build as exe

Started by piotr_s on 4,837 views

The version above should be production ready, so there's no need to wait for it to hit the download page if it works. The dev builds all have a large amount of automated testing behind them, and I try to make them reliable enough that people can make use of important things without needing to wait for full releases.

How is it that you've configured a different assembly name from the project name? Was this using the AssemblyName build property? I ask as NCrunch should be able to handle this. The .deps modifying code above works using the AssemblyName build property, and presently I don't know of a way to cause a deviation from the assembly name inside the .deps.json.

Edited

Yes, different assembly name has been configured using AssemblyName property in project file.

Post a reply

Log in to reply.