Activities of "sid@extranerds.com"

We have a VS solution created in ABP Suite which was running perfectly. Suddenly, with no changes to the code, the application will no longer run in Visual Studio. With the Blazor application set as the startup project, if I hit F5 to run the app for local debugging, the Chrome browser window opens for a few seconds, attempts to load https://localhost:44326/ and then disappears. The application has stopped running and I'm back in VS 2022 with no explanation of what has occurred other than a message in the Debug window that says "The program '[64480] iisexpress.exe' has exited with code 4294967254 (0xffffffd6).". We have three developers. Our Team license expires next year. All three developers started experiencing the same issue at the same time. Is this a licensing issue, perhaps due to the recent release of ABP 7.0? We haven't upgraded yet. Is that required? What could be the problem here, or what steps do we take to determine what the problem is?

• ABP Framework version: v6.0.1
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace: The program '[64480] iisexpress.exe' has exited with code 4294967254 (0xffffffd6).
• Steps to reproduce the issue: Open the ABP solution in VS 2022. Use F5 to run the Blazor app.

hi

Please try to run app via dotnet run command the check the output and logs.

When we run the app via dotnet run we get the following output...

[10:16:50 INF] TRIAL-INFO - You are using the trial version of ABP and your expiry date is 2023-01-09
[10:16:51 ERR] ABP-LIC-0018 - djcw(redacted)jUX0: Your trial period has ended! - Please contact to license@abp.io to purchase a license.

I redacted some of the text above because I wasn't sure if it's private data. I went to the "Organization Management" page on the ABP Commercial website to view my license info. I see my API key, and I confirmed that this matches the API key we have on our NuGet.Config file (key="ABP Commercial NuGet Source").

Our license expires Jan 2, 2024. Our trial expired Jan 9, 2023, but as far as I know we are not using the trial license anymore. Is there some other place in our code we need to replace the trial license key with the purchased license key? In short, why is it still trying to use our trial license?

Nevermind. I figured it out on my own. I had to uninstall ABP Suite, re-authenticate, create a new dummy application/solution, get the license key from the source code in that application, and copy it into the source code of my original application. The reason is because my application was created while I was still using the trial license. It wasn't clear that any applications created while using the trial license would need to be updated with a new license key (or how to do it). But, again, I figured it out.

I searched the docs and reviewed several similar problems, but none seemed to pertain to the specific error I'm seeing below (or I couldn't find the support document).

I created a Blazor Server app named "ABPBlazor" using ABP Suite, used DbMigrator to set up the database on an Azure SQL database, pushed the code to an Azure DevOps Git repo where a build/package/deploy pipeline released it into an Azure app service. I am now trying to run the application and I'm getting an error. Thanks for your assistance.

• ABP Framework version: v7.0.1
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace: See below
• Steps to reproduce the issue: Visit https://abpblazorapp.azurewebsites.net/

Here is the error:

HTTP Error 500.30 - ASP.NET Core app failed to start

Application '/LM/W3SVC/719996520/ROOT' with physical root 'C:\home\site\wwwroot' has exited from Program.Main with exit code = '1'. First 30KB characters of captured stdout and stderr logs: [18:45:42 INF] Starting web host. [18:45:46 FTL] Host terminated unexpectedly! Volo.Abp.AbpInitializationException: An error occurred during ConfigureServicesAsync phase of the module Volo.Abp.OpenIddict.AbpOpenIddictAspNetCoreModule, Volo.Abp.OpenIddict.AspNetCore, Version=7.0.1.0, Culture=neutral, PublicKeyToken=null. See the inner exception for details. ---> System.Security.Cryptography.CryptographicException: Access is denied. at System.Security.Cryptography.X509Certificates.StorePal.FromSystemStore(String storeName, StoreLocation storeLocation, OpenFlags openFlags) at System.Security.Cryptography.X509Certificates.X509Store.Open(OpenFlags flags) at Microsoft.Extensions.DependencyInjection.OpenIddictServerBuilder.AddDevelopmentEncryptionCertificate(X500DistinguishedName subject) at Microsoft.Extensions.DependencyInjection.OpenIddictServerBuilder.AddDevelopmentEncryptionCertificate() at Volo.Abp.OpenIddict.AbpOpenIddictAspNetCoreModule.<>c__DisplayClass1_0.<AddOpenIddictServer>b__0(OpenIddictServerBuilder builder) at Microsoft.Extensions.DependencyInjection.OpenIddictServerExtensions.AddServer(OpenIddictBuilder builder, Action1 configuration) at Volo.Abp.OpenIddict.AbpOpenIddictAspNetCoreModule.AddOpenIddictServer(IServiceCollection services) at Volo.Abp.OpenIddict.AbpOpenIddictAspNetCoreModule.ConfigureServices(ServiceConfigurationContext context) at Volo.Abp.Modularity.AbpModule.ConfigureServicesAsync(ServiceConfigurationContext context) at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync() --- End of inner exception stack trace --- at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync() at Volo.Abp.AbpApplicationFactory.CreateAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.ServiceCollectionApplicationExtensions.AddApplicationAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.WebApplicationBuilderExtensions.AddApplicationAsync[TStartupModule](WebApplicationBuilder builder, Action1 optionsAction) at ABPBlazor.Blazor.Program.Main(String[] args) in D:\a\1\s\src\ABPBlazor.Blazor\Program.cs:line 36

