Hi There! Can you share the error you're getting? As far as I know any service you create in your application project that ends in AppService is automatically exposed so you can consume it from your web project.
Hello David. I will send you a sample project that DevExpress has been fully implemented.
I'd love this project too :)
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
The documentation at https://docs.abp.io/en/abp/latest/PlugIn-Modules does a decent job of explaining how to work with modules to separate new features on your main application, however all of the examples are for MVC. Is this possible for the angular UI as well? In mvc it seems you just add a new module and add your views, compile and include that somewhere so its loaded up by the main app, would there be a similar process supported for Angular? If not, does that mean that all of the features would have to be implemented for every deployment then since we cant split out module UIs?
Hi,
Thanks for the feedback I'll take a look into it. I see the example is to user razor pages even though my project is implementing apis on the net core and the frontend on angular. Does that mean that the real base of abpio is to use the mvc deployment since some modules seem to rely on it? for example docs module doesnt seem to be available for angular
Should I just switch my entire project over to netcore with mvc to have the largest coverage?
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
The documentation for the commercial payment module says the below. does this mean we can implement other payment systems, if so, wheres the documentation for what we need to do? I dont have the higher level license to download existing pro module code, so documentation on these things is crucial..
Configure<PaymentOptions>(options => { options.Gateways.Add( new PaymentGatewayConfiguration( "MyPaymentGatewayName", new FixedLocalizableString("MyPaymentGatewayName"), typeof(MyPaymentGateway) ) ); });
Same problem if you upgrade existing solution to 4.0.1, angular client stays at gray screen and this can be seen in console.
Cli 4.0 and suite 4.0 Generate a brand new project, build project, add an entity in suite. services are correctly generated on the backend, however UI is not generated on the frontend. reviweing suite log I can see the path to the schemas has .suite\schematics.suite\schematics in it (its duplicated!!) if you generate the path structure inside it as its looking for, it runs and generates the UI. surely this is just a bug with the duplicate path?
example
2020-12-03 10:42:03.931 -05:00 [INF] Running the Angular Schematics command: npx "projectpathhere/angular/.suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-pro CustomerPortal "projectpathhere/aspnet-core/.suite/entities/Customer.json" 2020-12-03 10:42:07.601 -05:00 [INF] Angular Schematics command failed. Collection "projectpathhere\angular**\.suite\schematics\.suite\schematics**\node_modules\@abp\ng.schematics\collection.json" cannot be resolved.
Hi Alper, I was replicating this in a new project for you but seems this new 3.3.2 fixed the issue
Initial-value problem seems to have dissapeared after i updated efcore tools from prev version 3.1.4 then it would still fail to generate the migration on the last step (angular project would get the info, classes also created in dotnetcore). It seems that if i manually add a migration (1 time) to the new project and apply it, i can then add entities from abp suite and it succeeds. Strange?
Fresh install of the abp cli and suite, generate solution from suite, open solution in vs2019 run db migrator project to create the db, add any entity with any props, the steps suceed from 1-8, step 9 the db migrator part fails as most of the related .cs documents end up placing %%initial-value%% next to the generated properties..