(public).sospep.subjects ~ view article ~ what-dot-net-developers-ought-to-know-to-start-in-2017

<h1 style="text-align: center;">what .net developers ought to know to start in 2017</h1>
<h2>[WHAT]</h2>
<ol>
<li>[SUMMARY] by Scott Hanselman @ hanselman.com - Hanselman calls out what key .net concepts developers ] NEED to know, &nbsp;] SHOULD know and ] NICE to know circa 2107</li>
<li>*] the mindmap illustration is my interpration of .net (2017) and different than the illustration used in in Scotts article.</li>
</ol>
<h2>[WHY]</h2>
<p><iframe src="https://bubbl.us/Mzg0NDAxNy83NjIyNTc1LzFjMGE5MDAwNzYyNGJiYzhjY2VmNDA3NDI5N2ExZTdk-X?s=7622575" frameborder="0" width="90%" height="600"></iframe></p>
<h2>[WHERE]</h2>
<ol>
<li><strong>] READ THE FULL ARTICLE</strong></li>
<ol>
<li>]&nbsp;<a href="http://www.hanselman.com/blog/WhatNETDevelopersOughtToKnowToStartIn2017.aspx" target="_blank">http://www.hanselman.com/blog/WhatNETDevelopersOughtToKnowToStartIn2017.aspx</a></li>
</ol></ol>
<h2>[WHEN]</h2>
<ol>
<li>] 2017-01-21</li>
</ol>
<h2>[EXAMPLE]</h2>
<p><strong>[NEED to know]</strong></p>
<ol>
<li><strong>]&nbsp;definition - .net&nbsp;</strong></li>
<ol>
<li>] net is - an evolving platform/framework from microsoft that offers a complete toolset for developing and executing a variety of software applications types ( desktop, web, mobile) and services across multiple Operating System platforms. &nbsp;Components consist of both proprietary closed source and&nbsp;open source.&nbsp;</li>
</ol>
<li><strong>] runtimes&nbsp;</strong></li>
<ol>
<li>] .net core,&nbsp;</li>
<li>] framework 4.6.x,&nbsp;</li>
<li>] mono ,</li>
</ol>
<li><strong>]&nbsp;languages&nbsp;</strong></li>
<ol>
<li>] c#,&nbsp;</li>
<li>] f#,&nbsp;</li>
<li>] vb&nbsp;</li>
<li>] more ...&nbsp;</li>
</ol>
<li><strong>] platforms-os</strong></li>
<ol>
<li>] win&nbsp;</li>
<li>] osX</li>
<li>] linux</li>
<li>] iOS</li>
<li>] android</li>
</ol>
<li><strong>] frameworks-dev</strong>()</li>
<ol>
<li>]&nbsp;</li>
</ol>
<li><strong><span style="background-color: #00ff00;">NEW</span>] TargetFrameworkMonitor(TFM)</strong>&nbsp;</li>
<ol>
<li>] moniker that lets you refer to a runtime version ( runtime + version)&nbsp;</li>
<li>] Choosing a TFM decides which APIs are available to you, and which frameworks your code can run on.</li>
</ol>
<li><strong>] Nuget</strong>&nbsp;</li>
<ol>
<li>] package manager, centralized package repository(repo), use console cli to download and install packages() into your application</li>
</ol>
<li><strong>] <a href="http://stackoverflow.com/questions/2972732/what-are-net-assemblies" target="_blank">Assembly</a></strong> -&nbsp;</li>
<ol>
<li>] ? compiled code library, collection of dll's/exes to perform some task, ex LINQ, ? ex to use LINQ in your .net application you need to add a reference to the LINQ assembly,&nbsp;</li>
<li>]&nbsp;An assembly is typically a DLL or EXE containing compiled code. Assemblies are the building blocks of .NET Full Framework applications; they form the fundamental unit of deployment, version control, reuse, activation scoping, and security permissions. In .NET Core, the building blocks are NuGet packages that contain assemblies PLUS additional metadata</li>
</ol>
<li><strong><span style="background-color: #00ff00;">NEW</span></strong>] <strong>netstandard</strong>&nbsp;</li>
<ol>
<li>] simplifies references between binary-compatible frameworks, allowing a single target framework to reference a combination of others. The&nbsp;<a href="https://docs.microsoft.com/en-us/dotnet/articles/standard/library" target="_blank">.NET Standard Library</a>&nbsp;is a formal specification of .NET APIs that are intended to be available on all .NET runtimes.</li>
</ol>
<li><strong>] framework VS core&nbsp;</strong></li>
<ol>
<li>] framework is latest version, monolithic, windows only,&nbsp;</li>
<li>] core is cross platform, core has only subset of functionality/features of framework</li>
</ol></ol>
<p><strong>[SHOULD Know]</strong></p>
<ol>
<li><strong>] Common Language Runtime(CLR) -</strong> for .net framework applications, on windows, ,runtime that accepts compiled IL code and executes it,</li>
<li>] <strong>coreCLR</strong> - runtime for .net core applications, on linux, osX&nbsp;</li>
<li><strong>] mono</strong> - runtime for ios and android os platforms</li>
<li><strong>] coreFX</strong> -&nbsp;</li>
<li><strong>] roslyn</strong> - compiler, compiles supported languages source code to IL, which is executed on the runtime . Exposes API's for reading, writing, analyzing source code</li>
<li><strong>] Garbage Collection(GC)</strong> - uses GC to provide automatic memory management for code, ex garbage = objects that are no longer in use,&nbsp;</li>
<li><strong>] Managed Code(MC)</strong> - execution is managed by the runtime, managed = "automatic GC", memory management,&nbsp;</li>
<li><strong>] Intermediate Language(IL)</strong> -&nbsp;</li>
<li><strong>] Just In Time (JIT)</strong>&nbsp;</li>
<li>] disk location -&nbsp;</li>
<li>] Shared framework(SF) VS Self Contained Apps - SF (aka .net framework) &lt; SCA because #2] easier to distribute, multiple version,&nbsp;</li>
<li>] async &amp; await -</li>
<li><strong>] Portable Class Libraries(PCL)</strong> -&nbsp;"lowest common denominator" libraries that allow code sharing across platforms. Although PCLs are supported, package authors should support netstandard instead. The .NET Platform Standard is an evolution of PCLs and represents <strong>binary portability across platforms.</strong></li>
<li>] .net Core = 4] &nbsp; ] framework, ] SDK tools (compilers, )&nbsp;] host, ] runtime,</li>
</ol>
<p><strong>[NICE TO Know]</strong></p>
<ol>
<li><strong>] Global Assembly Cache (GAC)</strong> -&nbsp;is where the .NET full Framework on Windows stores shared libraries. You can list it out with "gacutil /l"&nbsp;</li>
<li><strong>] Assembly loading and binding</strong> -&nbsp;</li>
<li><strong>] Profiling ()</strong>&nbsp;</li>
<li><strong>] Language Integrated Native Query(LINQ)&nbsp;</strong></li>
<li><strong>] Common Type System(CTS)</strong></li>
<li><strong>] Common Language Specification(CLS)</strong></li>
<li><strong><span style="background-color: #00ff00;">NEW</span>] .net native -&nbsp;</strong></li>
<li><strong><span style="background-color: #00ff00;">NEW</span>] .net roadmap -&nbsp;</strong></li>
<li><strong><span style="background-color: #00ff00;">NEW</span>] c# 7 -&nbsp;</strong></li>
<li>] <strong>Reactive Extensions&nbsp;</strong>(Rx) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators." You can create sophisticated event-based programs that work cleanly and asynchronously by applying LINQ-style operators to data streams.</li>
</ol>
<p>&nbsp;</p>
<p>org by - ] RUNTIME/LANGUAGES, ] PLATFORMS/FRAMEWORKS , ]&nbsp;</p>
<h2>[HOW-TO]</h2>
<ol>
<li>]</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>x] # 6820 - <a href="/view/task?id=6820" target="_blank">CREATE-article# 5543</a> - (this)</li>
<li>[2017-01-11] SRC = HN, (60)&nbsp;<a href="https://news.ycombinator.com/item?id=13373975" target="_blank">comments</a>&nbsp;(26)</li>
</ol>
<h1 style="text-align: center;">&nbsp;</h1>

~ view article ~ Chapter] index FROM [ Book] strategy-software-developer IN [ libraries] technology-developer-software