Path to 1.0.1

[rkosafo]

This is to track issues/tasks on the path to 1.0.1.

• Upgrade Rezoom to 1.0.1 (package not available)
• Upgrade FParsec-Pipes to 1.1.1 (gives an error)
• Test TSQL
• Test Sqlite
• Test Posgres
• Fix error when select has only 1 field

[rkosafo]

@rspeele I get the error below when it was updated to FParsec-Pipes 1.1.1. FParsec-Pipes 1.1.1 works fine.

FileLoadException: Could not load file or assembly 'FParsecCS, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

I'm suspecting it has something to do with A strongly-named assembly is required. Any idea if there is any difference between the libraries besides the version numbers. Could it be signing related?

[rspeele]

Haven't had much chance to look at this one, but I made a console app in .NET Framework and .NET Core referencing FParsec-Pipes and wasn't able to get the same problem to occur. Nothing changed between 1.1.0 and 1.1.1 other than this commit: rspeele/FParsec-Pipes@69b62b5

[rkosafo]

Is the library signed? Could that be a reason or vice versa?

[rspeele]

Yes, fparsec-pipes is signed. The FParsecCS assembly is part of the base FParsec library but I don't know why it wouldn't be signed - it looks like it is when I reference it from a console app.

…

On Sun, Mar 24, 2019 at 3:54 PM Richard ***@***.***> wrote: Is the library signed? Could that be a reason or vice versa? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#42 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABj-WlDaa9YO1ulZnhwXEE25HelBpPdIks5vZ9fvgaJpZM4cBW-v> .