All geek questions in one place

Should I include dependencies for my releases?

Should I include dependencies when releasing my common projects, such as CommonUtils, or just indicate which dependencies should be specified when they will be used?

+3
source share
4 answers

You do not want to work if you find out your dependencies.

  • What packages do I need?
  • What to do if it is unavailable? (dead server, provider is down)
  • Which version of each do I need?
  • What to do if it is unavailable? (a new version)
  • How to load each of them?
  • How to install each of them?

Protect your software from disappearing / inaccessible dependencies. Protect your users from pain when defining this material.

: , , . ( ).

+2

, .

GAC, .

+1

(, ). 3- dll. Framework. , , , . ( , DLL- ), .

0

I would include dependencies with your version. When you release, you want to control how your application runs and how it behaves. If a user is required to install the dependencies, then they can choose a compatible version, however it may not make X or make X different. Which will change the behavior of your application and increase the support and maintenance of applications.

0
source

Source: https://habr.com/ru/post/1698574/

More articles:


All Articles