Diffsharp an AD Library for .NET Languages
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
IJIRT | Volume 2 Issue 6 | ISSN: 2349-6002
© November 2015 | IJIRT | Volume 2 Issue 6 | ISSN: 2349-6002 .Net Surbhi Bhardwaj Dronacharya College of Engineering Khentawas, Haryana INTRODUCTION as smartphones. Additionally, .NET Micro .NET Framework (pronounced dot net) is Framework is targeted at severely resource- a software framework developed by Microsoft that constrained devices. runs primarily on Microsoft Windows. It includes a large class library known as Framework Class Library (FCL) and provides language WHAT IS THE .NET FRAMEWORK? interoperability(each language can use code written The .NET Framework is a new and revolutionary in other languages) across several programming platform created by Microsoft for languages. Programs written for .NET Framework developingapplications. execute in a software environment (as contrasted to hardware environment), known as Common It is a platform for application developers. Language Runtime (CLR), an application virtual It is a Framework that supports Multiple machine that provides services such as Language and Cross language integration. security, memory management, and exception handling. FCL and CLR together constitute .NET IT has IDE (Integrated Development Framework. Environment). FCL provides user interface, data access, database Framework is a set of utilities or can say connectivity, cryptography, web building blocks of your application system. application development, numeric algorithms, .NET Framework provides GUI in a GUI and network communications. Programmers manner. produce software by combining their own source code with .NET Framework and other libraries. .NET is a platform independent but with .NET Framework is intended to be used by most new help of Mono Compilation System (MCS). applications created for the Windows platform. MCS is a middle level interface. Microsoft also produces an integrated development .NET Framework provides interoperability environment largely for .NET software called Visual between languages i.e. -
Comparative Studies of Programming Languages; Course Lecture Notes
Comparative Studies of Programming Languages, COMP6411 Lecture Notes, Revision 1.9 Joey Paquet Serguei A. Mokhov (Eds.) August 5, 2010 arXiv:1007.2123v6 [cs.PL] 4 Aug 2010 2 Preface Lecture notes for the Comparative Studies of Programming Languages course, COMP6411, taught at the Department of Computer Science and Software Engineering, Faculty of Engineering and Computer Science, Concordia University, Montreal, QC, Canada. These notes include a compiled book of primarily related articles from the Wikipedia, the Free Encyclopedia [24], as well as Comparative Programming Languages book [7] and other resources, including our own. The original notes were compiled by Dr. Paquet [14] 3 4 Contents 1 Brief History and Genealogy of Programming Languages 7 1.1 Introduction . 7 1.1.1 Subreferences . 7 1.2 History . 7 1.2.1 Pre-computer era . 7 1.2.2 Subreferences . 8 1.2.3 Early computer era . 8 1.2.4 Subreferences . 8 1.2.5 Modern/Structured programming languages . 9 1.3 References . 19 2 Programming Paradigms 21 2.1 Introduction . 21 2.2 History . 21 2.2.1 Low-level: binary, assembly . 21 2.2.2 Procedural programming . 22 2.2.3 Object-oriented programming . 23 2.2.4 Declarative programming . 27 3 Program Evaluation 33 3.1 Program analysis and translation phases . 33 3.1.1 Front end . 33 3.1.2 Back end . 34 3.2 Compilation vs. interpretation . 34 3.2.1 Compilation . 34 3.2.2 Interpretation . 36 3.2.3 Subreferences . 37 3.3 Type System . 38 3.3.1 Type checking . 38 3.4 Memory management . -
Introduction to .NET, C#, and Visual Studio
Introduction to .NET, C#, and Visual Studio C# Programming January 8 Part I Administrivia Administrivia • When: Wednesdays 10–11am (and a few Mondays as needed) • Where: Moore 100B • This lab has Windows machines, but feel free to bring laptops • Office Hours: to be announced • Course webpage: http://www.seas.upenn.edu/~cse39905 Course Structure • No quizzes, no exams • Roughly 6 projects • Roughly 2 weeks per project • The final project will be slightly longer and more open-ended • Projects will be due at midnight on the night of the deadline • All assignments should be submitted through the Blackboard Digital Dropbox • Late policy: 15% off each day, up to 3 days late Final Project • Your chance to choose your own project • Brainstorming and planning will begin after spring break • Top projects will be entered into the Xtreme.NET Challenge – hopefully there will be 20 top projects :-) • First prize: Xbox 360! • Judges will include someone from Microsoft recruiting, maybe someone from the C# team • More details to come at http://www.seas.upenn.edu/~cse39905/xtreme Part II What is .NET? The Microsoft .NET Framework • .NET is a development platform that launched in 2000 • Goals include language independence, language integration, web services • Technologies to promote rapid development of secure, connected applications • .NET components include: • Languages (C#, VB, Visual C++, Visual J#, ...) • Common Language Runtime (CLR) • Framework Class Library (FCL) Common Language Runtime • A single runtime environment to execute programs written in any .NET language • Includes a virtual machine • Activates objects, manages memory, performs security checks, collects garbage • To run on the CLR, a language must adhere to a Common Language Specification (CLS) • A language must also build upon base types specified in the Common Type System (CTS) Languages • Language compilers translate source into Microsoft Intermediate Language (MSIL). -
Comparative Studies of Six Programming Languages
Comparative Studies of Six Programming Languages Zakaria Alomari Oualid El Halimi Kaushik Sivaprasad Chitrang Pandit Concordia University Concordia University Concordia University Concordia University Montreal, Canada Montreal, Canada Montreal, Canada Montreal, Canada [email protected] [email protected] [email protected] [email protected] Abstract Comparison of programming languages is a common topic of discussion among software engineers. Multiple programming languages are designed, specified, and implemented every year in order to keep up with the changing programming paradigms, hardware evolution, etc. In this paper we present a comparative study between six programming languages: C++, PHP, C#, Java, Python, VB ; These languages are compared under the characteristics of reusability, reliability, portability, availability of compilers and tools, readability, efficiency, familiarity and expressiveness. 1. Introduction: Programming languages are fascinating and interesting field of study. Computer scientists tend to create new programming language. Thousand different languages have been created in the last few years. Some languages enjoy wide popularity and others introduce new features. Each language has its advantages and drawbacks. The present work provides a comparison of various properties, paradigms, and features used by a couple of popular programming languages: C++, PHP, C#, Java, Python, VB. With these variety of languages and their widespread use, software designer and programmers should to be aware -
NET Framework
.NET Framework #.net 1 1: .NET Framework 2 2 2 . 2 Compact Framework 2 3 Examples 3 C # Hello World 3 Visual Basic .NET Hello World 3 Hello World in F # 4 C ++ / CLI Hello World 4 PowerShell Hello World 4 Nemerle 4 Oxygene 4 Boo Hello World 5 Hello World in Python (IronPython) 5 IL 5 2: .NET 6 6 6 Examples 6 6 3: .NET JSON Newtonsoft.Json 7 7 Examples 7 JSON 7 JSON . 7 4: ADO.NET 8 8 8 Examples 8 SQL 8 - SQL 8 ADO.NET 9 . 10 5: ASP.NET ASP.NET MVC 11 11 Examples 11 11 6: C # SHA1 13 13 Examples 13 # SHA1 13 7: C # SHA1 14 14 Examples 14 # SHA1 14 # 14 8: CLR 15 Examples 15 15 9: DateTime 16 Examples 16 ParseExact 16 TryParse 17 TryParseExact 18 10: HTTP 19 Examples 19 HTTP (HttpListener) 19 HTTP (ASP.NET ) 21 11: HTTP 23 23 Examples 23 System.Net.HttpWebRequest GET 23 System.Net.WebClient GET 23 System.Net.HttpClient GET 24 System.Net.HttpWebRequest POST 24 System.Net.WebClient POST 24 System.Net.HttpClient POST 25 System.Net.Http.HttpClient HTTP 25 12: JIT 27 27 27 Examples 27 27 13: JSON 30 30 Examples 30 System.Web.Script.Serialization.JavaScriptSerializer 30 Json.NET 30 Json.NET 30 - Newtonsoft.Json 31 31 JsonSerializerSettings Json.NET 32 14: LINQ 33 33 33 39 39 ToArray() ToList() ? 39 Examples 39 () 40 () 40 40 OrderByDescending 40 41 41 41 41 () 41 42 42 LastOrDefault 42 SingleOrDefault 42 FirstOrDefault 43 43 44 SelectMany () 44 45 45 45 SequenceEqual 45 46 OfType 46 46 46 46 47 47 GroupBy 47 ToDictionary 48 49 ToArray 49 ToList 49 49 49 ElementAtOrDefault 50 SkipWhile 50 TakeWhile 50 DefaultIfEmpty 50 () 51 51 52 53 54 54 54 55 55 55 15: NuGet 57 57 Examples 57 NuGet 57 UI 58 58 58 59 59 59 (MyGet, Klondike ) 59 UI () Nuget 59 61 16: ReadOnlyCollections 62 62 ReadOnlyCollections ImmutableCollection 62 Examples 62 ReadOnlyCollection 62 62 LINQ 62 62 ReadOnlyCollection 62 : ReadOnlyCollection . -
(Genbinmsil) Via IKVM.Reflection
Emitting binary assemblies (GenBinMSIL) via IKVM.Reflection c Miguel Garcia, LAMP, EPFL http://lamp.epfl.ch/~magarcia October 28th, 2011 Abstract These notes cover the differences between GenMSIL and GenBinMSIL. Both emit semantically the same information (a .Net assembly) however in different formats (textual ILAsm vs. binary). • A big plus of IKVM.Reflection is that it doesn't depend on any of the remaining IKVM libraries (it just depends on System.dll and mscorlib.dll). • The cross-compiler will retain its dependency on ch.epfl.lamp.compiler.msil, but the bootstrapped compiler can have it removed (once TypeParser is updated to use IKVM.Reflection) For now, given that our cus- tom library is working fine, it remains in use in TypeParser in the bootstrapped compiler too. Finally, these notes cover API-diffing tools and future work (emtiting debug-mode assemblies). Contents 1 Differences with GenMSIL 2 1.1 Bug fixes to make peverify happy . .2 1.2 TODO: Pending type discovery of unsigned integers . .2 1.3 TODO: More complete assembly initialization . .2 2 Write your own disassembler 3 3 API-diffing 4 3.1 ApiChange ...............................4 3.2 LibCheck . .4 3.3 Framework Design Studio . .4 4 Future Work: Emitting debug-mode assemblies (A story about csc.exe optimizations and CLR JITing) 5 A Appendix: Limitations of System.Reflection.Emit 5 1 1 Differences with GenMSIL 1.1 Bug fixes to make peverify happy In GenICode: else (from, to) match { case (BYTE, LONG) | (SHORT, LONG) | (CHAR, LONG) | (INT, LONG) => ctx.bb.emit(CALL_PRIMITIVE(Conversion(INT, -
Доповідь Використання Платформи Microsoft .NET Та Мови C# Для
Ⱦɨɩɨɜɿɞɶ ȼɢɤɨɪɢɫɬɚɧɧɹɩɥɚɬɮɨɪɦɢ Microsoft .NET ɬɚɦɨɜɢ C# ɞɥɹ ɧɚɜɱɚɧɧɹɩɪɨɝɪɚɦɭɜɚɧɧɹɜɫɟɪɟɞɧɿɯɡɚɝɚɥɶɧɨɨɫɜɿɬɧɿɯ ɧɚɜɱɚɥɶɧɢɯɡɚɤɥɚɞɚɯ ɒɟɜɱɭɤɉɟɬɪɨȽɟɨɪɝɿɣɨɜɢɱ, ɚɫɩɿɪɚɧɬȱɧɫɬɢɬɭɬɭɿɧɮɨɪɦɚɰɿɣɧɢɯɬɟɯɧɨɥɨɝɿɣɬɚ ɡɚɫɨɛɿɜɧɚɜɱɚɧɧɹȺɤɚɞɟɦɿʀɩɟɞɚɝɨɝɿɱɧɢɯɧɚɭɤɍɤɪɚʀɧɢ Ƚɚɥɭɡɶ ɪɨɡɪɨɛɤɢ ɩɪɨɝɪɚɦɧɨɝɨ ɡɚɛɟɡɩɟɱɟɧɧɹ ɽ ɜɢɡɧɚɱɚɥɶɧɨɸ ɞɥɹ ɪɨɡɜɢɬɤɭ ɿɧɮɨɪɦɚɰɿɣɧɨɝɨ ɫɭɫɩɿɥɶɫɬɜɚ. ɉɪɨɝɪɚɦɭɜɚɧɧɹ ɰɟ ɧɟ ɥɢɲɟɜɢɪɨɛɧɢɰɬɜɨɬɚɧɚɭɤɚɚɣ, ɜɹɤɿɣɫɶɦɿɪɿ, ɫɤɥɚɞɨɜɚɤɭɥɶɬɭɪɢ, ɨɫɜɿɬɢ ɿ ɧɚɜɿɬɶ ɪɿɡɧɨɜɢɞ ɦɢɫɬɟɰɬɜɚ. ȼɚɠɥɢɜɚ ɪɨɥɶ ɜ ɩɿɞɝɨɬɨɜɰɿ ɦɚɣɛɭɬɧɿɯ ɩɪɨɝɪɚɦɿɫɬɿɜ ɧɚɥɟɠɢɬɶ ɫɟɪɟɞɧɿɦ ɡɚɝɚɥɶɧɨɨɫɜɿɬɧɿɦ ɡɚɤɥɚɞɚɦ. ȼɫɭɩɟɪɟɱ ɬɨɦɭ, ɳɨ ɩɪɨɝɪɚɦɭɜɚɧɧɹ ɰɟ ɨɞɢɧ ɡ ɧɚɣɛɿɥɶɲ ɡɚɬɪɟɛɭɜɚɧɢɯ ɜɢɞɿɜ ɥɸɞɫɶɤɨʀ ɞɿɹɥɶɧɨɫɬɿ ɬɚ ɨɞɧɚ ɡ ɧɚɣɰɿɤɚɜɿɲɢɯ ɮɨɪɦ ɬɜɨɪɱɨɫɬɿ ɜ ɨɫɬɚɧɧɿ ɪɨɤɢ ɧɟ ɫɩɨɫɬɟɪɿɝɚɽɬɶɫɹ ɩɿɞɜɢɳɟɧɧɹ ɡɚɰɿɤɚɜɥɟɧɨɫɬɿɞɿɬɟɣɩɪɨɝɪɚɦɭɜɚɧɧɹɦ. ȼɿɪɨɝɿɞɧɨ, ɳɨɨɪɝɚɧɿɡɚɰɿɹɬɚ ɦɟɬɨɞɢɱɧɟ ɡɚɛɟɡɩɟɱɟɧɧɹ ɜɢɜɱɟɧɧɹ ɩɪɨɝɪɚɦɭɜɚɧɧɹ ɫɭɬɬɽɜɨ ɜɿɞɫɬɚɽ ɜɿɞɜɢɦɨɝɱɚɫɭ. Ɋɨɡɜɢɬɨɤ ɨɛɱɢɫɥɸɜɚɥɶɧɨʀ ɬɟɯɧɿɤɢ ɰɟ ɬɚɤɨɠ ɪɨɡɜɢɬɨɤ ɩɪɨɝɪɚɦɧɨɝɨɡɚɛɟɡɩɟɱɟɧɧɹɚɨɬɠɟɿɩɪɨɝɪɚɦɭɜɚɧɧɹ. ɉɨɪɹɞɡ ɫɬɚɧɨɜɥɟɧɧɹɦ ɦɟɬɨɞɿɜ ɩɪɨɝɪɚɦɭɜɚɧɧɹ: ɚɥɝɨɪɢɬɦɿɱɧɟ, ɫɬɪɭɤɬɭɪɧɟ, ɨɛ¶ɽɤɬɧɨɨɪɿɽɧɬɨɜɚɧɟ ɪɨɡɜɢɜɚɸɬɶɫɹ ɿ ɬɟɯɧɨɥɨɝɿʀ ɬɪɚɧɫɥɹɰɿʀ ɤɨɦɩ¶ɸɬɟɪɧɢɯɩɪɨɝɪɚɦ. ɉɟɪɲɿɨɛɱɢɫɥɸɜɚɥɶɧɿɦɚɲɢɧɢɤɟɪɭɜɚɥɢɫɹ ɩɪɨɝɪɚɦɚɦɢ ɪɨɡɪɨɛɥɟɧɢɦɢ ɬɚ ɜɜɟɞɟɧɢɦɢ ɥɸɞɢɧɨɸ ɜ ɦɚɲɢɧɧɢɯ ɤɨɞɚɯ. ɇɚɛɿɪɬɚɤɢɯɤɨɞɿɜɬɚɦɨɜɚɛɟɡɩɨɫɟɪɟɞɧɶɨʀɪɨɛɨɬɢɡɧɢɦɢ - ɚɫɟɦɛɥɟɪ, ɫɩɟɰɢɮɿɱɧɿ ɞɥɹ ɤɨɠɧɨʀ ɧɨɜɨʀ ɚɩɚɪɚɬɧɨʀ ɦɨɞɟɥɿ ɤɨɦɩ¶ɸɬɟɪɿɜ. Ɍɨɛɬɨɩɪɨɝɪɚɦ, ɧɚɜɿɬɶɞɥɹɜɢɪɿɲɟɧɧɹɨɞɧɿɽʀɿɬɿɽʀɠ ɡɚɞɚɱɿ ɞɨɜɨɞɢɥɨɫɶ ɩɢɫɚɬɢ ɫɬɿɥɶɤɢ, ɫɤɿɥɶɤɢ ɛɭɥɨ ɪɿɡɧɢɯ ɦɨɞɟɥɟɣ ɤɨɦɩ¶ɸɬɟɪɿɜ. ɉɨɹɜɚ ɦɨɜ ɩɪɨɝɪɚɦɭɜɚɧɧɹ ɬɚ ʀɯ ɤɨɦɩɿɥɹɬɨɪɿɜ ɞɨɡɜɨɥɢɥɚ, ɲɥɹɯɨɦ ɭɞɨɫɤɨɧɚɥɟɧɧɹ ɤɨɦɩɿɥɹɬɨɪɚ, ɚɞɚɩɬɭɜɚɬɢ ɜɢɤɨɪɢɫɬɚɧɧɹ ɪɨɡɪɨɛɥɟɧɢɯ ɩɪɨɝɪɚɦ -
Syntax-Extending and Type-Reflecting Macros in an Object-Oriented Language
Institute of Computer Science University of Wroc law Syntax-extending and type-reflecting macros in an object-oriented language Master Thesis Wroc law 2005 Kamil Skalski Contents 1 Preface 4 2 Introduction 4 2.1 Taxonomyofmeta-programs. 5 2.2 SubsetofNemerlelanguage . 6 2.2.1 Meta-programming extension . 7 2.3 Features .............................. 8 2.3.1 Syntacticcorrectness . 8 2.3.2 Hygiene .......................... 9 2.3.3 Lexicalscoping . .. .. 10 2.3.4 Syntaxextensions. 12 2.3.5 Typereflection ...................... 12 3 Implementation of core system 13 3.1 Compilerpasses.......................... 14 3.2 Macros............................... 15 3.2.1 SeparateCompilation. 16 3.2.2 Macroexpansion . 16 3.3 Quotations............................. 17 3.4 Hygiene .............................. 18 3.4.1 Formalrewritingrules . 19 3.5 Lexicalscoping .......................... 20 3.5.1 Cross stage persistence of global symbols . 20 4 Partial evaluation 21 4.1 Power function - classical example . 22 4.2 Imperativecodegeneration. 24 4.2.1 Permutationfunction . 25 4.3 Transforming interpreter into compiler . 27 4.3.1 Standardinterpreter . 29 4.3.2 Stagedinterpreter. 30 4.3.3 Frominterpretertocompiler . 31 5 Top level macros 32 5.1 Languageextended withOOcomponents . 33 5.1.1 Stages of class hierarchy building . 34 5.1.2 Changestometa-system . 34 5.2 Implementing design patterns . 36 5.2.1 Proxydesignpattern . 36 2 5.3 Hygieneconsiderations . 38 5.3.1 ’this’reference. 38 5.3.2 Classsymbols ....................... 39 5.3.3 Implementation . 40 5.4 Aspect-Orientedprogramming . 41 6 Syntax extensions 42 6.1 Basesystem............................ 43 6.2 Parsingstages........................... 44 6.3 Deferringparsing ......................... 45 6.4 Extendingtoplevel . .. .. 46 7 Type reflection 47 7.1 Typeinferencealgorithm. -
The Early History of F
The Early History of F# DON SYME, Microsoft, United Kingdom Shepherd: Philip Wadler, University of Edinburgh, UK This paper describes the genesis and early history of the F# programming language. I start with the origins of strongly-typed functional programming (FP) in the 1970s, 80s and 90s. During the same period, Microsoft was founded and grew to dominate the software industry. In 1997, as a response to Java, Microsoft initiated internal projects which eventually became the .NET programming framework and the C# language. From 1997 the worlds of academic functional programming and industry combined at Microsoft Research, Cambridge. The researchers engaged with the company through Project 7, the initial effort to bring multiple languages to .NET, leading to the initiation of .NET Generics in 1998 and F# in 2002. F# was one of several responses by advocates of strongly-typed functional programming to the “object-oriented tidal wave” of the mid-1990s. The 75 development of the core features of F# 1.0 happened from 2004-2007, and I describe the decision-making process that led to the “productization” of F# by Microsoft in 2007-10 and the release of F# 2.0. The origins of F#’s characteristic features are covered: object programming, quotations, statically resolved type parameters, active patterns, computation expressions, async, units-of-measure and type providers. I describe key developments in F# since 2010, including F# 3.0-4.5, and its evolution as an open source, cross-platform language with multiple delivery channels. I conclude by examining some uses of F# and the influence F# has had on other languages so far. -
Porting My Programming Language Onion from Java to Scala
Porting my programming language Onion from Java to Scala Kota Mizushima Some Company in Japan About Myself Name: Kota Mizushima Country: Japan Got Ph.D.in University of Tsukuba Parsing Algorithm Hired by some company (not related to Scala) developing embedded software I'm interested in programming languages Scala, Nemerle, Nice, Haskell, Ruby, and so on Scala-chan and Java-co Mascot characters of Scala and Java in Japan Java-co is a older sister of Scala-chan Introduction to Onion Object oriented and statically typed Closures #(arg: type){/* code */} Delegation Many syntax sugars and simple type inference x.y → x.getY() x = 1 → x: Int = 1 if there is no declaration such as x: Int above Compiled to Java class file Existing Java librarys is available Structure of Onion Compiler LoC: 10000 lines over (was written in Java) Source Parsing Info Typing Generation JavaCC Class File Grammar(.jj) Why Scala? Writing compilers in Java is painful Visitors lacks flexibility No first class function , no pattern matching . etc. Scala is good for writing compilers Pattern matching First class functions and many higher-order methods Algebraic data type by sealed trait + case class → I decided to port my java code to scala code How to port it 1. Create Scala classes for AST nodes 2. Rewrite the grammar( Parsing code) to use the Scala classes 3. Rewrite Info , Typing to use Scala classes 4. Port Java utility classes to Scala classes Used from Info , Typing 5. Port Info , Typing phases 6. Port Generation phase (not completed yet) Problem(1) – object inside object from Java Assume object AST { case object ByteT } Do you have AST.ByteT ? I don't know. -
The .NET Framework: What Is It and How to Use It?
The .NET Framework: What is it and How to Use it? Drs.ir. Vadim V. Zaytsev 19 October 2004 History en Future of Cobol • The lecture in week 45 will be cancelled! • Replacement lecture will take place as a part of a bigger event: • A symposium in honour of Wim Ebbinkhuijsen: 22 October 2004 (Friday), 13:00, Auditorium. Please read information at http://www.automatiseringgids.nl/events/default.asp? page=hfcobol and then register via [email protected] (or contact Ralf). 1 Technical issues • Up-to-date information about the course: requirements, suggestions, slides, papers, rescheduling issues, . — http://www.cs.vu.nl/~ralf/oo/lecture-2004/ • These slides incorporate some of the work by Ralf L¨ammel, Manuel Costa, Kai Rannenberg, Erik Meijer, Damien Watkins, Hanspeter M¨ossenb¨ock & probably some others. 2 What is .NET? • Microsoft .NET is a set of Microsoft software technologies for connecting information, people, systems, and devices. It enables a high level of software integration through the use of Web services—small, discrete, building-block applications that connect to each other as well as to other, larger applications over the Internet. ( c M$ website) • A development platform: interfaces, components and tools to develop software. The biggest change in the Microsoft platform since Windows NT replaced DOS. ( c Manuel Costa) 3 The components of Microsoft .NET- connected software 4 .NET framework principles • Make Internet-scale distributed computing ubiquitous • Seamless integration of multiple applications and devices • Deliver software -
Shared Source CLI 2.0 Internals
Shared Source CLI 2.0 Internals Joel Pobar, Ted Neward with David Stutz and Geoff Shilling Table of Contents PREFACE ..................................................................................................................................................... 1 Who Should Read This Book ..................................................................................................................... 4 How This Book Is Structured ..................................................................................................................... 4 Online CLI Resources ................................................................................................................................ 6 Acknowledgments ...................................................................................................................................... 6 1 INTRODUCING THE CLI COMPONENT MODEL ......................................................................... 9 The CLI Virtual Execution Environment ..................................................................................................10 A CLI Implementation in Shared Source: Rotor .......................................................................................17 2 GETTING STARTED WITH ROTOR ................................................................................................25 A Simple Component Assembly ...............................................................................................................25 Observing Managed Execution .................................................................................................................36