Develop Reference

BLL and DLL are not founded, when I move them somewhere except source repos(Visual Studio 2019)

I have 3-layer MVVM project, my solution folder, DLL folder and BLL folder are inside 'source > repos >' and project loads normally
But if I move BLL or DLL(or both) to some other folder, or Desktop for example, my project doesn't load correctly and file moved to Desktop defined as not founded in solution explorer
How could I fix it? I need put all this three project folders(DLL, BLL, View) to one folder, because I need to share it as one big project, but I can't, because any movement with files or folder finishes with error 'Files not founded'
Sadly can not send images here, in y question(
Thanks in advance for your answers!

Check for that in your project: is it in the references list? If it is, check that it's built for the same CPU type as your project, and that the Reference properties option "Copy Local" is set to true.
If it isn't, try adding it. If that works, try rebuilding. If it doesn't, then it's probably a Native Library, and you need to ensure that the DLL is either in the EXE folder, or in a folder on the current PATH that Windows uses to locate executables.

You Need to compile the DLL project into a dll file and then refer to the compiled dll file.
Or just use project references to add your DLL project and BLL project.

Automatically copying dll.config to a referenced projects output directory

I used the method suggested in the following post to include an App.config file to Class Library project.
Equivalent to 'app.config' for a library (DLL)
It works as mentioned and creates the .dll.config file in respective Class Library projects output directory (e.g. ApiCommunicator\bin\Debug).
I have referenced this Class Library project as a "Project Reference" from another Console Application project within the same Visual Studio solution.
Now the problem is, the .dll is getting copied to the Console Projects output directory (i.e. Engine\bin\Debug) but the .dll.config doesn't. If I manually copy it, everything works fine but is there a way to configure Visual Studio to auto copy .dll.config to any other project's output directory which references the Class Library project?
Thanks,
Bathiya

Although I am late, but my answer can help others. I used the following command as pre-build event:
copy /Y $(SolutionDir)\[YOUR_LIBRARY_PROJECT]\app.config $(ProjectDir)$(OutputPath)[YOUR_LIBRARY_NAME].dll.config
I tried to be dynamic as much as possible, and the above command worked.
I posted the same answer at the question Can we autocopy the *.dll.config? as well.

It would have to be the other way around: Projects referencing your dll could copy it's dll.config from a known location as a post-build event.
However I think it would be much better to provide the configuration from within the consumer application's configuration. That way each referencing project would have an option to adjust the configuration to its needs, which I would think is a critical feature.
If that is not the case, then I don't see the reason for having the .dll.config, and you can just hardcode the values.

You can use the 'Build Events' tab of your project properties to run command line instructions post-build or even pre-build. This way, you can use a simple
copy /Y "<yourconfigfilepath>" "<yourprojectfilepath>\Engine\bin\Debug\"
This will copy the dll.config file you are needing over to the correct directory.

Change local path of referenced project

I'm building a set of plugin assemblies that I want to load in my main application. For that reason I have to search through a plugin directory named "plugins". I currently have my plugins attached to my main applications' solution with all projects in my solution and all projects are added as ProjectReference in the project file of the main application with CopyLocal set to true.
The problem is the I want to have the project reference outputs not copied to the OutputPath of the main application, but in a subfolder. I couldn't find any option to set something like this.

If I understand correctly this is what you want.
In the plugins project right click -> properties -> build -> output path
You can change the output path to anywhere you need and have the parent project reference the assemblies in that folder.

Loosely-coupled, non-referenced assembly - how to make sure it's in the \bin\Debug folder of the exe project for debugging?

I'm building a loosely-coupled app, where the main exe project only contains references to an assembly with interfaces. The concrete implementations of those interfaces are in assemblies that are referenced indirectly - via IoC. However, those assemblies' build output doesn't get copied to the bin\Debug folder of the exe, which means my IoC can't find them.
How do I make sure those assemblies are copied, if there is no actual project/assembly reference?

You can create a post-build event to copy the desired files to the output directory after the project is built.

did you try to right click your exe project -> Project Dependencies.
Then tick all the projects that you need to be copied over your bin\Debug folder ?
Alternatively what Konamiman said would work as well.

You can make sure they are built before the main exe project by checking the relevant projects in Build Dependencies dialog (found in the Project context menu).
However I think you need to use xcopy in a post-build step to actually copy the assemblies.

Can Visual Studio compile project references into a different folder then the main .exe

I have a WPF Application project with several project references within a single solution in VS 2008. When I compile my solution, all of the referenced dlls are output into the same folder that the main .exe is output into.
Is it possible to configure my main .exe project build to output all references in a sub folder relative to my .exe?
I would like the final result to be something like this:
MyApp.exe
MyApp.exe.config
Lib\SomeReference.dll
Lib\SomeReference2.dll
(I assume if this is possible, it would be possible with any .exe).
Thanks!
Jon

It looks like its a fairly intensive process.
First set the reference's Copy Local property to false so that the .dlls aren't copied to the bin\Debug folder .
Then create an assemblyBinding\probing element in your app.config to instruct the runtime to look for dlls in the Lib folder
Then create a post-build action to copy the necessary dlls to the \bin\Debug\Lib folder.