Updating the dotConnect references in a moderately sized solution (60+ projects).
Please, please create a NuGet package! I notice that the dotConnect Express is already supported in NuGet.
NuGet support
Re: NuGet support
Other editions can not be distributed via NuGet because only run-time assemblies can be supplied in this way. Standard/Professional editions include design time which can be installed only with a full installation package.JeffCertain wrote: I notice that the dotConnect Express is already supported in NuGet.
Re: NuGet support
NuGet packages would make dotConnect deployment so much easier!
You could provide an installation package for the Visual Studio integration and provide the runtime assemblies via NuGet. For some applications the Visual Studio integration might not even be needed (Code First, etc.).
You could provide an installation package for the Visual Studio integration and provide the runtime assemblies via NuGet. For some applications the Visual Studio integration might not even be needed (Code First, etc.).
-
- Posts: 4
- Joined: Mon 27 Jul 2015 23:17
Re: NuGet support
mko has the right idea. We're using EF6 code first.
At this point, I'm going to have to extract the DLLs, bundle them in a custom NuGet package, host my own server... you get the idea.
But that's less work than updating the project references manually a couple of times.
At this point, I'm going to have to extract the DLLs, bundle them in a custom NuGet package, host my own server... you get the idea.
But that's less work than updating the project references manually a couple of times.
Re: NuGet support
Thank you for your feedbacks. We will investigate the possibility of implementing our NuGet server (license management).
That is a current workaround (documentation).JeffCertain wrote:At this point, I'm going to have to extract the DLLs, bundle them in a custom NuGet package, host my own server...