Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request : Add options to publish created nuget file to specified Nuget Server #2

Open
PJTewkesbury opened this issue Jun 7, 2017 · 3 comments

Comments

@PJTewkesbury
Copy link

Hi,

I have just found this gem of a nuget package. Thanks for sharing.

It would be even more useful if, after the nupkg file has been created if it could be published to a specified nuget server so to completely automate the process.

Many thanks.

Peter Tewkesbury

@Puresharper
Copy link
Owner

Puresharper commented Jun 7, 2017

Hi, I understand your needs and I already worked on. Unfortunately, I have to resolve some kind of configuration not allowed by nuget to do it. I don't want to impose this feature directly in NuPack. However, that's one of the reasons why I am working actively on NuPack extension to provide additional package to improve NuPack behavior. It will be released very soon.

First sample NuPack extension will be licence management, .nuspec merge, local copy and publish to online repository.

@Puresharper
Copy link
Owner

I just released NuPack 3.4.2 + NuPack Extension 2.1.0
Extends NuPack is now available.

How to?

  • Just create a library project with Visual Studio
  • Install NuPack.Extension 2.1.0+
  • Create a class with a parameterless constructor
  • Implements this interface : IPuglin
  • Install NuPack 3.4.2+ to create your extension package

It allows to adjust PackageBuilder before saving it.
Dispose is called at the end of process that allow you to trigger a publish process to a nuget server.

note : I don't have time to do it today, but I work on.

@PJTewkesbury
Copy link
Author

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants