|
2020-04-27
| ||
| 08:19 | • Ticket [7c73262e6f] ad28d8e026c4c227 still broken using 1.0.112.1 status still Closed with 3 other changes artifact: 0b6ee87d7c user: anonymous | |
|
2020-04-25
| ||
| 20:25 | • Closed ticket [7c73262e6f]. artifact: 9ff0cb25f3 user: mistachkin | |
| 16:49 | • Ticket [7c73262e6f]: 5 changes artifact: 61bc10715a user: mistachkin | |
| 16:46 | The core NuGet packages MUST include the pre-compiled binaries for the .NET Standard 2.1. Fix for [ad28d8e026] and [7c73262e6f]. check-in: e96e13ac75 user: mistachkin tags: trunk | |
| 14:00 | • Ticket [7c73262e6f] ad28d8e026c4c227 still broken using 1.0.112.1 status still Pending with 3 other changes artifact: 8de422e455 user: mistachkin | |
|
2020-04-23
| ||
| 21:05 | • Ticket [7c73262e6f]: 3 changes artifact: 11f045c269 user: anonymous | |
|
2020-04-18
| ||
| 13:11 | • Ticket [7c73262e6f]: 3 changes artifact: bef66e7127 user: mistachkin | |
|
2020-04-15
| ||
| 18:04 | • Ticket [7c73262e6f]: 3 changes artifact: d13085cc98 user: anonymous | |
|
2020-04-07
| ||
| 16:30 | • Ticket [7c73262e6f]: 3 changes artifact: 10b043cbda user: anonymous | |
| 16:12 | • Ticket [7c73262e6f]: 3 changes artifact: a84a43bbab user: mistachkin | |
|
2020-04-06
| ||
| 21:41 | • Ticket [7c73262e6f]: 4 changes artifact: a8e450b746 user: mistachkin | |
| 16:02 | • Ticket [7c73262e6f]: 3 changes artifact: 25d934018f user: mistachkin | |
| 15:12 | • Ticket [7c73262e6f]: 3 changes artifact: e6e2cadfa5 user: mistachkin | |
| 15:10 | • Pending ticket [7c73262e6f]. artifact: 1fca2a0305 user: mistachkin | |
| 10:57 | • New ticket [7c73262e6f]. artifact: 9a31d3431b user: anonymous | |
| Ticket Hash: | 7c73262e6f3d77e7c788ca2005d0dce4f04c5167 | |||
| Title: | ad28d8e026c4c227 still broken using 1.0.112.1 | |||
| Status: | Closed | Type: | Incident | |
| Severity: | Important | Priority: | Medium | |
| Subsystem: | NuGetPackage | Resolution: | Fixed | |
| Last Modified: | 2020-04-27 08:19:30 | |||
| Version Found In: | 1.0.112.1 | |||
| User Comments: | ||||
|
anonymous added on 2020-04-06 10:57:43:
The very same null exception with very same call stack happens. I would have commented to the original ticket but I'm not allowed to. mistachkin added on 2020-04-06 15:10:58: This appears to have a different underlying cause than [ad28d8e026c4c227],
which was addressed by check-in [6b6fb5374d] on trunk and subsequently merged
into the 1.0.112 release branch.
Initial analysis has been frustrated by the inability to get visibility into
the assembly loading process when running on .NET Core (3.0).
When using the dedicated test program (testef6), the System.Data.SQLite.EF6
assembly cannot be loaded for reasons that are yet unclear. It produces a
generic error message and very few details. However, when loading the same
assembly via Eagle (for .NET Core), everything appears to work fine.
This leads me to think there is a configuration file issue with the (multiple)
JSON files used to configure the .NET Core assembly loading mechanism.
mistachkin added on 2020-04-06 15:12:34: If you have any additional details which may be useful, please add them to this ticket. mistachkin added on 2020-04-06 16:02:49: Further testing and analysis appears to reveal that the System.Data.SQLite.EF6 assembly included with the 1.0.112.1 does work. Research is ongoing. mistachkin added on 2020-04-06 21:41:47: I am unable to reproduce the issue. mistachkin added on 2020-04-07 16:12:58: In the attached PNG, I see a warning for the System.Data.SQLite.Linq package; however, since that package is not supported when using .NET Standard, I'm not sure what the underlying issue is. The image itself cuts off the warning in the dependencies window. anonymous added on 2020-04-07 16:30:01: I'll try to create a minimalistic sample from scratch. anonymous added on 2020-04-15 18:04:53: Is the .linq file of any use to you, or do you need a zip with .cs+.csproj? mistachkin added on 2020-04-18 13:11:50: Sorry, I don't really use LINQPad. anonymous added on 2020-04-23 21:05:13: The zip file should be more useful, I hope. mistachkin added on 2020-04-25 14:00:53: Thanks, I'll look further into this... mistachkin added on 2020-04-25 16:49:44: This turned out to be a NuGet packaging problem. The issue will be resolved in the NuGet packages versioned "1.0.112.2". Thanks for the help. anonymous added on 2020-04-27 08:19:30: Looks good now :) I wonder that I neither have to reference | ||||