Activities of "okains"

OK I found out what was going on here, everything actually works with replacing the Default.cshtml file. However the sample file provided had a hack around the custom styles section that made it so that the custom styles were not written:

@* TODO: We can continue with this until find a better way *@
@if (logoUrl != null || logoReverseUrl != null)
{

<style> :root { @logoUrl @logoReverseUrl }

.card {
    background: #55535f;
    color: #ffffff;
    border-radius: 250px;
    padding: 50px;
    min-width: 500px;
    text-align: center;
}

body {
    background-color: #9B9B9B;
    text-align: center;
    background-image: url('https://placeimg.com/640/480/tech/grayscale');
}

</style> }

So, remove the @* TODO :

and it works.

Thanks for getting back to me on this. Yeah I am guessing this is a config issue of some sort, and I was hoping that you / someone would be familiar with this and would know what is going on.

I may have tried to install a pre-release of LeptonX in this solution a while back, I wonder if that caused any config problems? Any thoughts on that possibility?

I will try and recreate on my end also and get back to you with more details.

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:

1. Using ABP Suite, create New Blazor Server Project
2. PUBLISH the project ( anywhere )
3. 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: