بله درسته، من یک لحظه از وابستگی razor به کامپایلر #C غافل شدم.

در intelij idea میشد خیلی از امکانات webstorm رو با کمک plugin اضافه کرد، با اینکه rider رو استفاده کردم اما به این نکته دقت نکردم، آیا توی rider هم این امکان هست؟

In short, domain events help you to express, explicitly, the domain rules, based in the ubiquitous language provided by the domain experts. Domain events also enable a better separation of concerns among classes within the same domain. It's important to ensure that, just like a database transaction, either all the operations related to a domain event finish successfully or none of them do. Domain events are similar to messaging-style events, with one important difference. With real messaging, message queuing, message brokers, or a service bus using AMQP, a message is always sent asynchronously and communicated across processes and machines. This is useful for integrating multiple Bounded Contexts, microservices, or even different applications. However, with domain events, you want to raise an event from the domain operation you are currently running, but you want any side effects to occur within the same domain. The domain events and their side effects (the actions triggered afterwards that are managed by event handlers) should occur almost immediately, usually in-process, and within the same domain. Thus, domain events could be synchronous or asynchronous. Integration events, however, should always be asynchronous.

• Custom Project Template Not Found
• msvsmon.exe crashes when hitting breakpoint in native C++ code
• Search for a folder in solution explorer, then click home or the X in the search box. The view is reset.
• External Tools argument current line is always zero.
• Can't create v3 Function project.
• Access violation reading location 0xFFFFFFFFFFFFFFFF. after updating to VS 2019 Update 16.4.3
• Cannot create function app under 16.4
• MSVC2019 generates AVX-512 instruction in AVX/AVX2 mode
• Bad code generation with rsqrtss (register clobber)
• Visual Studio 2019 Debugger crashes when viewing FastLink callstack.
• C#: Fixed a crash when an attribute constructor is decorated with itself and Nullable Reference Types is enabled.
• Fixed an optimization-analysis bug where we lose track of alias information for arrays of indeterminate length (declared as extern int a[]) when we unroll loops, leading to possible incorrect dead-store removal. 

PostSharp 6.0 is the biggest refactoring since the 2.0 version released in July 2010. For a good cause: PostSharp 6.0 now runs natively in .NET Core 2.0. Previous versions of PostSharp executed only under .NET Framework at build time and the support for .NET Core was achieved by using a load of hacks that ended up being unmaintainable, warranting this big refactoring.

Let’s have a look at the new features of PostSharp 6.0 :

• Support for .NET Core 2.0-2.1 and .NET Standard 2.0.
• Support for Portable PDB.
• Support for C# 7.2.
• Ending the PostSharp versioning hell side-by-side: backward compatibility within the same major version.
• Logging: robustness to faults in the logging subsystem.
• Logging: no need to initialize before the first logged method is hit.
• Caching: preventing concurrent execution (locking).
• Visual Studio tooling: support for the new CPS-based project systems.
• GDPR compliance: we no longer collect your name and email for trial, nor use unsecure HTTP, nor use non-resettable user id hashes. 

Sleep is MORE important than Eating 

Aurelia is one of the best frameworks that we have ever seen in terms of software design, hence, we decided to write a bunch of tools for its developers to pave the way for further usage.

aurelia-toolbelt is that, in which we tried to gather the best libraries in Javascript world together in aurelia fashion. Writing custom-elements, value-converters, and so on. We tried not to invent the wheel, so most of the work is a wrapper, or bridge( am not sure whether the way that we coded can be called bridge or not), around other libraries.

• Its is utterly important for us to provide a link as a reference to the libraries used, or inspired from, so that other developers can visit their product and decide on their own to use which, besides it's one way that we can respect the time and effort of those programmers.

• All libraries used in aurelia-toolbelt are open-source and free of charge; most of which are  MIT , however we will provide definition whenever it differs. 

GitHub : aurelia-toolbelt

NPM : aurelia-toolbelt

Twitter : aureliatoolbelt

At Build 2019, Microsoft announced the release date for .NET Core 3.0 to be this coming September. This release includes the highly touted support for desktop platforms like WinForms and WPF. Today, there’s still a large developer base that’s building desktop applications using these .NET Windows desktop frameworks and by using .NET Core 3.0, you can now build desktop applications on the .NET Core platform.