So we all use nuget now - I think, but when creating a nuget version of a package what is the best way to tie it in.
My instinct is not to create a dependency on umbraco because if your umbraco installation hasn't also be nuget'ed then i have no idea what might happen.
but not putting the dependency in makes an umbraco package an odd thing you can import into any project.
what do people think ? especially those who actually do use nuget for dev
On uComponents, our early releases on NuGet didn't have a dependency on UmbracoCms.Core (actually I don't think it even existed back then).
The only gotcha that we heard back from developers was that they couldn't use it without having Umbraco installed (which we assumed that they would have) ... other than that, it didn't cause any issues - at least none that we got feedback on.
I think you'd be fine not specifying a specific Umbraco version - as long as you documented (in a README) the minimum compatible version.
creating nuget packages for Umbraco
So we all use nuget now - I think, but when creating a nuget version of a package what is the best way to tie it in.
My instinct is not to create a dependency on umbraco because if your umbraco installation hasn't also be nuget'ed then i have no idea what might happen.
but not putting the dependency in makes an umbraco package an odd thing you can import into any project.
what do people think ? especially those who actually do use nuget for dev
On uComponents, our early releases on NuGet didn't have a dependency on UmbracoCms.Core (actually I don't think it even existed back then).
The only gotcha that we heard back from developers was that they couldn't use it without having Umbraco installed (which we assumed that they would have) ... other than that, it didn't cause any issues - at least none that we got feedback on.
I think you'd be fine not specifying a specific Umbraco version - as long as you documented (in a README) the minimum compatible version.
Cheers,
- Lee
is working on a reply...