- In existing project ABP "nuget package replace by code" is not working and throwing various errors in ABP console
Can you write which module you are trying to add by source-code? Also ensure that your ABP CLI and ABP Suite versions must be the same with your project version. Suite and CLI must be v4.0.2 in your case.
- Cannot create new entity as mulitple namepsaces changed in C# which is breaking the whole project
This shouldn't be problem if you are using the same Suite version. See How can I install a specific version of ABP Suite?
- Cannot add new/change UI as proxy generation command is creating new proxy folder structure which is different than previous version. It is causing whole UI to break.
If you change the backend's project structure, the proxy folder structure also changes.
Folder paths are being created according to namespaces.
Updating the links to those proxies in the UI will fix it
You can try all proxy imports directly from the proxy folder
import {SomeDto} from '@proxy'
If you revise tsconfig you can achieve this.
Create a new project to see the new tsconfig.json file.
hi gary,
what's your UI (MVC/Blazor/Angular)? And ABP version?
you can disable it with AutoValidate = false https://docs.abp.io/en/abp/4.1/CSRF-Anti-Forgery#abpantiforgeryoptions
or
you need to add the anti-forgery token to the header with the header name RequestVerificationToken.
this is implemented in new ABP templates. you can create a new template to see how it works and adopt to your existing project.
in this article it shows how to customize the login page. similar to your requirement https://community.abp.io/articles/how-to-customize-the-login-page-of-an-abp-blazor-application-by4o9yms
1- I am not able to downlaod code as ABP suite is breaking again. Raised it as another ticket.
So what's the repro steps? If you have another step. let's not discuss it here!
2- abp generate-proxy is generating proxy classes in completely different folder st. then the provious build and it is breaking the whole project. Please confirm i can raise seperate ticket for that.
can you give details
do you know the reason why it doesn't work when you run in Visual Studio? IIS Express does not allow remote connections by default.
There are some ways of achieving this:
I use dotnet run command line, it works..
great work paul! I didn't expect this step :)
login screen has changed to support "code flow" in Identity Server 4 after ABP v4.0. if you don't want to use Identity Server, then you don't need that. but this question is for Blazor. maybe we can discuss it in a new question so that people here will not get unnecessary notifications.
btw refunded your question credit.
Hello,
"Program" is not a C # reserved keyword and yet when you want to use an entity with this name as an association on another entity the Program.cs file is not listed. However, the creation of the "Program" entity went very well.
Erratum: It's only related on the filename "Program.cs" If I rename it to "ProgramTest.cs" all is working well.
Nicolas.
@willignicolas
yes it's not a C# reserved keyword but Suite automatic class finder filters it because it's interferring with program.cs in host projects.
Also it may break namespaces as there's an existing Program class.
I created an internal ticket for that to be able to use Program keyword.
I myself had the same situation while creating Program in a School portal. It's being problem with dotnet Program classes (not related to ABP) so I used SchoolProgram. But if you insist on this name, there's a work around. Choose any other class (eg: AppUser) then save it without generating. After, go to aspnet-core\.suite\entities folder and find your entity.json. You'll see the file paths and other properties for the navigation property. Update them and go back to Suite. Refresh it and click save and generate.
