In response to Sahil Malik's recent post on CLR Types as UDT's in Yukon, I have to say I prefer the Typed Xml in Yukon to CLR Types.
In Yukon there are two paths to creating User Defined Types. The CLR path has some limitations, (primarily the 8K size limititation). I am a big fan of the XML Type path. Typed XML inside the server is a better way to create complex types in the database IMHO. Typed XML is schema based. This means the types in your database can be exposed externally as well if needed (like through web services <some of you might be seeing a pattern emerge here>).
In addition, Microsoft's extensions to XQuery (which I hope the standards board adopt) allow you to do in-place editing of Typed XML which means you don't have to do wholesale replacement of xml documents any longer (or wholesale changes to CLR based UDF's). The syntax allows you to do insert, updates and deletes to individual nodes (or series' of nodes).
|Vue.js by Example (New Lower Price)|
|Bootstrap 4 by Example (New Lower Price)|
|Intro to Font Awesome 5 (Free Course)|
|Building an API with ASP.NET Core (New Course)|
|Building a Web App with ASP.NET Core, MVC6, EF Core, Bootstrap and Angular (updated for 2.2)|
|Less: Getting Started (New)|
|Using Visual Studio Code for ASP.NET Core Projects|
|Implementing ASP.NET Web API|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||v4.0.30319||Runtime Framework||x86|
|App Path||D:\home\site\wwwroot\||Runtime Version||.NET Core 4.6.27514.02|
|Operating System||Microsoft Windows 10.0.14393||Runtime Arch||X86|