Directory structure for solution
-
I have a solution in C# which has 6 projects Say A, B, C, X, Y, Z Where A, B, C generates exe's and X, Y, Z is of type Class library (DLL) 1) Executables A and B both hold a reference to Projects X, Y, Z (dll). 2) Where Executable C holds a reference to Dll X only. X,Y,Z are private assemblies and not candidates for GAC. Now since they are private assemblies when I add a reference it'll be copied to the project output directory locally. And if I'll set the property "Copy Local = false" then it'll not get copied and the exe's fails when. What I wanna impose is a directory structure for my solution to avoid multiple copies of dll's when deploying. LetSay it'll copy all the files in... \AppRoot ......... A.exe ......... B.exe ......... C.exe \AppRoot\Lib .............. X.dll .............. Y.dll .............. Z.dll And have them work correctly. I'm new to Dotnet and perhaps to programming.. Please help how to impose this kind of directory structure for my app. Thanks. SMK
-
I have a solution in C# which has 6 projects Say A, B, C, X, Y, Z Where A, B, C generates exe's and X, Y, Z is of type Class library (DLL) 1) Executables A and B both hold a reference to Projects X, Y, Z (dll). 2) Where Executable C holds a reference to Dll X only. X,Y,Z are private assemblies and not candidates for GAC. Now since they are private assemblies when I add a reference it'll be copied to the project output directory locally. And if I'll set the property "Copy Local = false" then it'll not get copied and the exe's fails when. What I wanna impose is a directory structure for my solution to avoid multiple copies of dll's when deploying. LetSay it'll copy all the files in... \AppRoot ......... A.exe ......... B.exe ......... C.exe \AppRoot\Lib .............. X.dll .............. Y.dll .............. Z.dll And have them work correctly. I'm new to Dotnet and perhaps to programming.. Please help how to impose this kind of directory structure for my app. Thanks. SMK
Create a common folder for the output from the class library projects and change the project settings for these. Then have your exe project reference the assemblies from this location. AppRoot Common Lib x y z
only two letters away from being an asset
-
Create a common folder for the output from the class library projects and change the project settings for these. Then have your exe project reference the assemblies from this location. AppRoot Common Lib x y z
only two letters away from being an asset
The deployed structure need not echo the development structure. Add a deployment project.
-
The deployed structure need not echo the development structure. Add a deployment project.
True, however creating a common folder for this senerio will ease creating a deployment package
only two letters away from being an asset
-
Create a common folder for the output from the class library projects and change the project settings for these. Then have your exe project reference the assemblies from this location. AppRoot Common Lib x y z
only two letters away from being an asset
Create a common folder.... Where... do you mean solution folder or a folder in each project? Change the project settings for these... How... you mean using Project Properties>> Built>>> Output Path?? Do I have to use an absolute or relative path to Common?? Please need a little more clarification on this. SMK
-
Create a common folder.... Where... do you mean solution folder or a folder in each project? Change the project settings for these... How... you mean using Project Properties>> Built>>> Output Path?? Do I have to use an absolute or relative path to Common?? Please need a little more clarification on this. SMK
Common to the solution. The reference can be either relative or absolute, although I believe VS converts it to relative if it can.
only two letters away from being an asset