Weird behaviour with .NET constructor node and GZipStream compression

[ThiCop]

Hello Stinus,

A Corrective Action Request with the number 493662 has been filed.

Is there anything else I could do to assist you?

[Stinus Olsen]

Hi Thierry

Thanks for the feedback!

I have attached a link to this thread in the 2014 Septembers Monthly Bug list here.

Thanks you very much for your help in propagating this..

Best Regards

Stinus

[ThiCop]

Hello Stinus,

No problem...

If I can help with other issues, then just let me know.

[JackDunaway]

---

@ThiCop wrote:

A Corrective Action Request with the number 493662 has been filed.

---

Hi Thierry, any update on CAR #493662? I'm running into this issue also. Does there exist a workaround?

[ThiCop · Accepted solution]

Hello Jack,

Sorry for the late reply.

Holidays/vacation came in the way.. 🙂

Currently I cannot provide you with more (useful) updates about the status of the CAR.

There were 3 "work-arounds" that I could think of originally for this specific constructor.

Some of them are better than others:
- Using the dotNET 2.0 version from LabVIEW 2012 SP1 does work, because there is no overloading in this version of the .NET Assembly. (work-around 1)
- Creating your own custom/new Assembly (without these types of overloads) in Visual Studio and calling that one from inside LabVIEW 2013 or 2014 (work-around 2)
- Do not use Assemblies with these types of overloads (not really a work-around), but use alternative ones.

If you want to brainstrom about other work-arounds, then don't hesistate to let me know.

[Sev_K]

Hi,

For those who might find it helpful I've created a .net assembly in C# that allows you to compress and decompress strings in LabVIEW 2014 using Gzip library. (workaround #2 in Thierry's post above)

[ThiCop]

Thanks for the update and the efforts on this!

[WireStraits]

@Sev_K wrote:

Hi,

For those who might find it helpful I've created a .net assembly in C# that allows you to compress and decompress strings in LabVIEW 2014 using Gzip library. (workaround #2 in Thierry's post above)

---

The compressed string seems to be longer and more character limited than needed.  Is this doing base64 encoding or something?  Do you have a version without such encoding?

[bseguin]

Dear all, Yes it is a old thread... but I cannot find a suitable solution... All my data are in the database and not recoverable since I cannot uncompress them. Anyone has a solution yet?

I am using LabVIEW 2017

Thanks

Benoit

[Stinus Olsen]

I ended up writing a small .NET assembly that supports GZip compression/decompression with and without base64 encoding..

So, from reading your post it still seems this is an issue in LV2017?

BR

Stinus