Suggestion: -i input directory flag #110

New Issue

claunia · 2026-01-29T16:29:47Z

claunia commented

2026-01-29 16:29:47 +00:00

Originally created by @pagner on GitHub (Nov 18, 2021).

It seems you have to build the project inline before the packaging runs.

It would be nice if we could specify the manually built publish folder and just run the packaging on it. Skip the build and get to the packaging

The reason I need this feature is because I obfuscate my dll's before release. This is a separate command altogether.

For example:

dotnet rpm -i path/to/my/publish/folder -o path/to/my/output/folder

Thanks

Originally created by @pagner on GitHub (Nov 18, 2021). It seems you have to build the project inline before the packaging runs. It would be nice if we could specify the manually built publish folder and just run the packaging on it. Skip the build and get to the packaging The reason I need this feature is because I obfuscate my dll's before release. This is a separate command altogether. For example: dotnet rpm -i path/to/my/publish/folder -o path/to/my/output/folder Thanks

claunia commented

2026-01-29 16:29:48 +00:00

@sduffy77 commented on GitHub (Dec 22, 2024):

I would like to see this feature added as well.

@sduffy77 commented on GitHub (Dec 22, 2024): I would like to see this feature added as well.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dotnet-packaging#110