Hello,
We had a consultant use our ASPNetZero to build our website, we call Merlin. They built it with version 13.2.0. We are now supporting this website and adding a new module. When I attempt to use the ASPNetZero Rad tool it assumes I am using v14.0.0. That version, as I am sure you know, is on .NET9 and our version is on .NET8. So I am trying to figure out how to get our current new module done in the least amount of time. I have spent the week trying, unsuccessfully, to upgrade from v13.2.0 to v14.0.0. My manager asked if there is a way to use the Radtool so it uses the v13.2.0 files?
28 Answer(s)
-
0
Hi @mittera
It was my pleasure to assist you. If you encounter any further issues or need additional assistance, please don't hesitate to reach out.
Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image) -
0
Hi @mittera
I have reviewed the project you provided. In the service-proxies, some class references are missing due to naming conventions. Therefore, the following changes need to be made:
- In the
UserNotificationHelperfile, EntityDtoOfGuid should be replaced with GuidEntityDto. - In
friends-lookup-table.component.ts:- The PagedResultDtoOfFindUsersOutputDto class should be renamed to FindUsersOutputDtoPagedResultDto.
- The PagedResultDtoOfNameValueDto class should be updated to NameValueDtoPagedResultDto.
Additionally, there are build errors caused by missing imports for some standalone components. To resolve these issues, I recommend reviewing the official documentation: 🔗 Angular Standalone Migrations
If the issue persists after making these changes, please do not hesitate to contact me.
That was very helpful. I updated UserNotificationHelper and friends-lookup-table. I still have to research what I need to do with the Angular Standalone Migration.
Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image) - In the
-
0
Hi @mittera
After updating the Angular CLI to the latest version, you need to follow the commands outlined step by step in the Angular migration guide. It is recommended to create a new branch before making these changes to ensure stability. Note that your Angular CLI project may not fully transition to standalone automatically. Under the "Manual" section, you will need to adjust the parts that were not migrated by following the provided instructions.
- Run
ng g @angular/core:standaloneand select "Convert all components, directives and pipes to standalone" - Run
ng g @angular/core:standaloneand select "Remove unnecessary NgModule classes" - Run
ng g @angular/core:standaloneand select "Bootstrap the project using standalone APIs" (If you have fully migrated to the latest version of ASP.NET Zero, this step will not be necessary.) - Run any linting and formatting checks, fix any failures, and commit the result
Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image) - Run
