You appear to be using VS Code. I am using Visual Studio. I am trying to start the app with debugging in Visual Studio.
Further to this. I have tried running DBMigrator project and have found the following:
If I run from Visual Studio, using 'Debug | Start New Instance' I get the following error:
However, if I open a terminal window and simply do dotnet run --no-build
(i.e. using exactly the same binaries that just failed), it works no problem.
How do I run unit tests and DBMigrator both of which seem to be having the similar problems with license?
Microsoft have now made central package management a possibility for larger projects (https://devblogs.microsoft.com/nuget/introducing-central-package-management/)
Can we use this with abp solutions? If so, what are the downsides of doing so? If not, when will we be able to do so?
Thanks, Phil
FYI. I reverted the above changes and tried again.
After doing the switch to nightly builds using abp-suite there are a number of package references I had to manually correct but the result is the same:
[14:09:13 ERR] ABP-LIC-0003 - No modules found! There's no module found for your organization. Contact to license@abp.io for more information. [14:09:14 ERR] ABP-LIC-0013 - License exception: ABP-LIC-0023: An error occured while calling the license server! License check communication failed! The response was not successful: 400 - Bad Request [14:09:14 ERR] ABP-LIC-0001 - Couldn't check license within the allowed time period, please enable your internet connection. [14:09:14 ERR] ABP-LIC-ERROR - License check failed for 'Volo.Abp.Identity.Pro.Domain-v8.0.0.0'.
I used abp-suite to switch my solution to nightly builds.
I then updated all the EF Core references in my projects to: 8.0.0-rc.2.23480.1
I then built the application but get the error shown when I try to run.
As suggested in https://support.abp.io/QA/Questions/5912/How-do-I-start-using-the-new-features-in-EF-Core-8 I modified my solution to use the nightly ABP builds and I now cannot start the application due to the licensing error above.
Thanks. Will this be available in the nightly builds once your pull request in merged?