[MONGOCRYPT-471] Improve libmongocrypt packaging for .NET/C# bindings Created: 11/Aug/22 Updated: 17/Mar/23 |
|
| Status: | Backlog |
| Project: | Libmongocrypt |
| Component/s: | .Net Binding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | James Kovacs | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
libmongocrypt. is currently packaged as a content file. This can result in the unmanaged libraries not getting copied properly during a NuGet restore as mentioned in |
| Comments |
| Comment by Nicholas Chen [ 17/Mar/23 ] |
|
Our teams are also getting the same issue with OctoPack. Downgrading core driver for now but would like to upgrade so that we can eventually update our mongo databases to latest. |
| Comment by Marcin Radziszewski [ 30/Jan/23 ] |
|
Hi, is there any progress on this? While it seems like it doesn't harm anyone when building solutions in VS, it turns out to be an issue when using OctoPack when MongoDB.Libmongocrypt is referenced in multiple projects. |