hi,
we couldn't reproduce... can you try to generate it again then send us the Suite logs to info(@)abp.io the logs are located here
%UserProfile%\.abp\suite\logs
Actualla a module is not different than the application itself. The main difference is UI files and dependant client packages. The UI files (JS, CSS and others) must be embedded resources to be able to use it in the main application. Add the 3rd party library references to your module and use it. if you fall into any issue write back us.
@kzmyvr we'll check and get back to you.
@alexander.nikonov I created a new question for this seperate issue. https://support.abp.io/QA/Questions/876/Suite-module-page-is-not-loading
can you open the developer console and check if there's a log. 1- open Chrome Developer Console and refresh page 2- see if there's an error or awaiting XHR request 3- check the CMD window (which you have started the Suite). is there any error there?
@alexander,
the --version
parameter came to ABP CLI after v4.0.
so when you are using an older version than 4.0 you cannot use --version
parameter.
use the below command:
dotnet tool uninstall --global Volo.Abp.Suite
dotnet tool install -g Volo.Abp.Suite --version 3.3.2 --add-source https://nuget.abp.io/<your-api-key>/v3/index.json
@scott7106
Hi @alper,
After upgrading my CLI and Suite to 4.2 and everything worked correctly. For future reference, does Suite always generate based on the latest stable version regardless of which version I have installed? I do not see an option to tell Suite to use --preview or a specific version.
Suite has a --preview
option but not for generating code.
you can install the preview version of the Suite like below
abp suite install --preview
If you are using a preview ABP version, then you can install the Suite preview version.
@gexiaoxu are you working on a module? if so we have fixed this in the latest relese. check that you don't have a preview version.