Process Id: 16792. File Version: 17.0.22341.2. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 7c810658463f35c39c54d5fb8a8dbbfd463bf747

As suggested in the linked question, I did the following:

1. I create a console app to generate two self-signed certificates
2. I uploaded both certificates into Azure
3. I obtained the thumbnails of each certificate
4. I added a WEBSITE_LOAD_CERTIFICATES app setting with a value of the two thumbprints, comma separated

The application event log no longer reports an error. It now says the following: Application 'C:\home\site\wwwroot\' started successfully. Process Id: 2912. File Version: 17.0.22341.2. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 7c810658463f35c39c54d5fb8a8dbbfd463bf747

However, when attempting to load the app in a browser I now see a different error.

I obtained the source of the error from the logs. Here it is.

After sending stdout to a log file I was able to see the source of the problem...

Volo.Abp.AbpException: Could not find file '/libs/bootstrap/css/bootstrap.css'

In my Azure app service my "wwwroot" folder did not have a libs folder, and this was the reason for the error. So I investigated to find out why the libs folder is missing. It turns out that the .gitignore file produced by ABP Suite contains the following...

# Use abp install-libs to restore.
**/wwwroot/libs/*

So, when I committed my code, the contents of the "lib" folder were being ignored. I commented out the second line above and committed the entire contents of the "libs" folder to my code repo. Azure CI/CD then compiled, packaged, and deployed to the Azure app service. Finally the app loaded without errors.

I would like to understand more about why the .gitignore file generated by ABP Suite is configured by default to ignore the libs folder when it is clearly needed for the app to function. Is there an assumption that the developer will execute abp install-libs in the Azure DevOps build pipeline or on the server where the application is ultimately deployed?

Thank you. Since the "libs" folder is not included in the code by default when pushing to a Git repo, can anyone provide steps (YAML code) to restore the contents of the "libs" folder during an Azure DevOps build pipeline?

• ABP Framework version: v7.4.0
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

Quick background. My app relates to the exchange of foreign currencies. I have two entities... a "Currency" (eg. UD dollar, Japanese Yen, etc.) and a "CurrencyPair" (eg. USD/JPY, EUR/USD, etc.). So I have a "Currency" entity with a GUID ID and a name (eg. "USD", "EUR", "JPY", etc.), and I have a "CurrencyPair" entity with a GUID ID and a name (e. "EUR/USD", "USD/JPY", etc.). I created both entities. At this point, there is no relationship between them, and each entity only has an ID and a Name. I was able to "Save and Generate" these entities, which built the code. And I ran the app with no issues.

Now I am trying to define the navigation properties. A "CurrencyPair" must reference two "Currency" entities. For the currency pair called "USD/JPY", "USD" is called the "quote" currency and "JPY" is referred to as the "base" currency. So I have two navigation properties I need called "QuoteCurrency" and "BaseCurrency". So, I defined these as follows when defining the navigation properties on the "CurrencyPair" entity:

1. On the "Basic" tab I selected "Currencies.cs" for the Entity.
2. For Display Property I selected "Name".
3. I toggled the "Required" checkbox ON.
4. On the "Advanced" tab the only thing I changed was to rename Property Name in the Others section from "CurrencyId" to "QuoteCurrencyId"
5. I repeated the above steps for the "base" currency navigation property, thus renaming "CurrencyId" to "BaseCurrencyId"
6. I clicked "Save and Generate"

ABP, after several seconds, produced this error: Error occurred on DB migration step! Make sure the project is compiled and working. Command output: Build started... Build failed. Use dotnet build to see the errors.

Using ABP Suite to define an entity with a 1-n navigation property that is flagged as required... It seems that any time I flag a navigation property as "required" ABP Suite will fail to "Save and generate" the code. When it attempts to, I receive the error provided above. Interestingly, If I remove the required flag on these navigation properties, the issue goes away. If I check the "required" box and try again the error comes back. After seeing this error I switched over to Visual Studio and tried to build the solution. This is what I see.

The issue appears to be with this line of generated code: <Select TValue="Guid"

If I manually change it to: <Select TValue="Guid?"

... in other words, make it nullable, now the solution builds without errors.

Shouldn't this be defined as Guid? always, even if the navigation property is required? This is select item for a filter. Although a value for this property is required in the entity definition, it shouldn't be required to filter by this property. Or may there's something I don't understand about this. Please clarify if you can.

At any rate, vanilla code produced by ABP Suite (before any custom modifications) should not produce ABP Suite and build errors... unless I'm doing something wrong. Please advise.

• ABP Framework version: v7.3.3 and v7.4.0
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace: N/A
• Steps to reproduce the issue:

I installed ABP, ABP CLI, and ABP Suite several weeks ago. At that time I was using ABP Suite 7.3.3 and created my first project. Everything worked great. Fast forward several weeks. Time to create a new project. I updated ABP to 7.4.0 and created my new project. Everything worked great. But now I have two projects. One was built on 7.3.3 and the other was 7.4.0. I tried to upgrade the 7.3.3. project to 7.4.0 but encountered all kinds of errors. So I decided to keep it on 7.3.3 for now.

Next, I needed to add an entity in my 7.3.3. project. In ABP Suite I got an error when attempting this because I'm running 7.4.0 and trying to create entities in a 7.3.3. project. Fortunately, I figured out the solution... remove ABP Suite 7.4.0 and install ABP Suite 7.3.3. Then I could open my 7.3.3. project in ABP Suite and make changes. Great.

But now I need to work in my 7.4.0 project again. Unfortunately, I'm getting ABP Suite errors again because I'm trying to use 7.3.3 to add an entity into a 7.4.0 project. Yes, I could remove 7.3.3 and install 7.4.0. So it appears that every time I need to make a change in one of my projects, however minor, I need to remove ABP Suite and re-install it using the correct version before opening my project in ABP Suite. That's cumbersome if, like me, you create multiple projects for several customers and need to manage them all... sometimes touching on 2-3 projects at a time and needing to switch back and forth between them several times in a given work week.

Is this what you must do every time you want to work with a project that was created on a different version of ABP Suite? Or, is there some way to launch ABP using a specific version? You might sau, just upgrade everything to 7.4.0. But that's easier said then done. It's sort of a complex process involving creating an empty project on both the old and new version then using WinMerge to determine the difference and manually editing the older project. It's pretty messy. So I don't agree that upgrading is always the best solution, especially for complex projects where entities classes, pages, etc created in ABP Suite might have been drastically altered.

Short question. What's the best way to manage ABP projects of varying versions?

A great answer would be something like... "Just type 'abp suite install --version 7.3.3' and 'abp suite install --version 7.4.4' to install both versions and then type 'abp suite --version 7.4.0'" to open ABP Suite using one of the many versions of it (eg 7.4.0) that you might have installed. That way, if I need to switch to the 7.3.3. project I can just exit ABP Suite and type 'abp suite --version 7.3.3.' to work on the other project. Is something like this possible? If not, can you make it happen?

• ABP Framework version: v8.0.0

• UI Type: Blazor WASM

• Database System: EF Core (SQL Server)

• Tiered (for MVC) or Auth Server Separated (for Angular): no

• Exception message and full stack trace:

• System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Code\extranerds\AProInspector\test\AProInspector.TestBase\AddressTypes\AddressTypesDataSeedContributor.cs'. at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options) at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode) at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode) at System.IO.File.OpenText(String path) at Volo.Abp.IO.FileHelper.ReadAllTextAsync(String path) in D:\ci\Jenkins\workspace\abp-volo-release\abp\framework\src\Volo.Abp.Core\Volo\Abp\IO\FileHelper.cs:line 59 at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.UnitTestCommandCommand.mgaozo0CnE(String ) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.UnitTestCommandCommand.LshoDsMRxy(TestDataObject , Int32 ) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.UnitTestCommandCommand.ipuoypI5wn() at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.UnitTestCommandCommand.ExecuteAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.CommandManager.ExecuteAllAsync(CrudPageCommandOptions options) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.CrudPageGenerator.GenerateAsync(EntityModel entity, Solution solution, EntityModel masterEntity) at Volo.Abp.Suite.Controllers.CrudPageGeneratorController.SaveAndGenerateEntityAsync(Guid solutionId, EntityModel entity) at lambda_method2022(Closure, Object) at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfActionResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)PS C:\Code\extranerds\AProInspector> Shutting down...

• Steps to reproduce the issue:

1. Create a new project
2. Add a new entity using ABP Suite named "AddressType" (AddressTypes plural)
3. Add another new entity using ABP Suite named "ClientAddress" (ClientAddresses plural) with a 1-n navigation property referencing AddressTypes
4. Save and Generate

Notice that the exception is the result of the process trying to locate "AProInspector.TestBase\AddressTypes\AddressTypesDataSeedContributor.cs". However, that file exists elsewhere at "AProInspector.Domain.Tests\AddressTypes\AddressTypesDataSeedContributor.cs".

Please provide a temporary workaround if possible. I'm dealing with a deadline. Thank you.