This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
forked from wwahammy/signing
-
Notifications
You must be signed in to change notification settings - Fork 43
Make Main package independent from Redist #115
Comments
Last technical build does not use redist and symbols packages. It uses overlay mechanism. Any platform and build specific files are placed in separate hidden packages that will be installed in project at build step.
Please read #116 |
I download the latest version of CoApp,but it still can't generate one single package. |
Hi,
CoApp has been dead for a while, and it's not coming back.
The best alternative now is to use vcpkg with the just-released Binary
Caching:
https://vcpkg.readthedocs.io/en/latest/specifications/binarycaching/
Best regards,
Renato C.
Le ven. 18 déc. 2020 à 12:32, 9426224 <[email protected]> a écrit :
… I download the latest version of CoApp,but it still can't generate one
single package.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNWTYD4EQ35NUIY2JVEV2TSVNYZZANCNFSM4BRGDGEQ>
.
|
Thanks very much!! I’ll try this new feature!
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Renato Cherullo<mailto:[email protected]>
Sent: Friday, December 18, 2020 23:57
To: coapp/coapp.powershell<mailto:[email protected]>
Cc: 9426224<mailto:[email protected]>; Comment<mailto:[email protected]>
Subject: Re: [coapp/coapp.powershell] Make Main package independent from Redist (#115)
Hi,
CoApp has been dead for a while, and it's not coming back.
The best alternative now is to use vcpkg with the just-released Binary
Caching:
https://vcpkg.readthedocs.io/en/latest/specifications/binarycaching/
Best regards,
Renato C.
Le ven. 18 déc. 2020 à 12:32, 9426224 <[email protected]> a écrit :
I download the latest version of CoApp,but it still can't generate one
single package.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNWTYD4EQ35NUIY2JVEV2TSVNYZZANCNFSM4BRGDGEQ>
.
―
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#115 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADFPIUWV3PAQ3YFSLMVO2ATSVN3VNANCNFSM4BRGDGEQ>.
|
Sign up for free
to 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: