Base solution for your next web application
Open Closed

NuGet API Key not visible for Enterprise license – need private ABP 11.3.0 packages for v15.4.0 #12699

User avatar
0
CommunityCare created

We are upgrading to ASP.NET Zero v15.4.0 (ASP.NET Core & Angular, .NET 10).

The project references ABP 11.3.0 packages (Abp, Abp.AspNetCore, Abp.ZeroCore.EntityFrameworkCore, Abp.ZeroCore.OpenIddict, …), Abp.Mapperly 11.3.0 and Abp.AspNetZeroCore 6.x. These do not restore from nuget.org (latest ABP there is 10.5.1, and Abp.AspNetZeroCore 6.x requires ABP 11.2+). We understand ABP packages are now published as private NuGet packages that require the license's NuGet API key.

On our license page we only see the License, GitHub Members and Invoice tabs – there is no "NuGet API Key" link.

Could you please:

  1. Enable / show the NuGet API Key (package source) for our Enterprise license.
  2. Tell us the feed URL format and authentication (key in the URL, or username + key).
  3. Advise on Azure DevOps: can the feed be added as an upstream source of an Azure Artifacts feed? If not, is it OK to push the packages into our private Azure Artifacts feed, or should CI use the feed directly with a secret?
  4. Confirm whether one key can be shared by our developers and build agents.
  5. Confirm Abp.AutoMapper 11.3.0 is available in the same feed (we still have many AutoMapper mappings in our own modules).

Thank you!

Markdown is supported
Copy & paste or drag & drop images (max 30 MB per image)
Go to accepted answer
1 Answer(s)
  • User Avatar
    0
    oguzhanagir created
    Support Team

    Hi @CommunityCare

    Hello,

    We apologize for the inconvenience caused by the NuGet API Key not being visible in your license profile.

    We have now assigned a NuGet API Key to your license. You can view it here:

    https://aspnetzero.com/LicenseManagement

    Regarding your other questions:

    1. NuGet Feed URL and Authentication

    You can access our private NuGet feed using the following URL:

    https://nuget.aspnetzero.com/{YOUR-API-KEY}/v3/index.json

    Simply replace {YOUR-API-KEY} with the key displayed on your License Management page.

    You can add this URL directly to your NuGet.Config file as a package source. No additional username or password is required.

    2. Azure DevOps Integration

    Azure Artifacts does not support arbitrary private NuGet feeds as upstream sources.

    However, you can publish the required packages to your private Azure Artifacts feed and use them in your Azure DevOps pipelines.

    We recommend using our private NuGet feed directly, as this provides easier access to newly published package versions without requiring manual synchronization.

    3. Sharing the NuGet API Key

    The NuGet API Key is associated with your license and can be used by your development team and CI/CD build agents within your licensed organization, subject to your license terms.

    We recommend storing the key securely in Azure DevOps secret variables or Azure Key Vault rather than committing it to source control.

    4. Abp.AutoMapper 11.3.0

    ASP.NET Zero v15.4 uses Mapperly by default.

    If you still need AutoMapper for your existing modules, please first check whether Abp.AutoMapper 11.3.0 is available in your private NuGet feed.

    If the package is not available, you can build the corresponding version from the ABP source code and publish it to your internal NuGet feed.

    We have also published a detailed guide explaining this process:

    https://aspnetzero.com/blog/using-automapper-after-migrating-to-mapperly

    Please let us know if you encounter any issues while restoring the packages or configuring your development environment.

    Thank you.

    Markdown is supported
    Copy & paste or drag & drop images (max 30 MB per image)
    1
Assignee
No one
Labels
None yet