Eziriz's ".NET Reactor" Error #9553

icoretchi created 8 days ago

Template: microservice
Created ABP Studio Version: 0.9.26
Current ABP Studio Version: 1.0.2
Multi-Tenancy: Yes
UI Framework: angular
Theme: leptonx
Theme Style: system
Run Install Libs: Yes
Database Provider: ef
Database Management System: sqlserver
Mobile Framework: none
Public Website: No
Include Tests: Yes
Dynamic Localization: Yes
Kubernetes Configuration: Yes
Grafana Dashboard: Yes
Use Local References: No
Optional Modules:
- GDPR
- FileManagement
- TextTemplateManagement
- AuditLogging
- Chat
- OpenIddictAdmin

Hi,

I've added the new microservice to the solution with the latest version 1.0.2. of abp.studio and I am receiving the following error:

This kind of error has happened before, but recently, such errors have not appeared. To the suggestions from similar problem tickets I've clean the nuget packages with dotnet nuget locals all --clear, but doesn't help. Any other suggestion?

Thanks.

Go to accepted answer

AI-Bot created 8 days ago

Support Team ABP Agent

The error message:

System.Exception: This assembly is protected by an unregistered version of Eziriz's ".NET Reactor"! This assembly won't further work.

indicates that one of the assemblies in your solution was built or obfuscated using an unregistered (trial) version of Eziriz's ".NET Reactor" tool. This is not related to ABP Framework or ABP Studio itself, but rather to a third-party or custom assembly in your solution.

How to resolve:

Identify the problematic assembly:
- Check which project or NuGet package is causing the error. The error stack trace should point to the specific assembly (e.g., Abc.ProjectionService).
- If you recently added a new microservice or referenced a third-party DLL, that is likely the source.
Replace or rebuild the assembly:
- If it is your own code, rebuild the assembly without using an unregistered version of ".NET Reactor".
- If it is a third-party library, contact the vendor for a properly licensed version, or replace it with an alternative.
Clean and restore packages:
- Run the following commands to ensure all packages are up to date and not corrupted:
```
dotnet clean
dotnet nuget locals all --clear
dotnet restore
```
Check your NuGet sources:
- Ensure you are not pulling any unofficial or tampered packages from custom NuGet feeds.
Remove any trial/protected DLLs:
- Search your solution for any DLLs that may have been obfuscated or protected with ".NET Reactor" and replace them with clean, licensed versions.

This is not an ABP-specific issue, but a general .NET assembly protection/licensing problem.

Sources (validated):

This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

maliming created 8 days ago

Support Team Fullstack Developer

Can you zip and share the bin folder of the error project?

liming.ma@volosoft.com

Thanks.

icoretchi created 8 days ago

Send it.

icoretchi created 8 days ago

Hi,

I have found the error. The Abp Studio generated the service with <PackageReference Include="Volo.Abp.Studio.Client.AspNetCore" Version="0.9.24" /> When I updated to the version 1.0.2 everything started to work.

maliming created 8 days ago

Support Team Fullstack Developer

Yes, you are right.

Upgrade Volo.Abp.Studio.* to >=0.9.25 if your project uses it(Packages name start with Volo.Abp.Studio).

https://abp.io/support/questions/8990/unregistered-version-of-Eziriz%27s-NET-Reactor#answer-3a18ca49-409a-d43e-0df5-8df4b150c93d

icoretchi created 8 days ago

I have to mention, that even if you have latest versions of the abp studio and cli, which is 1.0.2 and 9.2.1, the studio will generate the microservices not with the latest packages. I think you'll need to update the generators.

Cheers

maliming created 8 days ago

Support Team Fullstack Developer

Thanks. I will check the template.

maliming created 8 days ago

Support Team Fullstack Developer

Created ABP Studio Version: 0.9.26

And can you try to use the latest(1.0.2) Studio?

icoretchi created 8 days ago

I am using it. You can see solution configuration. Initially I created the solution with version 0.9.26. That was some time ago. But I've added the new microservice just right now with already updated studio.