CodemerxDecompile icon indicating copy to clipboard operation
CodemerxDecompile copied to clipboard

Creating projects for multiple assemblies is painful

Open CoolDadTx opened this issue 3 years ago • 0 comments

Often you want to create a set of projects (one for each assembly opened). Currently you select an assembly and then use the menu to create a project. The folder you select then gets the solution and project file while the files themselves are in child folders based on namespace. This mostly, but does not completely, follow the standard Visual Studio practice of putting a project file and its source files into a folder based upon the project name.

For a single assembly this might work but when you are creating a project for several assemblies then you have to manually create a child folder to put the project into otherwise it'll simply merge the created project into the existing folder structure which makes it very hard to keep assembly files separated without manual work.

Example:

  • AssemblyA
    • File1 in namespace N1
    • File2 in namespace N1
  • AssemblyB
    • File3 in namespace N1
    • File4 in namespace N1

Create a project using src as root and repeat for both assemblies.

Result:

  • src
    • N1
      • File1
      • File2
      • File3
      • File4
    • AssemblyA.csproj
    • AssemblyA.sln
    • AssemblyB.csproj
    • AssemblyB.sln

Proposal: Place each assembly into a same-named folder as the assembly. It doesn't matter where the solution goes but often it is at the root.

CoolDadTx avatar Nov 30 '22 18:11 CoolDadTx