CODEWITHSUNDEEP
.netdeploymentdll
open-collar
open-collar

Reputation: 1424

How to manage versions and compatibility when publishing a library in .NET

I manage a library project that exposes a range of interfaces and library classes. Our user base is expanding and we want to adopt a more frequent release cycle. How do I avoid forcing my users needing to recompile every time I release?

Upvotes: 1

Views: 89

Answers (2)

TonySalimi
TonySalimi

Reputation: 8427

If your interfaces are changing in each release, then there is no way to avoid your users from recompiling the code. But by using some practices, you may lessen this re-compilation process:

  1. Hide the details of your library as much as you can to your users.
  2. Try to lessen the dependency of your exported stuff, as much as you can.
  3. Do not put too much services in a single interface. Cut your interfaces properly.

Upvotes: 0

Henk Holterman
Henk Holterman

Reputation: 273179

Deploy to the GAC, manage your publisher redirect policies.

Assemblies in the GAC (can) have their own release cycles.

Upvotes: 2

Related Questions