How does one handle .dll dependencies when switching branches in Git? I have only source code in git but when I switch to older branch and want to compile I will be compiling against newer version dependancies as my reference is not in the git repo.
相关问题
- Why does recursive submodule update from github fa
- Extended message for commit via Visual Studio Code
- Emacs shell: save commit message
- Can I organize Git submodules in a flat hierarchy?
- Upload file > 25 MB on Github
相关文章
- 请教Git如何克隆本地库?
- GitHub:Enterprise post-receive hook
- Git Clone Fails: Server Certificate Verification F
- SSIS solution on GIT?
- Is there a version control system abstraction for
- ssh: Could not resolve hostname git: Name or servi
- Cannot commit changes with gitextensions
- git: retry if http request failed
Good flow is to have dependencies described in your source code and a way to clean/fetch anew based on the branch you've just switched to.
In the unfortunate case you have to fetch the dependencies manually, you could probably have multiple working directories for your major branches/releases.