Add sample for use with Binary dataset

[PeterPann23]

[Enter feedback here]

Would be nice to show how a binary file can be used (and re-used) to use strong typed data

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d77f7787-449e-9eeb-9dc8-e7ca22091538
• Version Independent ID: 2dca3efe-4be8-72c3-0e71-226c2183cc89
• Content: DataOperationsCatalog.CreateEnumerable(IDataView, Boolean, Boolean, SchemaDefinition) Method (Microsoft.ML)
• Content Source: dotnet/xml/Microsoft.ML/DataOperationsCatalog.xml
• Product: dotnet-ml-api
• GitHub Login: @sfilipi
• Microsoft Alias: johalex

[CESARDELATORRE]

@PeterPann23 - Can you clarify what do you mean with a 'binary file'?
Do you mean an IDV dataset? (.IDV is the IDataView proprietary serialization format).

Or do you mean a different kind of binary file?

Thanks,
Cesar

[PeterPann23]

Yes, yes I do, there is a convention to call/ save it using .idv extension, however
this suggestion is not written anywhere in the the code comments and the methods are called
mlContext.Data.SaveAsBinary(dataView, fileName);
mlContext.Data.LoadFromBinary(fileName);

so to call it binary or to call "Internal Data View" or what does it stand for...

[CESARDELATORRE]

@PeterPann23 - I agree. This should also be in the docs.microsoft.com pages.
I just created another issue in there related to this:

dotnet/docs#12451

[najeeb-kazmi]

@CESARDELATORRE @PeterPann23 is this related to #3661 ? I have a PR #3745 out that adds a sample for Binary load/save, as well as Text load/save.

[CESARDELATORRE]

@najeeb-kazmi - Yep! Completely related! That PR is great to have.
But we should also document it in a more "tutorial" approach at docs.microsoft.com so that's why I opened another issue at docs.microsoft.com

Thanks Najeeb! 👍

[najeeb-kazmi]

@CESARDELATORRE @PeterPann23 - Shall we close this issue then, since it's covered by the PR on the ML.NET side, and we have another issue to track the tutorial on docs.microsoft.com?

[abgoswam]

Closing this issue . PR #3745 addresses this