Opened 12 years ago
Last modified 4 months ago
#847 new enhancement
NuGet packages
| Reported by: | jng | Owned by: | jng |
|---|---|---|---|
| Priority: | major | Milestone: | 4.2.0 |
| Component: | Build System | Version: | 3.7.0 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description
For ease of consumption by .net applications, it would be really nice to have FDO available as NuGet packages
Change History (2)
comment:1 by , 12 years ago
comment:2 by , 4 months ago
| Milestone: | 3.7.0 → 4.2.0 |
|---|
The .net Core/5+ nuget packaging story (especially around .net libraries with native dependencies) is much more simpler.
Since the .net bindings now target net6.0. This is something worth investigating again.
Note:
See TracTickets
for help on using tickets.
Just a mental note.
Our current approach is wrong. Look to the SQLServerCompact nuget package as an example of how our FDO nuget packages should look like:
https://bitbucket.org/davidebbo/nugetpackages/src/1cba18b864f7/SqlServerCompact/
Their package correctly sets up post-builds to copy from the package source directory, which is what we want for FDO as well.