Machinelearning: Microsoft.ML.TensorFlow is currently broken

[eerhardt]

System information

• OS version/distro: all
• .NET Version (eg., dotnet --info): any

Issue

• What did you do?
  Create a .NET Core console project that references the latest version of Microsoft.ML.TensorFlow.

• What happened?
  I don't get a reference to the Microsoft.ML.TensorFlow.dll. I only get a reference to DnnAnalyzer.dll
  

• What did you expect?
  I expected to get a reference to Microsoft.ML.TensorFlow.dll so I could call methods in it.

Notes

The reason this happens is because we are including the DnnAnalyzer.dll in the lib\netcoreapp2.0 directory of the Microsoft.ML.TensorFlow nuget package:

NuGet only picks assets from 1 of these folders. And since my app is .NET Core, it only picks the assemblies from the lib\netcoreapp2.0 directory.

/cc @ericstj @yaeldekel @abgoswam

[ericstj]

We shouldn't be putting DnnAnalyzer in the lib folder at the least. Perhaps we should consider a better place for tooling to get this info. Does ML.NET have any other command-line tools? Have we considered a CLI extension?

[eerhardt]

We have the Maml.exe command line tool, which currently doesn't ship publicly. We've discussed making it a "global tool", but haven't executed on that plan.

[eerhardt]

@tomfinley - I think you may have been mistaken. This isn’t the test break that just occurred. This is a problem with the assets in our NuGet packages. Specifically in the TensorFlow package.

[TomFinley]

Whoops you're right sorry, got confused about the builds breaking.

[TomFinley]

Anyway, DnnAnalyzer should not be shipped in the nugets. It should have been rewritten as a command, but not in the nugets.