Entity Framework half-heartedly supported Domain-Driven Design patterns. But the new-from-scratch EF Core has brought new hope for developers to map your well-designed domain classes to a database, reducing the cases where a separate data model is needed. EF Core 2.1 is very DDD friendly, even supporting things like fully encapsulated collections, backing fields and the return of support for value objects. In this session, we'll review some well-designed aggregates and explore how far EF Core 2.1 goes to act as the mapper between your domain classes and your data store.
اشتراکها
بررسی NET Standard.
Description
There has been a lot of talk lately about .NET Standard, both in the community and on Channel 9. But there is also still confusion about it. In this episode, Kathleen Dollard clears up some of this confusion. She and Robert chat about why .NET Standard was created, as well as how and when you should take advantage of it.
نظرات مطالب
خلاصه اشتراکهای روز جمعه 4 آذر 1390
یک سری توهماتی این دور و اطراف هست مانند اینکه لینوکس نیازی به ویروس یاب نداره، لینوکس امنه، لینوکس خیلی گله! بی نظیرتر از اون نیست؛ ولی واقعیت این است که این سیستم عامل زمانیکه از اون حد کاربران یک یا چند درصدی دستکاپ خودش فاصله میگیره و مثلا میشه Android، تازه مشخص میشه که ای بابا! ویندوز هم امنه! اگر کاربری نمیدونه هر فایلی رو نباید اجرا کنه، هر دسترسی رو نباید بده این مشکل سیستم عامل نیست. ولی خوب این هجمه سیاسی و عموما کودکانه علیه ویندوز وجود داره و گاهی هم لازم هست اینها رو کمی عیانتر بیان کرد با مثالهای دنیای واقعی تا کمی از توهمات دور بشیم که بله؛ اگر از کاربران حرفهای سرورها فاصله بگیریم میرسیم به «عوام». میرسیم به دنیایی خارج از یک یا چند درصد کاربری دسکتاپ. اینجا است که حالا باید دید سیستم عامل تا چه حد میتونه مؤثر واقع بشه، یا اینکه رکورد بزنه تا تاریخ امروز.
یک CMS تجاری بزرگ با قابلیتهای زیر
A modular, service based web application model
Code generator to produce initial services / user interface code for an SQL table
T4 based code generation on server to reference script widgets with intellisense / compile time validation
T4 based code generation to provide compile time type safety and intellisense while calling AJAX services from script side.
An attribute based form definition system (prepare UI in server side with a simple C# class)
Automatic seamless data-binding through form definitions (form <-> entity <-> service).
Caching Helpers (Local / Distributed)
Automatic cache validation
Configuration System (storage medium independent. store settings in database, file, whatever...)
Simple Logging
Reporting (reports just provide data, has no dependency on rendering, similar to MVC)
Script bundling, minification (making use of Node / UglifyJS / CleanCSS) and content versioning (no more F5 / clear browser cache)
Fluent SQL Builder (SELECT/INSERT/UPDATE/DELETE)
Micro ORM (also Dapper is integrated)
Customizable handlers for REST like services that work by reusing information in entity classes and do automatic validation.
Attribute based navigation menu
UI Localization (store localized texts in json files, embedded resource, database, in memory class, anywhere)
Data Localization (using an extension table mechanism helps to localize even data entered by users, like lookup tables)
Script widget system (inspired by jQueryUI but more suitable for C# code)
Client side and server side validation (based on jQuery validate plugin, but abstracts dependency)
Audit logging (where CDC is not available)
System for data based integration tests
Dynamic scripts
Script side templates
اشتراکها
استفاده از default و check در SQL
SQL is unusual is that data is not passively stored. Instead you use declarative SQL to specify the rules that underlie the data and its integrity. When used properly, constraints can avoid having to provide a lot of logic elsewhere. CHECK() and DEFAULT can do a lot to ensure that your data is correct