Base solution for your next web application
Open Closed

ASP.NET Zero v15.4 React - Power Tools Generate hangs in Visual Studio and CLI fails with SSL connection error #12684

User avatar
0
alexbai created

ASP.NET Zero v15.4 React - Power Tools Generate hangs in Visual Studio and CLI fails with SSL connection error

Hello ASP.NET Zero Team,

We are currently developing a new project based on ASP.NET Zero v15.4.0 React, and we are having problems using Power Tools.

Environment

  • ASP.NET Zero: v15.4.0
  • ASP.NET Boilerplate / ABP: 11.3
  • UI: React
  • ASP.NET Core / .NET: .NET 10
  • EF Core
  • SQL Server
  • Windows 11
  • Visual Studio 2022
  • pnpm 11.15.1

The base project itself is working correctly:

  • NuGet restore succeeds for the ASP.NET Zero / ABP packages
  • Solution builds successfully
  • EF Core migrations have already been applied successfully
  • Web.Host runs correctly
  • React frontend runs correctly
  • Login and Host Admin work correctly

So the ASP.NET Zero v15.4 React project itself is currently in a healthy and runnable state.

Problem 1 - Visual Studio Power Tools hangs during Generate

We created a very simple test entity using the ASP.NET Zero Power Tools Visual Studio extension.

Entity:

ExamBatch

Configuration included:

  • Namespace: ExamManagement
  • Base Class: FullAuditedEntity
  • Primary Key: long
  • Project Type: React
  • Create User Interface: enabled
  • Entity History: enabled
  • Host: enabled
  • Tenant: disabled
  • Unit Test: enabled
  • Auto Migration: disabled
  • Update Database: disabled

The Entity JSON was successfully created:

AspNetZeroRadTool/ExamManagement.ExamBatch.json

However, when clicking Generate, Visual Studio became permanently unresponsive.

After terminating Visual Studio, Git showed several hundred changes inside:

aspnet-core/AspNetZeroRadTool/

Most of them were Power Tools templates / DLL / runtime files.

No actual business code was generated.

We restored the Power Tools runtime/template directory and kept the Entity JSON.

Problem 2 - Running AspNetZeroRadTool.dll directly fails with SSL error

We then tried bypassing the Visual Studio extension and directly running the local Power Tools CLI.

From:

aspnet-core/AspNetZeroRadTool

we executed:

dotnet AspNetZeroRadTool.dll ExamManagement.ExamBatch.json

The process exited immediately with exit code 1 and returned:

The SSL connection could not be established, see inner exception.

No Entity, DTO, AppService, React page, migration, or other business code was generated.

The Git working tree remained clean after the failed CLI execution.

The local AspNetZeroRadTool.dll targets .NET 8, and the machine has a compatible .NET 8 runtime installed.

Problem 3 - New Global Power Tools cannot be installed

Since v15.4 introduces the new Power Tools Global .NET Tool, we also tried:

dotnet tool install --global AspNetZero.PowerTools

The installation fails while accessing our ASP.NET Zero NuGet source:

Unable to load the service index for source https://nuget.aspnetzero.com/[REDACTED]/v3/index.json

We also tried adding nuget.org and ignoring failed sources, but AspNetZero.PowerTools could not be found there.

We have intentionally redacted our private ASP.NET Zero NuGet feed key / API key.

Additional information

Our repository Power Tools configuration reports:

  • ProjectType: React
  • ProjectVersion: v15.4.0
  • React templates exist under the Power Tools FileTemplates/React directory
  • AutoMigration: false
  • UpdateDatabase: false

The generated Entity JSON looks valid and contains all expected entity properties.

The ASP.NET Zero private NuGet source is also registered in our NuGet configuration.

The normal ASP.NET Zero project packages were previously restored successfully from the private feed.

Questions

Could you please help us confirm the following?

  1. What is the recommended Power Tools workflow for an ASP.NET Zero v15.4 React project?

    • Visual Studio extension
    • local AspNetZeroRadTool.dll
    • new AspNetZero.PowerTools Global Tool

  2. From which NuGet feed should AspNetZero.PowerTools be installed?

  3. Does access to the new Global Power Tools require any additional license/API-key activation beyond normal ASP.NET Zero NuGet package access?

  4. Why does the local command

    dotnet AspNetZeroRadTool.dll ExamManagement.ExamBatch.json

    require an HTTPS connection before generating the entity?

  5. Is the SSL failure related to Power Tools license validation or another ASP.NET Zero service endpoint?

  6. Are there any known Power Tools SSL/TLS issues with:

    • ASP.NET Zero v15.4
    • Windows 11
    • .NET 10 SDK
    • local Power Tools runtime targeting .NET 8?

  7. Is the Visual Studio Power Tools Generate hang a known issue in v15.4 React projects?

  8. Is there a newer Power Tools package / DLL / extension version we should use with ASP.NET Zero v15.4?

