Available as Nuget package?

[JeffreyZolaVisibilEdi]

Is this version mature enough to be made available as an option within Nuget?

I stumbled upon it when looking for something to replace OOPFactory.X12 that is directly supported by .NET Core 2.2 and higher. We have been using the OOPFactory libraries for many years with .NET 4.x, but are moving toward .NET Core and want a natively compatible solution for our X12 HIPAA parsing needs!

Thanks!
Jeff

[anjalirawat11]

In .net core 2.2 it is giving warning

" Warning NU1701: Package 'OopFactory.X12 3.0.8.1' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.2'. This package may not be fully compatible with your project."

I want compatible solution for this.

[nwlynch]

In .net core 2.2 it is giving warning

" Warning NU1701: Package 'OopFactory.X12 3.0.8.1' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.2'. This package may not be fully compatible with your project."

I want compatible solution for this.

Did you want to compile it to use your.NET framework version (v4.6.1) or just compile without any warnings?

You should be able to get it to compile with your runtime version, but some code updates could be required.

[nwlynch]

Is this version mature enough to be made available as an option within Nuget?

I stumbled upon it when looking for something to replace OOPFactory.X12 that is directly supported by .NET Core 2.2 and higher. We have been using the OOPFactory libraries for many years with .NET 4.x, but are moving toward .NET Core and want a natively compatible solution for our X12 HIPAA parsing needs!

Thanks!
Jeff

Hi,
I've been using it for a while now with the only changes from the original source being the checking of arguments in the command line utilities.

I guess the whole codeset could be updated to use a new framework version, but I never really thought anyone else was interested in using it.

[tendimensions]

It's definitely getting used. I followed this repo because I was using it a couple of years ago. I'm sure there are people using this. It's very helpful!

[JeffreyZolaVisibilEdi]

I am currently using the package to parse X12 271 Eligibility Responses.

I agree with tendimensions that it is helpful - except that I found that it did fail to properly classify at least one sub-loop of these responses.

I am using it within a mature .NET 4.7x application as well as within a .NET Core application (or set of applications) I am developing from scratch based on my own custom .NET Standard libraries that will be imported into the mature application at some stage.

At some point in the future, I intend to explore parsing other X12 document types as well as constructing some.