KeyserDSoze/Rystem.RepositoryFramework.Infrastructure.Dynamics.Dataversev3.1.5
.NET 10.0
Rystem.RepositoryFramework allows you to use correctly concepts like repository pattern, CQRS and DDD. You have interfaces for your domains, auto-generated api, auto-generated HttpClient to simplify connection "api to front-end", a functionality for auto-population in memory of your models, a functionality to simulate exceptions and waiting time from external sources to improve your implementation/business test and load test.
Get Started
$ dotnet add package Rystem.RepositoryFramework.Infrastructure.Dynamics.DataverseReadme
What is Rystem?
Integration with Dataverse (Dynamics) and Repository Framework
builder.Services.AddRepositoryDataverse<CalamityUniverseUser, string>(x =>
{
x.Prefix = "repo_";
x.SolutionName = "TestAlessandro";
x.Environment = configuration["ConnectionString:Dataverse:Environment"];
x.ApplicationIdentity = new(configuration["ConnectionString:Dataverse:ClientId"],
configuration["ConnectionString:Dataverse:ClientSecret"]);
})
.AddBusinessBeforeInsert<CalamityUniverseUserBeforeInsertBusiness>()
.AddBusinessBeforeInsert<CalamityUniverseUserBeforeInsertBusiness2>();
You found the IRepository<CalamityUniverseUser, string> in DI to play with it.
Configure database after build
You have to run a method after the service collection build during startup. This method creates your tables.
var app = builder.Build();
await app.Services.WarmUpAsync();
Automated api with Rystem.RepositoryFramework.Api.Server package
With automated api, you may have the api implemented with your dataverse integration. You need only to add the AddApiFromRepositoryFramework and UseApiForRepositoryFramework
builder.Services.AddApiFromRepositoryFramework(x =>
{
x.Name = "Repository Api";
x.HasSwagger = true;
x.HasDocumentation = true;
});
var app = builder.Build();
app.UseHttpsRedirection();
app.UseApiForRepositoryFramework();