Tom Bogle

Based on this: https://stackoverflow.com/questions/45997649/geckofx-core-system-dllnotfoundexception, I'm guessing it is because of a missing Visual C++ redistributable.

Seems to work for me. Can you confirm that this is fixed?

*[`Palaso.sln` line 30 at r1](https://reviewable.io/reviews/sillsdev/libpalaso/1317#-NwKFbl4BlwI7aMtL8jS:-NwKIT-f-YKJIYaJHes1:b-pup2tv) ([raw file](https://github.com/sillsdev/libpalaso/blob/6f47b225bff805c6446c80c0eda091ae10498f6f/Palaso.sln#L30)):* Previously, tombogle (Tom Bogle) wrote… Now I'm wondering if we should actually be trying to split this stuff into Forms vs. non-Forms DLLs....

Not sure when I'll be able to get to this.

According to [this article](https://docs.microsoft.com/en-us/nuget/concepts/package-versioning), "floating" version numbers are supported: => When using the PackageReference format, NuGet also supports using a floating notation, *, for Major, Minor, Patch, and pre-release suffix...

Maybe we could write a new SIL BuildTask that would be able to go through the PackageReference elements for libpalaso packages and turn hard version numbers into floating version references....

> A different direction would be to use https://github.com/marketplace/actions/nukeeper-action, with the "repo" option, to automatically generate PRs when libpalaso is upgraded. Looks like SIL.FwBuildTasks uses [WhiteSource Renovate](https://www.whitesourcesoftware.com/free-developer-tools/renovate/) to do this...

In practice (and certainly on a 32-bit machine), strings can't really get that big (see: https://stackoverflow.com/questions/140468/what-is-the-maximum-possible-length-of-a-net-string). Long before we get close to MaxLength, we're going to either get an OutOfMemoryException...

WIP: https://github.com/sillsdev/libpalaso/pull/845

I'm doing some fixing in this area currently, so this might actually be a good time for me to try to break it into two parts. Give me a couple...