Thank you, that worked for me. Is there something extra that I need to do to get the current value to show when the page initially shows? It always just shows as blank.
The abp-date-picker does not appear to be respecting the minDate option. According to the documentation, https://docs.abp.io/en/abp/7.2/UI/AspNetCore/Tag-Helpers/Form-elements#tag-attributes-3, the below should work but nothing happens.
<abp-date-picker asp-for="CreateTransaction.SendDate" data-minDate="05/23/2023" date-format="MM/DD/YYYY" />
Thanks for the suggestion. Instead of creating a shared module, we decided to use the business exception code namespace to lookup the correct localization resource.
I have a solution with several modules (CoreModule, CrmModule, etc.). I have a need to access localization from CrmModule within CoreModule. When I attempt to do so, the error code is not found. What do I need to do to be able to access localization across all modules?
Below is details regarding my scenario.
BusinessException (in CrmModule):
public class ContactDoesNotExistException : BusinessException { public ContactDoesNotExistException() : base(CrmErrorCodes.ContactDoesNotExistException) { } }
ErrorCode (in CrmModule):
public const string ContactDoesNotExistException = "Contact:00001";
en.json (in CrmModule):
"Contact:00001": "Contact does not exist",
Write exception message to a string (in CoreModule):
exceptionMessage = L[((BusinessException)row.Exception).Code];
I want exceptionMessage to display "Contact does not exist" but instead I'm getting "Contact:00001."
I was able to solve the issue by adding the below to my EntityFrameworkCoreTestModule:
new BlobStoringDbContext( new DbContextOptionsBuilder<BlobStoringDbContext>().UseSqlite(connection).Options ).GetService<IRelationalDatabaseCreator>().CreateTables();
in the CreateDatabaseAndGetConnection method.
DbMigrator is working without issue and is seeding data, including blob storage data, as expected.
The issue is only occurring when running the automated tests. I am specifically looking for guidance on working with blob storage from the test projects.
No BLOB Storage provider was registered! At least one provider must be registered to be able to use the BLOB Storing System.
Hi,
You need to configure a BLOB Storage provider: https://docs.abp.io/en/abp/latest/Blob-Storing#blob-storage-providers
It appears that it needs this configuration somewhere in tests in order to work. Where should that go?
No BLOB Storage provider was registered! At least one provider must be registered to be able to use the BLOB Storing System.
Hi,
You need to configure a BLOB Storage provider: https://docs.abp.io/en/abp/latest/Blob-Storing#blob-storage-providers
It is configured in the WebModule.
private void ConfigureBlobStorage(ServiceConfigurationContext context, IConfiguration configuration)
{
var env = context.Services.GetHostingEnvironment();
Configure<AbpBlobStoringOptions>(options =>
{
options.Containers.ConfigureDefault(container =>
{
//use database blob storage for development convenience, use Azure in production
if (env.IsDevelopment())
{
container.UseDatabase();
}
else
{
container.UseAzure(azure =>
{
azure.ConnectionString = configuration["AzureBlobProviderConfiguration:ConnectionString"];
azure.ContainerName = configuration["AzureBlobProviderConfiguration:ContainerName"] ?? "default";
azure.CreateContainerIfNotExists = bool.TryParse(configuration["AzureBlobProviderConfiguration:CreateContainerIfNotExists"], out bool createContainerIfNotExists) ? createContainerIfNotExists : true;
});
}
});
});
}
I have a solution with several modules added (one of them is called Core). In Core.Domain I have an entity called Attachments (Attachments are files that users can upload to the system). In Core.Domain I have AttachmentDataSeederContributor where I seed one attachment. As part of this seed data, I have a need to save the file contents in my seed data to blob storage.
When I run DBMigrator, my data seeds as expected. However, when I attempt to run my tests, I receive the following error for all tests:
Message:
Volo.Abp.AbpInitializationException : An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module PlatformNext.Core.CoreTestBaseModule, PlatformNext.Core.TestBase, Version=0.1.0.0, Culture=neutral, PublicKeyToken=null: An exception was thrown while activating PlatformNext.Core.Attachments.AttachmentDataSeederContributor -> λ:Volo.Abp.BlobStoring.IBlobContainer -> Volo.Abp.BlobStoring.BlobContainer1[[Volo.Abp.BlobStoring.DefaultContainer, Volo.Abp.BlobStoring, Version=6.0.1.0, Culture=neutral, PublicKeyToken=null]].. See the inner exception for details. ---- Autofac.Core.DependencyResolutionException : An exception was thrown while activating PlatformNext.Core.Attachments.AttachmentDataSeederContributor -> λ:Volo.Abp.BlobStoring.IBlobContainer -> Volo.Abp.BlobStoring.BlobContainer1[[Volo.Abp.BlobStoring.DefaultContainer, Volo.Abp.BlobStoring, Version=6.0.1.0, Culture=neutral, PublicKeyToken=null]].
-------- Autofac.Core.DependencyResolutionException : An exception was thrown while invoking the constructor 'Void .ctor(Volo.Abp.BlobStoring.IBlobContainerFactory)' on type 'BlobContainer`1'.
------------ Volo.Abp.AbpException : No BLOB Storage provider was registered! At least one provider must be registered to be able to use the BLOB Storing System.
Thank you, that made it work.