Closed olmobrutall closed 6 years ago
No activity here, so I've published a Nuget from my Fork: https://www.nuget.org/packages/unofficial.microsoft.sqlserver.types/
There's (now) 5 different SqlServer Types packages on Nuget.org. It's a giant mess. You can just build this solution and you'll have a nuget as output that you can put in your local nuget repo. TBH I think it's rather bad form just grabbing someones repo as is, then throwing it on nuget just because it took me a few days to respond.
Hi @dotMorten,
I know was a bit unfriendly, but I'm migrating Signum Framework and many applications depending on it to .Net Core. I didn't want to add this repo as a submodule on each application for something that looks like a temporal problem anyway... (will SQL Server team make an official version for .Net Core some day? who knows 😞) So making a Nuget looked like the best option to move forward.
I gave you credit (Authors dotmorten and olmobrutall) and I'm happy to give you ownership of the nuget if you're happy with the name. Otherwise I'll use yours and delete mine when you make one.
I'm currently migrating https://github.com/signumsoftware/framework to .Net Core, this project uses
SqlGeometryId
andSqlHierarchyId
(I made a pull request to add support), so I would like to take a dependency to this project.Is there a nuget package?
If not, could you create one, or should I?