Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COI guess you are implying to move from source inclusion to DLL inclusion with reasonable dependency management. If it is, it sounds tempting, but right now we develop the shared libraries as part of the enclosing solutions. Seems a rather heavyhanded way to solve the problem.
      singulars
    2. COIf, as I understood, they are seperate VS projects, it should not pose a problem in terms of feasability, but indeed it is not the quick hack that you may be looking for... If you are worried about debugging then nuget supports linking to a symbol source server to keep the debug experience, but if there is a lot of back and forth between the main and the supporting projects, this could be an issue. I am a bit hesitant w.r.t. the lack of elegance of git submodules and I wanted to suggest an alternative that you did not list (and that supports versioning!).
      singulars
    3. COI'm a bit sad that this option wasn't available when I still worked with .NET as a team. Visual Studio is notoriously stupid when it comes to dependencies. This approach has a lot of advantages. But the most important to me is that from a developers perspective projects will become faster to set up, compile and program for. When I check out a new project I just fetch all the libraries needed and I just have to compile the project libraries to run it. Not only that but gone is the clutter of those subprojects which make projects much easier to understand.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload