Body: <p>I've got a project which consists of a number of executables and a lot of common libraries. Also lots of NuGet dependencies involved.</p>
  
  <p>I want to output them into one folder. 
  How to be sure that all of these executables are using compatible NuGet libraries and can be put into one folder?</p>
  
  <p>For now I wrote a small node.js snippet which analyzes project.lock.json and finds referenced libraries of different versions. Well it's rather hard and it requires some projects to reference libraries just to fix versions.</p>
  
  <p>Is there a better way? Can I somehow create a meta project which will resolve everything by itself for me?
  Is it ok to build solution executables sharing same libs into one folder? (I don't think so)</p>
  
Comments: CC BY-SA 3.0
Comments: 2017-09-22T13:53:22.473Z
Comments: What is your purpose for outputting them into one folder? Is it for a new project? Is it for repository organization?
Comments: Preston Martin
Comments: CC BY-SA 3.0
Comments: 2017-09-22T19:57:39.870Z
Comments: One self contained .NET Core project might have 50 files. Another one 55. 48 might have same names. So I need a way to understand if 48 are actually same version or not.
Comments: norekhov
Comments: CC BY-SA 4.0
Comments: 2019-12-22T13:56:10.503Z
Comments: Thank you for posting a question. Could you modify the question so that it contains the attempts you have done in order to solve the issue?
Comments: 030
Tags: <dotnet>
Title: Building multiple projects into one directory in VS and/or .NET Core
UserDisplayName: norekhov
ThreadText: # Building multiple projects into one directory in VS and/or .NET Core
  
  (Asked by: username_0 on 2017-09-21)
  
  I've got a project which consists of a number of executables and a lot of common libraries. Also lots of NuGet dependencies involved.
  
  I want to output them into one folder.
  How to be sure that all of these executables are using compatible NuGet libraries and can be put into one folder?
  
  For now I wrote a small node.js snippet which analyzes project.lock.json and finds referenced libraries of different versions. Well it's rather hard and it requires some projects to reference libraries just to fix versions.
  
  Is there a better way? Can I somehow create a meta project which will resolve everything by itself for me?
  Is it ok to build solution executables sharing same libs into one folder? (I don't think so)
  
  **Tags:** dotnet
  
  > **Comments:**
  > **username_1**: What is your purpose for outputting them into one folder? Is it for a new project? Is it for repository organization?  
  > **username_0**: One self contained .NET Core project might have 50 files. Another one 55. 48 might have same names. So I need a way to understand if 48 are actually same version or not.  
  > **username_2**: Thank you for posting a question. Could you modify the question so that it contains the attempts you have done in order to solve the issue?  
  
  ---
  
  ## 0 answers
  
  