DOCSLIB.ORG

1. What Is .NET Framework?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
1. What Is .NET Framework? 1. What is .NET Framework? The .NET Framework is the foundation on which you can design, develop, and deploy applications. t is the core of the .NET infrastructure. t e!ists as a layer "etween the .NET applications and the underlying operating system. The .NET Framework encapsulates much of the "asic functionality, such as de"ugging and security services, which was earlier "uilt into various programming languages. #. What does .NET Framework consists of? The .NET Framework consists of We" forms, Windows forms, and console applications that pertain to the presentation layer of an application. We" forms are used in We"$"ased applications, whereas Windows Forms are used in Windows$"ased applications for providing an interactive user interface. n addition, you can create character$"ased console applications that can "e e!ecuted from the command line. %esides these three components, the .NET Framework consists of two other components, the .NET Framework %ase &lasses and the &ommon Language (untime )&'(). +. Write a note on, a. -rogramming methodologies The .isual /tudio .NET programming methodology allows for mixed$ language programming. This is esta"lished through a &ommon Type /ystem )&T/) that is de0ned for all the languages that .NET Framework supports. 1ll these languages compile into an intermediate language "efore they compile in native code. Therefore, the .NET developer has the independence to code one module of an application in one language and the other module of the same application in another language. ". -latform technologies The .NET Framework includes platform technologies like 1DO.NET, 1/-.NET, and .%.NET. 1DO.NET allows .NET applications to communicate with a data"ase for retrieving, accessing, and updating data. 1/-.NET is a framework for "uilding enterprise-class We" applications. .%.NET is an o"4ect-oriented language that provides features such as a"straction, encapsulation, and polymorphism. %y using these technologies, you can easily develop ro"ust We" applications, Windows applications, and 56L We" services. c. &ode e!ecution The code e!ecution process involves the conversion of ntermediate Language into native or &-7-speci0c code. The &'( is completely architecture$neutral. 1ll the .NET languages get compiled into the L. This intermediate language gets compiled "y Just$in$Time )8 T) compiler into the native machine code. 1fter translating the ' into native code, the converted code is sent to the .NET runtime manager. The .NET runtime manager e!ecutes the code. While e!ecuting the code, a security check is performed to ensure that the code has the appropriate permissions for accessing the availa"le resources 9. Which are the platform technologies supported "y .NET Framework? /ome of the platform technologies supported "y .NET Framework are,n 1DO.NET , 1/-.NET ,.%.NET :. What is "ackward compatibility? %ackward compatibility refers to the a"ility of a technology to work with its previous versions or with other earlier technologies. For e!ample, the 1ctive Directory structure of Windows #;;; is "ackward compatible with Windows NT +.<1 and 9.;. /imilarly, the .NET Framework supports "ackward compatibility. For e!ample, you can compile and run applications created in .isual %asic :.; in .isual /tudio #;;<. =. Does .NET platform support "ackward compatibility? E!plain. The .NET platform supports "ackward compatibility. t is possi"le for an application compiled in one version of the .NET Framework to run on a different version of the .NET Framework. For e!ample, you can run applications developed in .isual /tudio #;;#?#;;+ on .isual /tudio #;;<. n addition to the a"ove e!ample, the .NET platform supports "ackward compatibility in the following ways, The .NET Framework #.; %&L supports "ackward compatibility with the earlier versions. .NET supports &++ "ecause of "ackward compatibility. To run a &++ code on .Net Framework, you need to include the following line at the "eginning of the code, Ausing <mscorli".dll> .% applications can work on .%.NET and 1/- applications can run on 1/-.NET "ecause of "ackward compatibility. Dou can easily reference &36 components in.NET applications. 1. What are the different types of application architectures? Or modi0ed architecture layout.of .NET framework. The different types of application architectures are, /ingle-tier, 1 single application handles all functions related to the user, "usiness, and data service layers. /uch an application is also called a monolithic application. Two$tier, The two$tier architecture divides an application into the following two components, &lient, mplements the user interface /erver, /tores data The "usiness logic can either "e integrated with the client (fat client* or with the server )fat server). Three-tier, n the case of three-tier architecture, all the three service layers reside separately, either on the same machine or on different machines. The user interface interacts with the "usiness logic. The "usiness logic validates the data sent "y the interfaces and forwards it to the data"ase if it conforms to the reEuirements. The front$end only interacts with "usiness logic, which, in turn, interacts with the data"ase. n-tier, 1n n-tier application uses "usiness o"jects for handling "usiness rules and data access. t has multiple servers handling "usiness services. This application architecture provides various advantages over other types of application architectures. /ome of the advantages include e!tensibility, resilience to change, maintaina"ility, and scala"ility of the application <. List the advantages of .NET Framework. The .NET Framework o>ers the following advantages,&onsistent programming model: The "ase classes of the .NET class library provide standard functionality such as, input/output, remoting, thread management, string manipulation, user interface design, and security management. The 1DO.NET classes allow developers to access data in the form of 56L. 56L classes ena"le developers to read, write, manipulate, and transform 56L 0les. The 1/-.NET classes support the development of We"$"ased applications and We" services. The Windows forms classes support the development of desktop$"ased applications. Together, the .NET class li"rary provides a common functionality to all .NET languages resulting in a consistent o"ject model regardless of the programming language used "y the developer. n Language independence, The .NET developer has the independence to code one module of an application in one language and the other module of the same application in another language. This language interopera"ility can help in code reuse, and improve the efficiency of the development process. n Ease of application deployment, The .NET Framework manages the details of locating and loading the components reEuired "y an application, even if several versions of the same application e!ist on the computer. The .NET Framework ensures that all the components on which the application depends are availa"le on the computer "efore the application "egins to run. .isual /tudio #;;< includes a new application deployment technology known as &lickOnce, which allows you to easily deploy a Windows forms application. &lickOnce ena"les you to create desktop applications that are deployed with a secure and system$ controlled installation. n mproved security, The .NET Framework provides several mechanisms for protecting resources and code from unauthorized users, H&ode 1ccess /ecurity )&1/) uses permissions to control the code accessing protected resources and operations. H (ole$"ased security provides information needed to make decisions a"out user permissions. n /upport for We" services, With the advent of .NET technology, We" services provide many "uilt$in %&L facilities that allow different applications from different sources to communicate with each other. We" services do not provide the user with a I7 . We" services instead share "usiness logic, data and processes through a programmatic interface across a network. n Ease of creating dynamic We" content, Dynamic We" content is easier to create with .NET. 1/-. NET #.; includes various features that ena"le you to easily develop We" applications having a consistent layout and appearance. n .isual /tudio .NET, .isual /tudio .NET is the 6icrosoft application and interface for programming in .NET. .isual /tudio .NET provides all the programming advantages mentioned so far. This development environment has an e!tensive set of ready-to use-controls, good de"ugging facilities, easy and simple programming features, and a vast set of .NET "ase classes. 1ll these features ena"le you to develop high performance applications in a short period of time. #. What is the difference "etween a project and a solution? n .isual /tudio .NET, an application can "e made up of one or more items, such as 0les and folders. To organize these items eFciently, .isual /tudio .NET has provided two types of containers, pro4ects and solutions.1 project typically contains items that are interrelated. tems can "e forms, references, and data connections. For e!ample, you may create a pro4ect that contains a form for accepting user details and data"ase connection for transferring these details to a data"ase. 1 project allows you to manage, "uild, and de"ug the items that make up an application. When you "uild a pro4ect, it usually results in the creation of an e!ecuta"le 0le (.e!e) or a dynamic link library ).dll). These 0les that are created as a result of "uilding the pro4ect are called the project output. 1 solution usually acts as a container for one or more pro4ects. For e!ample, you may create a solution containing two projects, one for manipulation of data and the other for generation of reports for the sales division of an organization. Thus, a solution allows you to work on multiple projects within the same instance of the .isual /tudio .NET DE. 1 solution also allows you to specify settings and options that apply to multiple projects. +. What does the .isual /tudio .NET DE provide? The .isual /tudio .NET DE provides you with a common interface for developing various kinds of projects for the .NET Framework.
Load more

Recommended publications
  • C# Programming
    Course 419 C# Programming G419/CN/E.1/609/D.1 © LEARNING TREE INTERNATIONAL, INC. All rights reserved. All trademarked product and company names are the property of their respective trademark holders. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, or translated into any language, without the prior written permission of the publisher. Copying software used in this course is prohibited without the express permission of Learning Tree International, Inc. Making unauthorized copies of such software violates federal copyright law, which includes both civil and criminal penalties. Introduction and Overview Course Objectives In this course, we will discuss the syntax and semantics of C# as • An object-oriented language ◦ Using encapsulation, inheritance, interfaces, realization, polymorphism, associations, and aggregates • A component-oriented language focusing on reuse via the .NET Framework Library, including ◦ Desktop graphical and web-based user interfaces ◦ Enabling cross-language operation ◦ Performing I/O using serial streams and serialization ◦ Interfacing to legacy COM components • A data-oriented language ◦ Using LINQ and the Entity Framework COM = component object model I/O = input/output LINQ = Language Integrated Query © Learning Tree International, Inc. All rights reserved. Not to be reproduced without prior written consent. Intro-2 Course Contents Introduction and Overview Chapter 1 Overview and Development Environment Chapter 2 From Your Language to C# Chapter 3 User Interface Development Chapter 4 Defining User-Written Data Types Chapter 5 The .NET Framework Chapter 6 Interfaces and Polymorphism Chapter 7 Writing .NET Components Chapter 8 Accessing Databases Chapter 9 Other C# Features Chapter 10 Course Summary Next Steps © Learning Tree International, Inc.
    [Show full text]
  • Dot Net Programming CLASS: TYBBA(CA) V SEM (2013 PATTERN)
    DNYANSAGAR ARTS AND COMMERCE COLLEGE, BALEWADI, PUNE – 45 Subject: 503 : Dot Net Programming CLASS: TYBBA(CA) V SEM (2013 PATTERN) Unit 1 :Introduction to .Net Framework Introduction to .NET Framework .NET is a software framework which is designed and developed by Microsoft. The first version of the .Net framework was 1.0 which came in the year 2002. In easy words, it is a virtual machine for compiling and executing programs written in different languages like C#, VB.Net etc. It is used to develop Form-based applications, Web-based applications, and Web services. There is a variety of programming languages available on the .Net platform, VB.Net and C# being the most common ones. It is used to build applications for Windows, phone, web, etc. It provides a lot of functionalities and also supports industry standards. .NET Framework supports more than 60 programming languages in which 11 programming languages are designed and developed by Microsoft. The remaining Non-Microsoft Languages which are supported by .NET Framework but not designed and developed by Microsoft. Common Language Runtime(CLR): CLR is the basic and Virtual Machine component of the .NET Framework. It is the run-time environment in the .NET Framework that runs the codes and helps in making the development process easier by providing the various services such as remoting, thread management, type-safety, memory management, robustness, etc.. Basically, it is responsible for managing the execution of .NET programs regardless of any .NET programming language. It also helps in the management of code, as code that targets the runtime is known as the Managed Code and code doesn’t target to runtime is known as Unmanaged code.
    [Show full text]
  • Interview Questions ASP.NET
    Interview Questions ASP.NET 1. Describe the role of inetinfo.exe, aspnet_isapi.dll andaspnet_wp.exe in the page loading process. inetinfo.exe is theMicrosoft IIS server running, handling ASP.NET requests among other things.When an ASP.NET request is received (usually a file with .aspx extension),the ISAPI filter aspnet_isapi.dll takes care of it by passing the request tothe actual worker process aspnet_wp.exe. 2. What’s the difference between Response.Write() andResponse.Output.Write()? The latter one allows you to write formattedoutput. 3. What methods are fired during the page load? Init() - when the pageis instantiated, Load() - when the page is loaded into server memory,PreRender() - the brief moment before the page is displayed to the user asHTML, Unload() - when page finishes loading. 4. Where does the Web page belong in the .NET Framework class hierarchy? System.Web.UI.Page 5. Where do you store the information about the user’s locale? System.Web.UI.Page.Culture 6. What’s the difference between Codebehind="MyCode.aspx.cs" andSrc="MyCode.aspx.cs"? CodeBehind is relevant to Visual Studio.NET only. 7. What’s a bubbled event? When you have a complex control, like DataGrid, writing an event processing routine for each object (cell, button, row, etc.) is quite tedious. The controls can bubble up their eventhandlers, allowing the main DataGrid event handler to take care of its constituents. 8. Suppose you want a certain ASP.NET function executed on MouseOver overa certain button. Where do you add an event handler? It’s the Attributesproperty, the Add function inside that property.
    [Show full text]
  • Programming with Windows Forms
    A P P E N D I X A ■ ■ ■ Programming with Windows Forms Since the release of the .NET platform (circa 2001), the base class libraries have included a particular API named Windows Forms, represented primarily by the System.Windows.Forms.dll assembly. The Windows Forms toolkit provides the types necessary to build desktop graphical user interfaces (GUIs), create custom controls, manage resources (e.g., string tables and icons), and perform other desktop- centric programming tasks. In addition, a separate API named GDI+ (represented by the System.Drawing.dll assembly) provides additional types that allow programmers to generate 2D graphics, interact with networked printers, and manipulate image data. The Windows Forms (and GDI+) APIs remain alive and well within the .NET 4.0 platform, and they will exist within the base class library for quite some time (arguably forever). However, Microsoft has shipped a brand new GUI toolkit called Windows Presentation Foundation (WPF) since the release of .NET 3.0. As you saw in Chapters 27-31, WPF provides a massive amount of horsepower that you can use to build bleeding-edge user interfaces, and it has become the preferred desktop API for today’s .NET graphical user interfaces. The point of this appendix, however, is to provide a tour of the traditional Windows Forms API. One reason it is helpful to understand the original programming model: you can find many existing Windows Forms applications out there that will need to be maintained for some time to come. Also, many desktop GUIs simply might not require the horsepower offered by WPF.
    [Show full text]
  • Web Technologies-Ii
    $ Edited by: Sarabjit Kumar WEB TECHNOLOGIES-II Edited By Sarabjit Kumar Printed by EXCEL BOOKS PRIVATE LIMITED A-45, Naraina, Phase-I, New Delhi-110028 for Lovely Professional University Phagwara SYLLABUS Web Technologies-II S. No. Topics 1. Making Sense of .NET & Anatomy of an ASP.NET Page: The Microsoft .NET Vision, ASP in NET, Introduction to C#, A Simple Web Page, Adding a Web Control, Introduction to In-Line Script, The Page Class. 2. Server Controls: Postback, Data Binding, Web Server Controls. 3. Server Controls: HTML Server Controls, Validation Controls. 4. Database Access: Error Handling, Database Access Using ADO.NET, Connection, Command, DataAdapter, and DataSet, DataReader, Connection Pooling. 5. Creating More Advanced ASP.NET Pages: Communicating with the Browser, Web.Config. 6. Creating More Advanced ASP.NET Pages: Page Sub-classing, User Controls, More Advanced Data Binding. 7. Applying What We’ve Learned So Far: The Database Model, Creating a Basic Object Model, Creating the User Interface. 8. Web Services: XML Web Services, Uses for Web Services, Web Services in Visual Studio .NET, Creating Web Services, Expanding Web Application with Web Services. 9. Security and Membership: IIS Security, ASP.NET Authentication. Adding E-Commerce Essentials: XML Tools, Freight Calculations, Email. 10. Debugging and Optimization: Debugging in an ASP.NET Application, Optimization, Optimizing Using Caching, Optimizing via Performance Profiling. CONTENT Unit 1: Making Sense of .NET and Anatomy of an ASP.Net Page 1 Kumar Vishal, Lovely
    [Show full text]
  • Appendixes APPENDIX A
    PART 8 Appendixes APPENDIX A COM and .NET Interoperability The goal of this book was to provide you with a solid foundation in the C# language and the core services provided by the .NET platform. I suspect that when you contrast the object model provided by .NET to that of Microsoft’s previous component architecture (COM), you’ll no doubt be con- vinced that these are two entirely unique systems. Regardless of the fact that COM is now considered to be a legacy framework, you may have existing COM-based systems that you would like to inte- grate into your new .NET applications. Thankfully, the .NET platform provides various types, tools, and namespaces that make the process of COM and .NET interoperability quite straightforward. This appendix begins by examin- ing the process of .NET to COM interoperability and the related Runtime Callable Wrapper (RCW). The latter part of this appendix examines the opposite situation: a COM type communicating with a .NET type using a COM Callable Wrapper (CCW). ■Note A full examination of the .NET interoperability layer would require a book unto itself. If you require more details than presented in this appendix, check out my book COM and .NET Interoperability (Apress, 2002). The Scope of .NET Interoperability Recall that when you build assemblies using a .NET-aware compiler, you are creating managed code that can be hosted by the common language runtime (CLR). Managed code offers a number of ben- efits such as automatic memory management, a unified type system (the CTS), self-describing assemblies, and so forth. As you have also seen, .NET assemblies have a particular internal compo- sition.
    [Show full text]
  • Project Files
    APPENDIX A Project Files This Appendix explains which files are created for each project type in Visual Studio .NET 2003 and their various descriptions. First, you'll see the project types and the files created by default with those project types. Then, in the second section, you'll see these various file types explained. Project Types and Their Associated Files Table A-1 presents the project types and their associated files. For an explanation of the file types themselves, please refer to the next section. TableA-1. Project Types Serial References Added Files Created Number Project Type by Default by Wizard 1 Wmdows Application System.dll Assembly Information File: A project for creating an System.Data.dll Assemblyinfo.cs or application with a Wmdows System.Drawing.dll Assemblyinfo.vb user interface. System.Windows.Forms.dll Source Code File: (vb orcs) System.XML.dll Resource File: resx Project me: csproj or vbproj Visual Studio Solution: Sln ICON File: I co (not created for VB) Visual Studio Project User Options: Csproj. user Solution User Options: . suo 2 Class Library System.dll Source Code File: -(vb orcs) A project for creating System.Data.dll Assembly Information File: classes to use in System.XML.dll Assemblyinfo. cs or other applications. Assemblyinfo.vb By default, on creation Project File: csproj or vbproj of a Class Library, a Visual Studio Solution: Sln class is also created Visual Studio Project User for writing code. Options: csproj. user or vbproj . user Solution User Options: . suo Continued 491 492 APPENDIX A- PROJECT FILES Table A-I. Project Types (continued) Serial References Added Files Created Number Project Type by Default by Wizard 3 Windows Control library System.dl Source Code File: (vb orcs) A project for creating System.Data.dll Assembly Information File: controls to use in System.Drawing.dll Assemblylnfo.cs or Windows applications.
    [Show full text]
  • Ultimate C#, .Net Interview Q&AE-Book
    Register your resume: www.terrafirmajobs.com _________________________________________________ www.terrafirmajobs.com Ultimate C#, .Net Interview Q&AE-book Free E-books available with Terra Firma Java Interview Q&A Terra Firma’s Interview Kit Are you stressed at your Desk Restore the rhythm of your life IT Resume writing tips Heart-Care Tips To get these free e-books, email to: [email protected] with the title of the e-book. Copy Right Note You are permitted to freely distribute/print the unmodified version of this issue/e-book/article. We are not attempting to obtain commercial benefit from the valuable work of the authors and the Editor/Publisher claims the ‘fair use’ of copyrighted material. If you think that by publishing a particular material, your copyright has been violated, please let us know. The Editor/Publisher is not responsible for statements or opinions expressed herein nor do such statements necessarily express the views of Editor/Publisher. 1 More Career Tips: http://www.terrafirmajobs.com/ITpros/IT_resources.asp?id=4 ______________________________________________________________________________ Register your resume: www.terrafirmajobs.com _________________________________________________ Index Chapter Name Page 1) C# interview Questions and Answers. 4 1.1) Advance C# interview Questions 2) General Questions 17 2.1 ) General Questions 2.2 ) Methods and Property 2.3) Assembly Questions 2.4) XML Documentation Question 2.5) Debugging and Testing 3) ADO.net and Database Question 26 4) C#, DOT NET, XML, IIS Interview Questions 28 4.1 ) Framework. 4.2 ) COM 4.3 ) OOPS 4.4 ) C# Language Features 4.5 ) Access Specifier 4.6 ) Constructor / Destructor 4.7 ) ADO.net 4.8 ) ASP.net 4.8.1) Session.
    [Show full text]
  • ADO.NET in Disconnected Mode
    C21613753.fm Page 1047 Monday, March 18, 2002 10:58 AM ADO.NET in Disconnected Mode In the preceding chapter, you saw how to work with ADO.NET in connected mode, processing data coming from an active connection and sending SQL commands to one. ADO.NET in connected mode behaves much like classic ADO, even though the names of the involved properties and methods (and their syntax) are often different. You see how ADO.NET differs from its predecessor when you start work- ing in disconnected mode. ADO 2.x permits you to work in disconnected mode using client-side static recordsets opened in optimistic batch update mode. This was one of the great new features of ADO that has proved to be a winner in cli- ent/server applications of any size. As a matter of fact, working in disconnected mode is the most scalable technique you can adopt because it takes resources on the client (instead of on the server) and, above all, it doesn’t enforce any locks on database tables (except for the short-lived locks that are created during the update operation). Note To make code samples in this chapter less verbose, all of them assume that the following Imports statements have been specified at the top of each source file: Imports System.Data Imports System.Data.OleDb Imports System.Data.SqlClient 1047 C21613753.fm Page 1048 Monday, March 18, 2002 10:58 AM 1048 Part V Database Applications The DataSet Object Because ADO.NET (and .NET in general) is all about scalability and perfor- mance, the disconnected mode is the preferred way to code client/server appli- cations.
    [Show full text]
  • Reflection in the .NET Framework
    Mastering C# and .NET Framework Deep dive into C# and .NET architecture to build efficient, powerful applications Marino Posadas BIRMINGHAM - MUMBAI Mastering C# and .NET Framework Copyright © 2016 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: December 2016 Production reference: 1091216 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78588-437-5 www.packtpub.com Credits Author Project Coordinator Marino Posadas Izzat Contractor Reviewers Proofreader Fabio Claudio Ferracchiati Safis Editing Commissioning Editor Indexer Edward Gordon Rekha Nair Acquisition Editor Graphics Denim Pinto Disha Haria Content Development Editor Production Coordinator Priyanka Mehta Aparna Bhagat Technical Editor Cover Work Dhiraj Chandanshive Aparna Bhagat Copy Editor Stuti Srivastava About the Author Marino Posadas is an independent senior trainer, writer, and consultant in Microsoft Technologies and Web Standards.
    [Show full text]
  • Bonus Chapter 14
    BONUS CHAPTER contents foreword xv preface xvii acknowledgments xix about this book xxii PART 1GETTING STARTED......................................... 1 Introducing LINQ 3 1 1.1 What is LINQ? 4 Overview 5 ■ LINQ as a toolset 6 ■ LINQ as language extensions 7 1.2 Why do we need LINQ? 9 Common problems 10 ■ Addressing a paradigm mismatch 12 LINQ to the rescue 18 1.3 Design goals and origins of LINQ 19 The goals of the LINQ project 20 ■ A bit of history 21 1.4 First steps with LINQ to Objects: Querying collections in memory 23 What you need to get started 23 ■ Hello LINQ to Objects 25 vii viii CONTENTS 1.5 First steps with LINQ to XML: Querying XML documents 29 Why we need LINQ to XML 30 ■ Hello LINQ to XML 32 1.6 First steps with LINQ to SQL: Querying relational databases 37 Overview of LINQ to SQL’s features 37 ■ Hello LINQ to SQL 38 ■ A closer look at LINQ to SQL 42 1.7 Summary 42 C# and VB.NET language enhancements 44 2 2.1 Discovering the new language enhancements 45 Generating a list of running processes 46 ■ Grouping results into a class 47 2.2 Implicitly typed local variables 49 Syntax 49 ■ Improving our example using implicitly typed local variables 50 2.3 Object and collection initializers 52 The need for object initializers 52 ■ Collection initializers 53 Improving our example using an object initializer 54 2.4 Lambda expressions 55 A refresher on delegates 56 ■ Anonymous methods 58 ■ Introducing lambda expressions 58 2.5 Extension methods 64 Creating a sample extension method 64 ■ More examples using LINQ’s standard query operators
    [Show full text]
  • I Wanted Was My Data
    Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Developers Print copy available for order. Details at http://devshaped.com/book. Created by Derek Hatchard and Dirk Primbs Edited by Derek Hatchard Comics by Sean Forney Version . Copyright 009 Microsoft Corporation Released under Creative Commons Attribution-Noncommercial-No Derivative Works .0 Contents Preface ����������������������������������������������������������������������������������������������������������������������� 7 Feature Articles 11 Working with Brownfield Code �������������������������������������������������������������������������� Beyond C# and VB ������������������������������������������������������������������������������������������������ 9 Remaining Valuable to Employers ��������������������������������������������������������������������� All I Wanted Was My Data ���������������������������������������������������������������������������������� 9 MAX(output) 41 Efficiency Upgrade ������������������������������������������������������������������������������������������������ Getting Started with Continuous Integration ��������������������������������������������������� 9 On Strike at the Software Factory ����������������������������������������������������������������������� 6 C# Features You Should Be Using ����������������������������������������������������������������������
    [Show full text]