- ABP Framework version: v5.3.0+
- UI type: Blazor
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace: N/A
- Steps to reproduce the issue:"
- Upgrade ABP Client & Suite from 5.2.2 to 5.3.0 or higher.
- Upgrade packages in an existing project from 5.2.2 to 5.3.0.
- Create a new entity in ABP Suite and click "Save and Generate."
- Receive the message "Your project seems to be working! Stop the project before generating code." even though the project is not running.
- Entity fails to generate.
As stated above, after upgrading Suite to 5.3.0 or higher, I can no longer use it in two already-existing 5.2.2 projects to generate new entities. Suite keeps telling me the project is running, even though it isn't. I've been able to create new entities on entirely new projects, as well as a project that has never been "published" through Visual Studio before (the two projects I receive this error for have). What is making Suite think that the project is running, and how do I correct it? I'm no longer able to use the latest version of ABP until I figure this out.
3 Answer(s)
-
0
Hi @AMacaulayAtETV,
To check if the project is running, Suite sends GET request to
launch url's in the solution. If the response is successfull, that means it is running.So please ensure that there are no any other project that runs on the same URL.
Also, it is a warning message. You can continue if you are sure that the project is not running.
Entity fails to generate
Can you explain a bit more?
-
0
Also, it is a warning message. You can continue if you are sure that the project is not running.
No, I can't. Clicking the "Okay" button on that popup doesn't let entity generation proceed. It just stops it there, and there's no other button to click.
To check if the project is running, Suite sends GET request to
launch url's in the solution. If the response is successfull, that means it is running.Well, that explains why it doesn't work on our published apps. Where would I go if I wanted to temporarily change that launch URL so that this response is no longer triggered?
-
0
No, I can't. Clicking the "Okay" button on that popup doesn't let entity generation proceed. It just stops it there, and there's no other button to click.
You are right. We've changed this already but i forgot that it is not released yet. In the next version it will be a warning only.
Well, that explains why it doesn't work on our published apps. Where would I go if I wanted to temporarily change that launch URL so that this response is no longer triggered?
You can temporarily change the
selfUrlvalues inappsetting.jsonfiles in your solution.
