Missing vcruntime140.dll and vcruntime140_1.dll dependencies about blingfire HOT 4 OPEN

Instead of adding the DLLs, could you compile the package to be independent of the runtime?

from blingfire.

Thanks for the suggestion. Are you suggesting to add the project to our solution and compile it as part of the solution instead of using the NuGet package? Just trying to clarify what the proposal is.

from blingfire.

IMHO, it's always easier when you can consume a single nuget package that contains the compiled binary for each platform - we do something similar with the RocksDB package we distribute: https://github.com/curiosity-ai/rocksdb-sharp

from blingfire.

For .Net SDK or .Net core, we expect it to be part of the system. For VC runtime, I would assume that same since the system32 directory does contain the runtime dlls. In this case, vcruntime140.dll was found but vcruntime140_1.dll was missing in some of our environments in system32 dir. Since Azure manages them, is this an issue with Azure? If the NUGet carried the missing dll until it is widely available (especially in Azure), it might have mitigated this issue and saved us investigation time. Our workaround was to bin place these Dlls in the app directory. This is temporary fix until we find a better solution for this issue. At this point, I am not sure what the better solution is.

from blingfire.