#CODE CHICKEN CORE 1.9 PORTABLE#
#CODE CHICKEN CORE 1.9 CODE#
#CODE CHICKEN CORE 1.9 WINDOWS 8#
#CODE CHICKEN CORE 1.9 WINDOWS#

In contrast to regular assemblies contract assemblies are designed around proper factoring. Contracts are simply assemblies that you compile against. The idea of contracts is to provide a well factored API surface area.

This made it very complicated to tool a class library experience that lets you target multiple verticals. This forces each vertical to subset even the very core of the platform. NET Framework contains many features that that canвЂ™t be supported everywhere (for example, remoting and AppDomains). The very core assembly that everything else depends on is mscorlib. NET Framework was designed around the assumption that itвЂ™s always deployed as a single unit, so factoring was not a concern.

#CODE CHICKEN CORE 1.9 WINDOWS#

When we designed the Windows Store profile we introduced a new concept to model the subsetting in a better way: contracts.

#CODE CHICKEN CORE 1.9 WINDOWS 8#

In the Windows 8 timeframe we came up with a plan to deal with this problem. This made targeting multiple verticals a daunting task. You were essentially stuck with creating multiple projects, linked files, and #if.

#CODE CHICKEN CORE 1.9 PORTABLE#

No portable class libraries, no shared projects.

#CODE CHICKEN CORE 1.9 CODE#

Originally, there was no concept of code sharing across verticals. Thus, itвЂ™s critical to support developers in building components that can span all the. Today itвЂ™s extremely common to have applications that span devices: there is virtually always a back end that runs on the web server, there is often an administrative front end that uses the Windows desktop, and a set of mobile applications that are exposed to the consumer, available for multiple devices. Now you have to reason about the availability of APIs and come up with a way to produce assets that work across the verticals you want to target. The problem arises as soon as you want to target the horizontal, that is multiple verticals. YouвЂ™re provided with an API set that is optimized for your vertical. What is the problem with fragmentation? If you only target a single vertical then there really isnвЂ™t any problem. Over time this causes more divergence unless explicit (and expensive) measures are taken to converge APIs. The outcome is a set of platforms that only share APIs by the fact that they started off from a common code base. But it becomes a problem if there is no systematic approach and specialization happens at every layer with little to no regards for corresponding layers in other verticals. Of course, there is nothing wrong with offering specialized features in order to cater to a particular need. NET Platform isnвЂ™t a single entity but a set of platforms, owned by different teams, and maintained independently. This yields to fragmentation because the. Since then, weвЂ™ve repeated this subsetting exercise many times: Silverlight, Windows Phone and most recently for Windows Store. It included the entire vertical: a runtime, a framework, and an application model on top. The compact framework was a separate code base from the. NET Framework that fit within the footprint of smaller devices, specifically Windows Mobile. NET Compact Framework which was a subset of the. NET Framework in 2002 there was only a single framework. This helps to motivate some of the decisions and ideas that resulted in the creation of. NET CoreДЇirst letвЂ™s look back to understand how the. NET Framework, and what this means for cross-platform and open source development. NET Core, how weвЂ™re going to release it, how it relates to the. In this post, IвЂ™ll provide an overview of. I also promised to follow up with more details on. NET Core will be entirely released as open source software.

Code chicken core 1.9