Activities of "okains"
An update on this:
I was able to work around this by using a less complex password. I had initially used long random passwords that contained many special characters. These would work when connecting remotely to an Azure SQL DB using SSMS, but would not work using DBMigrator against an Azure SQL DB.
I reduced the length and complexity of the passwords that I use, kept them to UpperCase/LowerCase/Numbers/[*!"] and DBMigrator now runs.
Hope that helps someone else get past this.
ABP Framework version: v4.4.2 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no
Exception message and stack trace: The project name is invalid! Please specify a different name. Volo.Abp.Cli.CliUsageException: The project name is invalid! Please specify a different name.
Steps to reproduce the issue:
It seems like it is impossible to create a new project/SLN in ABP Suite that contains/ends with "Blazor", like "TestProjectBlazor". Generating the project online with the same name and then open it in ABP Suite seem to work though. No problem creating something like "TestProjectAngular".
- at Volo.Abp.Cli.Commands.NewCommand.ExecuteAsync(CommandLineArgs commandLineArgs) in D:\ci\Jenkins\workspace\abp-commercial-release\abp\framework\src\Volo.Abp.Cli.Core\Volo\Abp\Cli\Commands\NewCommand.cs:line 66 at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SolutionService.CreateSolutionAsync(CreateSolutionModel input) at lambda_method2438(Closure , Object ) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.
I ran into this also and created a ticket : https://support.abp.io/QA/Questions/1706/Error-Project-Name-is-Invalid-when-creating-a-Blazor-Server-project-using-Suite
there is an open issue for this, but for now you can not use 'Blazor' in the project name.
https://github.com/abpframework/abp/issues/9853
Any idea when this fix will be available?
ABP SUITE GENERATE ENTITY BUG
ABP Suite, Blazor Server Project, error on SaveAndGenerate entity AFTER having published once. Seems to be looking for a {ProjectName}WEBAutoMapperProfile.cs file that does not exist , see file attached. This file isn't even called {ProjectName}WebAutoMapperProfile.cs in a Blazor project, it is {ProjectName}AutoMapperProfile.cs . In either case, the file does not exist in the location and this fails every time.
Steps To Reproduce:
- Using ABP Suite, create New Blazor Server Project
- PUBLISH the project ( anywhere )
- Create a new entity, SaveAndGenerate
Also I am still waiting on a patch for the other ABP Suite Blazor Server Code Gen bug I reported 1 week ago:
Blazor Server & ABP Suite Code Gen Issue #1721
#1721 is still unfixed, though there is a workaround. For this issue there is no workaround that I can see, I tried renaming the AutoMapperProfile.cs file and adding it to the location but that didn't work.
These are 2 SERIOUS BLOCKERS for me and any other Commercial customer using Blazor Server. I can not continue working on my current project as I have ~50 entities to generate. Can we please get a patch ASAP?
Thanks,
Karim
Hi,
Yes, I figured that out after experimenting a few times and just settled on using BZ instead. However 'Blazor' is and should be allowed in project names. If you look at a lot of the online tutorials / documentation they use Blazor in the project name extensively. Is there a reason why you decided to make it invalid in this case?
It seems that you added this validation in 4.4 :
https://github.com/abpframework/abp/issues/8959
and I am guessing you are validating out the keyword 'Blazor' for project names? When I changed from Blazor, to 'BZ' then the project was created.
I can create a project using VS with the keyword 'Blazor' in the project name. This took longer than it should have to work through, can you confirm that this is a bug in your code or if I have missed something?
Thanks,
Karim
OK, as mentioned in my question, and in my response:
As mentioned in my question, the credentials are correct. I can connect to the azure DB using SQL Enterprise Manager, remotely from my pc, with no issues.
This is the same user account that I am using to connect to the azure db using SQL Enterprise Manager, locally. So I know the credentials are correct, the firewall port is open and Azure has whitelisted my IP address.
So the user has permissions. Is there anything else that I am missing here that would prevent me from running the migrator locally to see this remote azure db?
Would this best handled in a DevOps pipeline? I was thinking that I could just quickly run the DBMigrator project with the remote connection string and be done with it.
Hi,
Double check what? My username / password?
As mentioned in my question, the credentials are correct. I can connect to the azure DB using SQL Enterprise Manager, remotely from my pc, with no issues.
This is the same user account that I am using to connect to the azure db using SQL Enterprise Manager, locally. So I know the credentials are correct, the firewall port is open and Azure has whitelisted my IP address.
Is there more config that I need for this? Maybe the connection string isn't set correctly? I have set the connection string in appsettings.json as follows:
"ConnectionStrings": { // "Default": "Server=localhost;Database=AbpDevOps;Trusted_Connection=True", "Default": "Server=tcp:clevermm.database.windows.net,1433;Initial Catalog=AbpDevOps;Persist Security Info=False;User ID=XXXXXXXX;Password=XXXXXXXX;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;"
Here is a screenshot of the exception:
OK, after spending some time reviewing your answer and digging into the namespaces around Payment I am starting to better understand how this module works. I can now inject the service, and I can see how the Gateway Page works and I can see the rest of the payment infrastructure.
I think fundamentally though that the documentation is not great, and it has taken more time than it should for me to get up to speed with how this works. I suggest that you provide in depth documentation for the Payment module, and probably for all modules, so that us, as your customers, can spend less time figuring out your infrastructure and more time on our projects.
I have 2 more questions around this then we can close out. First of all, the 2Checkout documentation lists a certain set of params in the json configuration. I have supplied all of these, yet I still get an error:
' ArgumentException: Two checkout extra parameters are not configured for this product !' error.
Here is my JSON config for payment, the 'XXXXXXXX--MYSIGHERE--XXXXXXXX' param is replace with a valid 2Checkout signature.
*
"Payment": {
"Payu": {
"Merchant": "TEST",
"Signature": "SECRETKEY",
"LanguageCode": "en",
"CurrencyCode": "USD",
"VatRate": "0",
"PriceType": "GROSS",
"Shipping": "0",
"Installment": "1",
"TestOrder": "1",
"Debug": "1"
},
"TwoCheckout": {
"Signature": "XXXXXXXX--MYSIGHERE--XXXXXXXX",
"CheckoutUrl": "https://secure.2checkout.com/order/checkout.php",
"LanguageCode": "en",
"CurrencyCode": "USD",
"TestOrder": "1"
},
"PayPal": {
"ClientId": "CLIENTID",
"Secret": "SECRET",
"CurrencyCode": "USD",
"Environment": "Sandbox",
"Locale": "enUS"
},
"Stripe": {
"PublishableKey": "PUBLISHABLEKEY",
"SecretKey": "SECRET_KEY",
"PaymentMethodTypes": [ "alipay" ]
}
}*
Second, I will be using a 3rd party gateway and I would like to know how to set this up correctly. There is no documentation that describes how to do this. In your documentation you state the following:
PaymentOptions is used to store list of payment gateways. You don't have to configure this manually for existing payment gateways. You can, however, add a new gateway like below:
Configure<PaymentOptions>(options => { options.Gateways.Add( new PaymentGatewayConfiguration( "MyPaymentGatewayName", new FixedLocalizableString("MyPaymentGatewayName"), typeof(MyPaymentGateway) ) ); });
What is MyPaymentGateway? Can you provide an example of this, along with any supporting classes or DTOs that I would need to configure a new payment gateway? I am sure that I am not the only person having trouble with this, I suggest updating your documentation to cover these common use cases and provide us, the end user, with functional examples of how to get things done.
Thanks for your help,
Karim
I don't understand. In the documentation it clearly states that there is a PaymentRequest object, also a PaymentRequestAppService, and a PaymentRequestRepository. None of these are created when I install the module. As you can see from the screenshot below the only thing related to 'PaymentRequest' are the migrations, which work fine. Other than that there is nothing, no Payment Gateway Selection UI, no admin menu options, nothing.
So what I am saying is that these required files are not being created on add-module. I understand about configuring the payment gateways in appsettings.json, that is fine. But what about all of the supporting files and UI?
Can you let me know if this is a bug, or if there are other steps that I need to take?
<br>
<br>
<br>