If useful, we can also provide the Power Tools Entity JSON and sanitized logs without exposing our LicenseCode or private NuGet credentials.

Thank you.

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

    Hi @alexbai

    Thank you for the detailed report. Starting with ASP.NET Zero v15.4, the recommended way to use Power Tools is the new .NET Global Tool not the Visual Studio extension or the legacy AspNetZeroRadTool.dll that ships inside the project.

    Here is how to get started:

    1. Prerequisites .NET 10 SDK must be installed on your machine. Verify with:

    dotnet --list-sdks

    You should see a 10.x entry. If a global.json in your project pins an older SDK, run the install command from a directory without one, or update global.json.

    2. Install the Global Tool

    dotnet tool install -g AspNetZero.PowerTools --source https://nuget.aspnetzero.com/{YOUR_API_KEY}/v3/index.json

    Important: Replace {YOUR_API_KEY} with your private ASP.NET Zero NuGet API key the same key you use to restore ASP.NET Zero NuGet packages. The --source parameter is required because this package is hosted on the ASP.NET Zero private feed, not on nuget.org.

    If you already attempted an install and get an "already installed" error, uninstall first:

    dotnet tool uninstall -g AspNetZero.PowerTools

    If you see DotnetToolSettings.xml was not found in the package, your active .NET SDK is older than 10.0. Install .NET 10 SDK and retry.

    3. Run Power Tools Navigate to your ASP.NET Zero project's aspnet-core directory and simply run:

    aspnetzero-powertools

    This will auto-detect your project configuration and open an interactive web UI in your browser where you can create/edit entities and generate code.

    Alternatively, for headless/CLI generation from an existing entity JSON:

    aspnetzero-powertools ExamManagement.ExamBatch.json

    Q: What is the recommended Power Tools workflow for v15.4 React? The .NET Global Tool (aspnetzero-powertools). The VS extension and the legacy AspNetZeroRadTool.dll are no longer the recommended approach.

    Q: From which NuGet feed should the tool be installed? From your ASP.NET Zero private feed: https://nuget.aspnetzero.com/{YOUR_API_KEY}/v3/index.json. It is not available on nuget.org.

    Q: Does it require additional license activation? No. It uses the same license code in your project's config.json. No additional activation is needed your existing ASP.NET Zero license covers Power Tools usage (as long as the license is active).

    Q: Why does the old DLL require an HTTPS connection? Power Tools validates your ASP.NET Zero license by contacting https://www.aspnetzero.com. The SSL error you encountered is likely a TLS compatibility issue between the old .NET 8-targeted DLL and your environment. The new Global Tool (targeting .NET 10) resolves this.

    Q: Is the VS Extension hang a known issue? The VS extension was designed for older versions and is not fully compatible with v15.4 React projects. Please use the new Global Tool instead.

    You can safely remove or ignore the aspnet-core/AspNetZeroRadTool/ directory content that was modified during the failed VS extension attempt it is part of the legacy tooling.

    If you run into any issues with the Global Tool installation or generation, please share the output and we'll be happy to help.

    Best regards

    Markdown is supported
    Copy & paste or drag & drop images (max 30 MB per image)
  • User Avatar
    0
    alexbai created

    Hi,

    Thank you for the clarification and detailed instructions.

    I followed the recommended ASP.NET Zero v15.4 workflow and tested the new AspNetZero.PowerTools .NET Global Tool.

    The tool is already installed successfully (AspNetZero.PowerTools 2.0.0), and running aspnetzero-powertools from the aspnet-core directory works correctly. The Web UI opens successfully and correctly detects our project as:

    Project: flintstone.OTS Project Type: React ASP.NET Zero Version: v15.4.0

    It also successfully detects our existing ExamManagement.ExamBatch entity definition.

    This confirms that the previous issue was related to using the legacy Visual Studio extension / AspNetZeroRadTool.dll workflow. We will use the new .NET Global Tool going forward.

    Thank you again for your help.

    Best regards, Alex

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