When working with DLLs from within the same solution or installed via NuGet, it's essential to have them updated in real-time. However, these DLLs are typically only automatically copied to the application's startup directory. You can use post-build event command lines to transfer and organize DLL files effectively.

Direct batch commands can be used to transfer DLL files, as demonstrated in the following examples for a VSDebug scenario:

>Method 1: Using specific paths and project names

::@echo off
:: Configure relevant paths
set OutputPath=C:\Development\VSDebug\bin\Debug\
set AppName=VSDebug

:: Create Lib and Dll directories if they don't exist
IF NOT EXIST "%OutputPath%Lib" MD "%OutputPath%Lib"
IF NOT EXIST "%OutputPath%Dll" MD "%OutputPath%Dll"

:: Define DLLs that should go to the Lib folder
setlocal enabledelayedexpansion 
:: Example with Newtonsoft.Json.dll
set SpecialLibs[1]=Newtonsoft.Json
set libCount=1

:: Move specified DLLs to the Lib folder
for /l %%i in (1,1,%libCount%) do (
echo  Moving !SpecialLibs[%%i]! related files
move  "%OutputPath!SpecialLibs[%%i]!.dll"  "%OutputPath%Lib"
move  "%OutputPath!SpecialLibs[%%i]!.xml"  "%OutputPath%Lib"
move  "%OutputPath!SpecialLibs[%%i]!.pdb"  "%OutputPath%Lib"
)

:: Move remaining DLLs to the Dll folder
move  "%OutputPath*.dll"  "%OutputPath%Dll"
move  "%OutputPath*.xml"  "%OutputPath%Dll"
move  "%OutputPath*.pdb"  "%OutputPath%Dll"

:: Extract main program files
move  "%OutputPath%Dll\%AppName%.xml" "%OutputPath%%AppName%.xml"  
move  "%OutputPath%Dll\%AppName%.pdb" "%OutputPath%%AppName%.pdb"

::pause

>Method 2: Using macro variables for automatic matching

::@echo off
:: Create Lib and Dll directories if they don't exist
IF NOT EXIST "$(OutDir)Lib" MD "$(OutDir)Lib"
IF NOT EXIST "$(OutDir)Dll" MD "$(OutDir)Dll"

:: Define DLLs that should go to the Lib folder
setlocal enabledelayedexpansion 
:: Example with Newtonsoft.Json.dll
set SpecialLibs[1]=Newtonsoft.Json
set libCount=1

:: Move specified DLLs to the Lib folder
for /l %%i in (1,1,%libCount%) do (
echo  Moving !SpecialLibs[%%i]! related files
move  "$(OutDir)!SpecialLibs[%%i]!.dll"  "$(OutDir)Lib"
move  "$(OutDir)!SpecialLibs[%%i]!.xml"  "$(OutDir)Lib"
move  "$(OutDir)!SpecialLibs[%%i]!.pdb"  "$(OutDir)Lib"
)

:: Move remaining DLLs to the Dll folder
move  "$(OutDir)*.dll"  "$(OutDir)Dll"
move  "$(OutDir)*.xml"  "$(OutDir)Dll"
move  "$(OutDir)*.pdb"  "$(OutDir)Dll"

:: Extract main program files
move  "$(OutDir)Dll\$(TargetName).xml" "$(OutDir)$(TargetName).xml"  
move  "$(OutDir)Dll\$(TargetName).pdb" "$(OutDir)$(TargetName).pdb"

::pause

The combination of @echo off and pause keeps the command window open after script execution. However, when these commands are added directly to post-build events, we don't need this combination, so it's commented out.

When dealing with numerous comamnds, adding them directly can be cumbersome and untidy. In such cases, you can edit the commands into a separate batch file and simply call it from the build events.

Macro Reference (available by clicking Edit Post Build → Macros):

$(ConfigurationName) - Name of the current project configuration (e.g., "Debug|Any CPU").

$(OutDir) - Path to the output file directory, relative to the project directory. This resolves to the value of the "Output Directory" property and includes a trailing backslash "\".

$(DevEnvDir) - Visual Studio installation directory (drive + path); includes a trailing backslash "\".

$(PlatformName) - Name of the current target platform (e.g., "AnyCPU").

$(ProjectDir) - Project directory (drive + path); includes a trailing backslash "\".

$(ProjectPath) - Absolute path name of the project (drive + path + base name + file extension).

$(ProjectName) - Base name of the project.

$(ProjectFileName) - File name of the project (base name + file extension).

$(ProjectExt) - File extension of the project. It includes "." before the file extension.

$(SolutionDir) - Solution directory (drive + path); includes a trailing backslash "\".

$(SolutionPath) - Absolute path name of the solution (drive + path + base name + file extension).

$(SolutionName) - Base name of the solution.

$(SolutionFileName) - File name of the solution (base name + file extension).

$(SolutionExt) - File extension of the solution. It includes "." before the file extension.

$(TargetDir) - Directory of the main output file (drive + path). It includes a trailing backslash "\".

$(TargetPath) - Absolute path name of the main output file (drive + path + base name + file extension).

$(TargetName) - Base name of the main output file.

$(TargetFileName) - File name of the main output file (base name + file extension).

$(TargetExt) - File extension of the main output file.