Geek Answers Handbook

Link to library binary version - debug or release version?

Today I asked a question ( Ways to manage the source code ), because I was unsatisfied with the way I manage the source code of my shared libraries. As a result of the answers I found the best method.

Now I am working on my repository, removing all my source code, but as a result, I now have another question ...

While I'm still developing a piece of software, is it better to refer to the debug assembly of the library (at this risk, forget to replace it with the release build later)?

Or, in other words, if I refer to the library release build, will it limit debugging if the debug build of my software works?

+7
c # visual-studio-2008 projects-and-solutions shared-libraries
source share
3 answers

It depends on how closely your project and library are linked during development, but you should generally

  • develop and test the library
  • create release build
  • use this release build in other projects
  • if necessary, temporarily use the Debug assembly to find and solve integration problems.

But when projects are closely intertwined, “temporarily” can cover most of the development cycle.

And there is no way to “forget” to switch, you should always check and double check. But that should not make your decision.

+5
source share

Also check out this article if you want to establish a connection with both. It appears twice in the folder with your links, but in addition to this slight aesthetic quality, it works great.

How to enable the correct link in C # using the "Browser" Tab

0
source share

Any reason not to use project links rather than dll links?

0
source share

More articles:


All Articles