DOCSLIB.ORG

Deploying .NET Applications Lifecycle Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Deploying .NET Applications Lifecycle Guide Deploying .NET Applications Lifecycle Guide The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This Documentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. This documentation is provided to you as a companion to Microsoft Visual Studio .NET, Visual Basic .NET, Visual C++, Visual C#, Visual J# .NET and/or the Microsoft .NET Framework SDK (any one of these, a “Microsoft Developer Tool”), specifically for your use in conjunction with the distribution or internal deployment of the Microsoft .NET Framework redistributable file (dotnetfx.exe). Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Please refer to the end user license agreement you received with a Microsoft Developer Tool for information regarding distribution or internal deployment of the dotnetfx.exe. © 2003 Microsoft Corporation. All rights reserved. Microsoft, ActiveX, Authenticode, Visual Basic, Visual C#, Visual J#, Visual Studio, Win32, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Contents Chapter 1 Introduction 1 Who Should Read This Guide . 1 Chapter Outlines . 2 Chapter 1: Introduction . 2 Chapter 2: Planning the Deployment of .NET Framework – based Applications . 2 Chapter 3: Implementing the Deployment of .NET Framework – based Applications . 2 Chapter 4: Maintaining .NET Framework – based Applications . 3 What Is Application Deployment? . 3 Microsoft Solutions Framework (MSF) . 3 The Deployment Process . 4 What Are .NET Framework – based Applications? . 7 What Is the .NET Framework? . 7 Common Language Runtime . 7 .NET Framework Class Library. 9 Types of Framework Applications . 9 Windows Forms Smart Client Applications . 10 ASP .NET Applications (Web-based Applications) . 10 XML Web Services . 11 Windows Services . 11 Console Applications . 11 Scripted or Hosted Applications . 12 Where to Deploy the .NET Framework . 12 Clients . 12 Web Servers . 12 Business Logic Servers . 13 .NET Framework to Database Servers . 13 Deploying the .NET Framework . 13 Requirements for Deploying the .NET Framework . 14 Further Requirements for .NET-based Applications . 14 Deploying the .NET Framework . 16 Localized Versions of the .NET Framework . 18 Summary . 19 More Information . 20 iv Contents Chapter 2 Planning the Deployment of .NET Framework-based Applications 21 What to Deploy with the Application . 21 Files and Folders . 21 Assemblies . 28 Installation Components . 35 COM Components . 37 Serviced Components . 39 IIS Settings . 40 Registry Settings . 43 Merge Modules . 43 CAB Files . 44 Localization . 44 Debug Symbols . 45 Choosing a Deployment Strategy . 46 No-Touch Deployment . 47 Windows Installer Package Deployment . 49 Deploying a Simple Collection of Build Outputs . 57 Summary . 62 More Information . 62 Chapter 3 Implementing the Deployment of .NET Framework-based Applications 67 No-Touch Deployment . 67 Security Considerations . 69 Installer Packages . 70 Adding Project Output Groups . 71 Adding Files . 72 Adding Assemblies . 75 Adding COM Components . 76 Adding Security Policy . 77 Managing Merge Modules . 78 Managing CAB Files . 81 Adding Dependencies . 82 Adding Launch Conditions . 83 Adding Registry Settings . 85 Adding File Associations. 86 Setting Project Properties . 86 Adding Custom Actions . 92 Design the User Interface of Windows Installer Files . 100 Building the Installer File . 101 Other Windows Installer Package Considerations . 103 Contents v Collection of Simple Build Objects . ..
Load more

