- ABP Framework version: v4.3
- UI type: MVC
- DB provider: MongoDB
- Tiered (MVC) or Identity Server Separated (Angular): yes
- Exception message and stack trace:
- Steps to reproduce the issue:
Hi
We have had some difficulty getting a new developer (who has a license) up and running with an already existing abp solution.
We tried to run the application, and could see in the log that there was a license validation problem. So, we then used the cli to login to abp "abp login..." and were logged in succesfully. When trying to run the application again, there were no issues is the log file, but everytime we tried to run the application it kept coming up with a 404 error.
We could see that the application worked succesfully when in Release mode, but not in debug mode. Trying to replace the ASPNETCORE_ENVIRONMENT=Development to Production did not fix the problem either (just different error page but stil 404 error).
After trying different things, we then decided to try the abp suite. After installing it for the first time and then adding the existing solution to abp, we then found that that after running the solution again (debug, ASPNETCORE_ENVIRONMENT=Development ), the application now started correctly.
Should simply logging in using the cli "abp login..." be enough to be start working with a solution? Is this the best way to get a new developer started? Or is there a better way?
Best regards,
Mike
3 Answer(s)
-
0
We have tried it for a different user on a new computer and we did not have to add the solution to the abp suite (but had to install it).
-
0
you don't need to add it to Suite.
abp loginis the only thing you need to do I see michael, sebastian and ludger can succesfully login and run the project. do you still get any error? then run these commandsdel %UserProfile%\.\AppData\Local\Temp\AbpLicense.bin del %UserProfile%\.abp\cli\access-token.binabp loginagain. -
0
This question has been automatically marked as stale because it has not had recent activity.
