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?
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) ) ); });