Recommended publications
  • 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]
  • 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]
  • A Programmer's Introduction to Visual Basic.NET
    00 2203-x FM 5/25/01 9:57 AM Page i Dear Reader, I wanted to take this opportunity to explain the rationale behind this book showing up on your shelf for free. Quite some time ago, Sams Publishing determined that the next big thing to hit the programmer/developer community would be Microsoft’s Visual Studio.NET and the .NET Framework. After discussions with many of you, our authors and key Microsoft team members, Sams dedicated itself to a strategy that would support your efforts to learn the .NET Framework as efficiently and as quickly as possible. A Programmer’s Introduction to Visual Basic.NET is the perfect example of how our strong relationship with Microsoft and our dedication to bring- ing you authors who are already respected sources in the community suc- cessfully blend and show that Sams Publishing is the source for .NET learning. Bringing you a Beta2 compliant book by May 2001 was not an easy task. Sams called upon a respected author, Craig Utley, to take on this project. Craig holds a unique place in the VB community where he has been devel- oping in VB since version 1.0. He brings years of experience as a trainer, writer, and speaker to this project and gives you the solid reference you need to make the transition from VB to VB.NET. I hope this book gives you the tools you need to begin to learn VB.NET. I invite your comments and ideas as I work to make Sams the publisher you look to as your .NET learning resource.
    [Show full text]
  • Installation Guide for the XM Scaled Topology a Guide to Installing the Sitecore XM Scaled Topology
    Installation Guide for the XM Scaled Topology A guide to installing the Sitecore XM scaled topology August 31, 2021 Sitecore Experience Platform 9.3.0 Installation Guide for the XM Scaled Topology Table of Contents 1. Choosing a topology .................................................................................................................. 4 1.1. On-premise topology options .............................................................................................. 5 2. Sitecore Installation Framework ................................................................................................. 7 2.1. Set up Sitecore Installation Framework ............................................................................... 7 2.1.1. Install the SIF Module using MyGet ............................................................................... 7 2.1.2. Validate the installation ................................................................................................ 8 2.1.3. Run multiple versions of SIF ......................................................................................... 8 2.1.4. Run a specific version of SIF .......................................................................................... 8 2.2. Install Sitecore Installation Framework manually ................................................................. 9 2.2.1. Unblock a .zip package ................................................................................................. 9 2.2.2. Extract the Sitecore Installation Framework
    [Show full text]
  • An Overview of Security in the .NET Framework
    An Overview of Security in the .NET Framework (also at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/netframesecover.asp, but may be dated) Dr. Demien Watkins, Project 42 Sebastian Lange, Microsoft Corporation January 2002 Summary: The fundamental features in the Microsoft .NET Framework security system are profiled, including the ability to confine code to run in tightly constrained, administrator-defined security contexts for a dynamic download and execution, and remote execution, model. Introduction Security is one of the most important issues to consider when moving from traditional program development, where administrators often install software to a fixed location on a local disk, to an environment that allows for dynamic downloads and execution and even remote execution. To support this model, the Microsoft .NET Framework provides a rich security system, capable of confining code to run in tightly constrained, administrator-defined security contexts. This paper examines some of the fundamental security features in the .NET Framework. Many security models attach security to users and their groups (or roles). This means that users, and all code run on behalf of these users, are either permitted or not permitted to perform operations on critical resources. This is how security is modeled in most operating systems. The .NET Framework provides a developer defined security model called role-based security that functions in a similar vein. Role Based Security’s principal abstractions are Principals and Identity. Additionally, the .NET Framework also provides security on code and this is referred to as code access security (also referred to as evidence-based security).
    [Show full text]
  • Smart Client Architecture and Design Guide
    Smart Client Architecture and Design Guide Foreword by Mark Boulter Smart Client Architecture and Design Guide patterns & practices David Hill, Microsoft Corporation Brenton Webster, Microsoft Corporation Edward A. Jezierski, Microsoft Corporation Srinath Vasireddy, Microsoft Corporation Mo Al-Sabt, Microsoft Corporation Blaine Wastell, Ascentium Corporation Jonathan Rasmusson, ThoughtWorks Paul Gale, ThoughtWorks Paul Slater, Wadeware LLC Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. © 2004 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Active Directory, BizTalk, InfoPath, MSDN, Outlook, Visual Basic, Visual C++, Visual C#, Visual Studio, and Win32 are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
    [Show full text]
  • Method, 365, 376, 383 Activator.Createinstance()
    Index A CreditRisks tables, 854 DBTransaction, 853 Abstract stream members, 765 IDbTransaction interface, 853 Accelerate() method, 365, 376, 383 ProcessCreditRisk(), 855 Activator.CreateInstance() method, 607 Rollback(), 854 Active Data Objects (ADO). see ADO.NET save points, 854 Adaptive rendering, 1396 test, 857 Add() method, 362 data providers AddAsync() method, 1554–1555 application configuration files, 813 AddComplete() method, 705–706 benefit, 802 add_Exploded() method, 377 C# Console Application project, 812 Add() method, 698, 702, 1588 centric namespaces, 806 AddOne() method, 723 core objects, 802 AddPerson(), 401 DBMS, 803 AddWithThreads, 745 factory pattern (see Data provider ADO.NET factory model) AutoLot database creation IDbConnection parameter, 811 adding test records, 818 Microsoft, 804 Customers and Orders tables, 820 Microsoft SQL Server, 813 GetPetName() stored procedure, 819 System.Data.OracleClient.dll, 805 Inventory table creation, 815 third-party, 805 table relationships, in Visual Studio, 822 data readers connected layer of, 801 DbDataReader type, 835 AutoLotDataReader, 830 ExecuteReader(), 835 command objects, 834 multiple result sets, 836 connection objects, 830 Read() method, 835 ConnectionStringBuilder objects, 833 string/int, 835 data reader object, 829 DataSets, 800 Console UI–based front end DataTable, 403 AutoLotCUIClient, 846 disconnected layer, 802 <connectionStrings> element, 847 EF, 802 DeleteCar() method, 850 reusable data access library InsertNewCar() method, 850 AutoLotDAL, 838 ListInventory() method,
    [Show full text]
  • Kapitel 5 Assemblies Und Deployment
    kap5.fm Seite 669 Freitag, 8. März 2002 2:03 14 Kapitel 5 Assemblies und Deployment 5.1 Assemblies in .NET 670 5.2 Konfiguration von .NET Applikationen 698 5.3 Deployment – was ist das? 712 kap5.fm Seite 670 Freitag, 8. März 2002 2:03 14 670 Assemblies in .NET Nachdem die Grundlagen der komponentenorientierten Entwicklung in .NET erläutert worden sind, wird in diesem Kapitel ein genauerer Blick auf die interne Struktur der erzeugten Programme und Bibliotheken geworfen. Dabei wird eben- falls das Deployment behandelt, d.h. wie die geschriebenen .NET-Anwendungen und Komponenten verteilt und installiert werden können. Es wurde bereits erwähnt, dass .NET auch Lösungen für die Versionierungs- und DLL-Konflikte bereithält, die Programmierer, Administrator und Anwender zu gleichen Teilen betreffen. In vorhergehenden Kapiteln wurden die Probleme bereits diskutiert (siehe Kapitel 1 und 3). Hier folgt nun eine detaillierte Erläute- rung dessen, was Assemblies sind, wie sie aufgebaut sind und warum sie gerade so aussehen wie sie aussehen, und wozu sie verwendet werden. 5.1 Assemblies in .NET Egal, welche Projekt-Vorlage benutzt wird, ob nun z.B. ein benutzerdefiniertes Steuerelement, eine Web-Anwendung oder ein Windows-Dienst, beim Kompilie- ren erzeugt ein von der Entwicklungsumgebung aufgerufener und der verwendeten Sprache entsprechender Compiler ein Assembly. Prinzipiell besitzen alle Assemb- lies den gleichen Aufbau, sie unterscheiden sich nur (von der Implementierung einmal abgesehen) in der Dateiendung und dem Vorhandensein und Nicht-Vorhan- densein eines Einsprungpunkts. Assemblies machen das oft zitierte XCopy-Deployment möglich. Bei dieser Art der Verteilung von Applikationen reduziert sich die Installation eines .NET-Programms auf das einfache Kopieren der kompletten Anwendung inklusive aller Verzeichnisse, Unterverzeichnisse, referenzierten Assemblies und externen Ressourcen-Dateien.
    [Show full text]
  • Dot Net Interview Questions
    Dear Friends, Hi I am satish marwat, this documents contains all the important questions that usually asked during the .NET interview, I had downloaded all the material from the Internet from various websites and collected to form a single film, u will find few repeated questions also, all the material are from the various websites, so I had just bind it into a single file. So for any mistake I am not responsible, this is just for the view purpose. My view was only to collect a material to a single file. Please, if u find any mistake in this file, please contact me to my email address [email protected], so that I can able to correct it. ALL THE BEST Thanks Satish J Satish Marwat Dot Net Web Resources [email protected] 1 Page .NET FRAME WORK Introduction 1.1 What is .NET? .NET is a general-purpose software development platform, similar to Java. At its core is a virtual machine that turns intermediate language (IL) into machine code. High-level language compilers for C#, VB.NET and C++ are provided to turn source code into IL. C# is a new programming language, very similar to Java. An extensive class library is included, featuring all the functionality one might expect from a contempory development platform - windows GUI development (Windows Form s), database access (ADO.NET), web development (ASP.NET), web services, XML etc. 1.2 When was .NET announced? Bill Gates delivered a keynote at Forum 2000, held June 22, 2000, outlining the .NET 'vision'. The July 2000 PDC had a number of sessions on .NET technology, and delegates were given CDs containing a pre-release version of the .NET framework/SDK and Visual Studio.NET.
    [Show full text]
  • Shared Add in Extensibility Microsoft Net 2.0 Download
    Shared add in extensibility microsoft net 2.0 download When you use Microsoft Visual Studio to create add-ins, smart documents, or smart tags, you may experience the following symptoms: This problem occurs when you create the add-ins, the smart documents, or the smart tags on a computer that has the Framework Hi, I'm using "Shared Add-in Support Update for Framework KB" as pre-requesites to load some Office plug-ins. This task will uninstall the MSI: Shared Add-in Extensibility Update for Framework (KB). This task was automatically. I uninstalled both 'Shared Add-in Extensibility for ' and 'Shared Add-in Support Update for '. Installing my. NET Framework - FRA * Shared Add-in Extensibility Update for framework (KB) * Shared Add-in Support Update for Uninstall BIP desktop from control->Add or remove programs. 2. Shared Add-in Extensibility Update for Framework (KB) Shared. Learn, Share, Build NET Framework (KB) to the prerequisites list. For the setup bootstrapper being able to download and install the files However, as far as I know, Microsoft doesn't offer these files as an individual download, so you HomeSite="". Module (Shared Add-in Extensibility Update for Framework (KB) v) will be installed. >>> Setup Module Shared Add-In Extensibility Net Framework or later. NET MVC 1 and 2, adding great features that both simplify your code and allow deeper Extensible Scaffolding with MvcScaffold integration. Microsoft NET Framework 4 is Microsoft's comprehensive and consistent SHAREit - Transfer & Share . 7 multi-touch, ribbon controls, taskbar extensibility features, and Surface SDK slow clunky and every upgrade stuff your code and previous created software does not work.
    [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]