You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
By default CoApp creates three packages: Main, Redist and Symbols. Main depends on Redist.
Is it possible to specify whether to create dependency on Redist package or not? Because it is not always necessary to have dll files. It can be enough just to have possibility to build the project. As far as I see all Redist does is copying binaries to target directory. Actually if you have many projects (1 exe and many dlls) that depends on the same nuget package in your solution then you need to execute copying only once for exe file. This could have perfect sense in case if your dlls have target directory different than main exe file. Currently I got nuget binaries copied to every directory with my dll.
Setup is as follows:
N - some nuget package (distrib package contains n.dll)
In solution, say, I have:
Exe project uses N and outputs to C:\Exe
Dll project uses N and outputs to C:\Exe\PlugIn\
After build I got n.dll copied to both directories: C:\Exe\ and C:\Exe\PlugIn\
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
By default CoApp creates three packages: Main, Redist and Symbols. Main depends on Redist.
Is it possible to specify whether to create dependency on Redist package or not? Because it is not always necessary to have dll files. It can be enough just to have possibility to build the project. As far as I see all Redist does is copying binaries to target directory. Actually if you have many projects (1 exe and many dlls) that depends on the same nuget package in your solution then you need to execute copying only once for exe file. This could have perfect sense in case if your dlls have target directory different than main exe file. Currently I got nuget binaries copied to every directory with my dll.
Setup is as follows:
N - some nuget package (distrib package contains n.dll)
In solution, say, I have:
Exe project uses N and outputs to C:\Exe
Dll project uses N and outputs to C:\Exe\PlugIn\
After build I got n.dll copied to both directories: C:\Exe\ and C:\Exe\PlugIn\
The text was updated successfully, but these errors were encountered: