NET 5.0 RC 1. منتشر شد
Today, we are shipping .NET 5.0 Release Candidate 1 (RC1). It is a near-final release of .NET 5.0, and the first of two RCs before the official release in November. RC1 is a “go live” release; you are supported using it in production.
NET 9 Release Candidate 2. منتشر شد
services.AddDNTScheduler(options => { // DNTScheduler needs a ping service to keep it alive. Set it to false if you don't need it. options.AddPingTask = true; options.AddScheduledTask<DoFillDataTask>( runAt: utcNow => { var schedulerTask = _config.GetSection("SchedulerTask"); var now = utcNow.AddHours(4.5); return now.Hour == 10 && now.Minute == 0 && now.Second == 0; }, order: 1); });
As discussed previously, this adds Razor support behind a new omnisharp.preview options flag. It works by downloading a platform-specific Razor Language Server executable (equivalent to the OmniSharp-Roslyn language server) and then running some VSCode-side logic that knows how to launch and interact with it.
Entity Framework Core 2.0 introduces global query filters that can be applied to entities when a model is created. It makes it easier to build multi-tenant applications and support soft deleting of entities. This blog post gives a deeper overview of how to use global query filters in real-life applications and how to apply global query filters to domain entities automatically.
همه چیز درباره الگوی طراحی Singleton
Singleton design pattern is one of the simplest design patterns: it involves only one class throughout the application which is responsible to instantiate itself, to make sure it creates not more than one instance; in the same time it provides a global point of access to that instance. In this case the same instance can be used from everywhere, being impossible to invoke directly the constructor each time.
حسابداری برای توسعه دهندهها
Accounting For Software Engineers
The difference between accountants and software engineers, when it comes to accounting systems, is about what we primarily care about. Accountants care about meaning: is the quick ratio in good shape? Is income growing at an expected rate? How do we deal with an upcoming expense? Software engineers care about: will we properly move money around so that the balances are correct given certain latency, concurrency, etc.? Do we have the information required to generate the Income Statement? How do we represent a credit memo?
Nowadays, I am trying to learn different design patterns in object oriented paradigm that are pretty useful to implement generic solutions for different scenarios. Few weeks ago for a job hunt, I got an assignment to do which was a web application that would interact with database, so I took it up as a challenge and decided to make it loosely coupled using design patterns which were applicable in that scenario.