Create a .NET ReadOnlySpan

[wiebe@CARYA]

And this works outside a PPL?

It doesn't for me.

The MS page on the ReadOnlySpan reverts back to Framework 9. So it seems to me Framework 4.7 doesn't even have a ReadOnlySpan object?

The interweb seems to confirm that:

c# - Why can't I assign a string to a ReadOnlySpan using .Net Framework 4.8? - Stack Overflow

BTW. I hope you didn't spend the last 2 years on this 😁.

[PragmaTest]

Yes it works outside a PPL.

I'm using the System.Memory nugget.

I didn't spend the last two years on this 😄 😂

But I'm on the way to upgrade this code and this time I'd like it working inside a PPL.

[PragmaTest]

Wiebe,

For your information the toolkit where this function is used is named LabPcap.

Here you can find a link to a video about LabPcap on my LabVIEW user group.

I'm actively working on making it open-source.

Sébastien

[wiebe@CARYA]

---

@PragmaTest wrote:

Yes it works outside a PPL.

I'm using the System.Memory nugget.

I didn't spend the last two years on this 😄 😂

But I'm on the way to upgrade this code and this time I'd like it working inside a PPL.

---

You might be victim of the RTE hell.

This option makes dlls, ppls and executables always use the newest RTE available. Even in the development environment.

This is horrible, because if you're developing in e.g. LV20, some code (references) doesn't work when it's running in a dll or dll, iff (or when) a newer version of LabVIEW is installed.

I've seen code (calling a dll) work on my system. The exe works on another system, while the code fails on that system. After switching off the option for the ppl, the code worked, but the exe failed. After switching off the option for the exe, both the exe and the code worked. This also means that code that has been working for years suddenly fails after installing LV or a LV exe, that installs a new RTE.

I'd really want this feature, but for now it's broken and causes huge problems.

I'm not sure if or how this relates to .NET. But I can imagine a .NET reference in one RTE doesn't exist in the other. I can't see why this would fail in your example, but I'dd check it to be sure.