Hi Team,
We have recently migrated our Angular project from Angular 10 to Angular 18, and we are considering adopting Standalone Components, Directives, and Pipes to simplify our project structure and improve performance.
However, we noticed that the Entity Creator does not seem to follow this approach. Before proceeding, we would like to understand:
1.Does ASP.NET Zero officially support Standalone Components in Angular 18?
2.Are there any compatibility concerns or known limitations with introducing angular best practice features in an ASP.NET Zero environment?
3. Are there any known issues or compatibility concerns with using Standalone Components in ASP.NET Zero projects?
4. If standalone was a necessary improvement, why hasn’t ASP.NET Zero adopted it in its templates yet?
5. Does ASP.NET Zero have any recommendations or guidelines on adopting Angular 18 best practices, especially features?
Additionally, I have a question regarding the versioning of our application. We have successfully migrated the backend server code to a newer version, and it shows as API: v13.3.0. However, the client version is still showing as Client: v9.2.0 [20250210], which seems to be the older version. Could you help us understand?
Your guidance will help us decide whether to implement this in our application. Looking forward to your response.
Many Thanks.
1 Answer(s)
-
0
Hi @Jorahealth
We have passed the Angular standalone components structure with this issue. It will have a standalone components structure with the newly released v14.1 version. You can review the changes here. Apart from that, there are documents about migration processes in Angular official documentation. We are considering improvements to the Angular section regarding other migration operations.
You can change the version update by updating the
WebAppGuiVersionvalue inAppConstsunder the shared folder in the Angular project.
