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.
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 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.
Do you have an updated release date?
<cite>ismcagdas: </cite> Hi @trendline,
ABP's breaking changes are mentioned here <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/releases">https://github.com/aspnetboilerplate/as ... e/releases</a> and <a class="postlink" href="https://github.com/aspnetboilerplate/module-zero/releases">https://github.com/aspnetboilerplate/mo ... o/releases</a>.
We are planning to release AspNet Zero v4.1 next week. If you want to use latest ABP earlier than that, we can try to help you with the errors you are getting.
Thanks.
Do you have an updated release target for 4.1? We have purchased the template and are about to begin development, but we want to wait until the next version is out to avoid a painful upgrade path once we begin customizing the template..
