Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Publishing symbols and full nuget packages



  • We've got a problem scenario when we’ve got packages that contain a “lib” folder & some other folder, like “Content” or “tools”.

    When we build this package with –Symbols to get the source, our two packages are not subsets of each other:
    Main package contains: lib, Content, tools.
    Symbol package contains: lib, src

    • This is just how nuget does things

    When I upload the normal package, everything works, but we don’t get source & symbols – obviously.
    When I upload the symbol package, we can debug – but the installation of the package misses any Content files or scripts that run on Install. These can be important.

    If we upload first one, then the other, then the packages just override each other.

    Is there anyway that we can get around this?

    Product: ProGet
    Version: 3.1.0



  • Unfortunately, NuGet does not distinguish between symbol and normal packages when uploading; all that's sent from the client is the package name, id, and bytes. Thus, there's no way to have ProGet automatically merge.

    In this case, you'll need to combine both packages in one, then upload it.

    Alternatively, you can create a symbols-only feed and upload to that.


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation