I know there are other questions regarding this subject, and I've looked at this question, but I'd like to see a little bit more discussion and information on both sides of this – is it a better practice to add a project to a solution and reference the project, or to add a reference to the .dll?
Visual-studio – Project reference vs. DLL Reference – Which is better
referencevisual studio
Related Topic
- C++ – Is the practice of returning a C++ reference variable evil
- Python – How to pass a variable by reference
- C# – How to debug a referenced dll (having pdb)
- Visual-studio – MSBuild doesn’t copy references (DLL files) if using project dependencies in solution
- C# – How to remedy “The breakpoint will not currently be hit. No symbols have been loaded for this document.” warning
- Visual-studio – How to install a NuGet package into the second project in a solution
- .net – How to fix the Visual Studio compile error, “mismatch between processor architecture”
- Asp.net-mvc – Visual Studio debugging/loading very slow
Best Answer
It's not much of a choice. If you have a solution with both projects then use a project reference. If your solution doesn't have the project then you have to use an assembly reference.
So the real question should probably be: do I create a solution with both projects? Yes, as long as the project is still in the debug stage and liable to require bug fixes.