Activities of "strix20"

<cite>ervingayle: </cite> I am using jQuery & .Net Core and hope to move to a continuous deployment model in Azure. So far there are aspnetboilerplate, jquery & .net (aspnetzero) which are being migrated into .net core jquery (aspnetzero). For Development, Staging & Production environments while you specify your configuration for each environment in the solution Azure does not provide specific isolation for an application with these SDLC environments. Essentially to mimic that model you will need to create three App Services applications.

As for continuous integration/deployment, there are some problems with deploying in my case because when the site is in use the ProjectName.Application.dll is use which causes the continuous deployment task to fail. I have even tried setting the app variable to offline (which is not ideal) because it will take the app offline during deployment to free in use files but this also fails.

You may not face this behavior using the Angular version but this has been my experience. Also to note, this is not happening with the .net aspnetzero application.

Have you tried using Team City and Octopus for your CI and automated deployment? The Azure CI in general is pretty bad. TC+Octo will give you much more control.

IdentityServer4 is an OAuth 2.0 Framework to provide authentication as a middleware service. It is designed to support authentication across multiple applications, not a single application with multiple tenants.

You can learn more about IdentityServer4 here:

[https://identityserver4.readthedocs.io/en/release/intro/terminology.html])

I am currently using the ASP.NET Core & jQuery version of asp.netzero and having trouble figuring out what the proper teamcity build steps should be to create a nuget package that I will then use to deploy using octopus. With my current configuration I install a nuget feed that the solution requires, do a dotnet restore, build the solution using visual studio, run tests, and then run a nuget pack. When I run the nuget pack my build fails because: "Unable to find 'C:\TeamCity\buildAgent\work\c04235ef53f2bb5a\src\Strix.Customs.Web.Mvc\bin\Release\net462\Strix.Customs.Web.Mvc.exe'. Make sure the project has been built."

Does anyone know what my build steps should look like here?

ABP is open source... you can find all of the ABP code in the public repository.

<a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/blob/dev/src/Abp/Modules/AbpModule.cs">https://github.com/aspnetboilerplate/as ... pModule.cs</a>

Now that Core 2.0 is out, can we expect a release that updates the system to a version of .net core that actually works?

I agree completely.

.Net core 1.1 is NOT production ready. We can't even begin to consider going to production prior to 2.0, and 2.0 will have major changes to the .net standard model.

What are the plans for the 2.0 upgrade path?

Does the development team have an internal build targeting 2.0 Preview?

What kind of breaking changes are we looking at?

Thanks for the response!

I am curious, what I actually did was this:

services.AddSingleton<IConnectionStringResolver, AzureKeyVaultConnectionStringResolver>();

in my startup.cs.

Is your method preferable? It seems your approach will override only for that module, but I don't know what modules embedded in ABP will be relying on a connection string?

We must use Azure Key Vault to store all secrets, including our connection strings.

I changed the CustomsEntityFrameworkCoreModule PreInitialize method to look like such:

public override void PreInitialize()
        {
            var connectionString = _appConfig["db-dev"];
            Configuration.DefaultNameOrConnectionString = connectionString;

            if (!SkipDbContextRegistration)
            {
                Configuration.Modules.AbpEfCore().AddDbContext<CustomsDbContext>(configuration =>
                {
                    CustomsDbContextConfigurer.Configure(configuration.DbContextOptions, connectionString);
                });
            }
        }

This works locally, but breaks in a hosted environment.

How can I replace the DefaultConnectionStringResolver?

We use Quartz almost exclusively for scheduled jobs. It's very easy to set up.

We actually developed a very simple service that combined Quartz with an AWS SQS queue, where quartz would trigger an SQS message, and the service would monitor the SQS queue for messages and respond with jobs accordingly. This allowed us to also manually trigger jobs from our web application, or from other services.