Repository navigation
Microsoft.ML.TensorFlow is currently broken #1027
Description
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 ofMicrosoft.ML.TensorFlow. -
What happened?
I don't get a reference to theMicrosoft.ML.TensorFlow.dll. I only get a reference toDnnAnalyzer.dll
-
What did you expect?
I expected to get a reference toMicrosoft.ML.TensorFlow.dllso 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.
Activity
ericstj commentedon Sep 25, 2018
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 commentedon Sep 25, 2018
We have the
Maml.execommand line tool, which currently doesn't ship publicly. We've discussed making it a "global tool", but haven't executed on that plan.eerhardt commentedon Sep 25, 2018
@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 commentedon Sep 25, 2018
Whoops you're right sorry, got confused about the builds breaking.
TomFinley commentedon Sep 25, 2018
Anyway,
DnnAnalyzershould not be shipped in the nugets. It should have been rewritten as a command, but not in the nugets.