DOCSLIB.ORG

Beginning .NET Game Programming in En

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Beginning .NET Game Programming in En Beginning .NET Game Programming in en DAVID WELLER, ALEXANDRE SANTOS LOBAo, AND ELLEN HATTON APress Media, LLC Beginning .NET Game Programming in C# Copyright @2004 by David Weller, Alexandre Santos Lobao, and Ellen Hatton Originally published by APress in 2004 All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN 978-1-59059-319-6 ISBN 978-1-4302-0721-4 (eBook) DOI 10.1007/978-1-4302-0721-4 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Technical Reviewers: Andrew Jenks, Kent Sharkey, Tom Miller Editorial Board: Steve Anglin, Dan Appleman, Gary Cornell, James Cox, Tony Davis, John Franklin, Chris Mills, Steve Rycroft, Dominic Shakeshaft, Julian Skinner, Jim Sumser, Karen Watterson, Gavin Wray, John Zukowski Assistant Publisher: Grace Wong Project Manager: Sofia Marchant Copy Editor: Ami Knox Production Manager: Kari Brooks Production Editor: JanetVail Proofreader: Patrick Vincent Compositor: ContentWorks Indexer: Rebecca Plunkett Artist: Kinetic Publishing Services, LLC Cover Designer: Kurt Krames Manufacturing Manager: Tom Debolski The information in this book is distributed on an "as is" basis, without warranty. Although every precaution has been taken in the preparation of this work, neither the author(s) nor Apress shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in this work. Para Ana: Mi esperanza, mi corazon, mi tesoro, mi amiga, mi amor. -David Weller Contents at a Glance Foreword ........................................................... .xi About the Authors ................................................ .xiii About the Technical Reviewers ................................... .xv Credits ........................................................... .xvi Acknowledgments .................................................. .xvii Preface ........................................................... .xix Introduction ...................................................... .xxi Chapter 1 • Nettrix: GDI + and Collision Detection ......... 1 Chapter 2 .Netterpillars: Artificial Intelligence and Sprites ....................................... 65 Chapter 3 Managed DirectX First Steps: Direct3D Basics and DirectX vs. GDI + ...................139 Chapter 4 Space Donuts: Sprites Revisited .............. .207 Chapter 5 Spacewar! ........................................243 Chapter 6 Spacewar3D: Meshes and Buffers and Textures, Oh My! ................................269 Chapter 7 Adding Visual Effects to Spacewar3D ..........325 Epilogue Taking Your Next Steps .........................341 Bonus Chapter Porting • Nettrix to Pocket PC .................349 Appendix A Suggested Reading ...............................369 Appendix B Motivations in Games ...........................373 Appendix C How Do I Make Games? ...........................379 Appendix 0 Guidelines for Developing Successful Games ..389 Index ..............................................................397 v Contents Foreword ........................................................... .xi About the Authors ................................................ .xiii About the Technical Reviewers ................................... .xv Credits ........................................................... .xvi Acknowledgments .................................................. .xvii Preface ........................................................... .xix Introduction ...................................................... .xxi Chapter 1 .Nettrix: GDI+ and Collision Detection .... 1 Basic GDI+ Concepts ................................................2 Performing Graphic Operations with a Graphics Object ...........4 Creating Gradients .................................................. 7 Collision Detection ................................................8 Optimizing the Number of Calculations ...........................17 Extending the Algorithms to Add a Third Dimension ............ .21 The Game Proposal ..................................................23 The Game Project ...................................................24 The Coding Phase .................................................. .30 Final Version: Coding the GameField Class and the Game Engine .................................................51 Adding the Final Touches .........................................59 Summary ............................................................. 63 Acknowledgments ....................................................64 Book Reference .....................................................64 Chapter 2 . Netterpillars: Artificial Intelligence and Sprites ...................... 65 Object-Oriented Programming ......................................66 Artificial Intelligence ........................................... 69 Sprites and Performance Boosting Tricks ........................ 76 The Game Proposal .................................................. 85 The Game Project ................................................... 86 vii Contents The Coding Phase ...................................................99 Adding the Final Touches ........................................134 Summary ............................................................138 Acknowledgments ...................................................138 Chapter 3 Managed DirectX First Steps: Direct3D Basics and DirectX vs. GDI+ .... 139 DirectX Overview ................................................. .140 3-D Coordinate Systems and Projections .........................151 Drawing Primitives and Texture ..................................158 The Application Proposal .........................................166 The Application Project ..........................................166 The Coding Phase ..................................................168 Adding the Final Touches ....................................... .202 More About DirectX and GDI+ .................................... .203 Summary ........................................................... .204 Acknowledgments .................................................. .205 Chapter 4 Space Donuts : Sprites Revisited ........... 207 Spri tes ........................................................... .208 Space Donuts ......................................................223 Summary ............................................................242 Acknowledgments ...................................................242 Chapter 5 Spacewar! ......................................... 243 About Spacewar ....................................................244 Methodology: Challenges of Working with Someone Else's Code ............................................246 Using the Application Wizard ....................................247 Direct Play .......................................................259 Summary ............................................................267 Acknowledgments ...................................................268 Chapter 6 Spacewar3D: Meshes and Buffers and Textures, Oh My! ......................... 269 DirectX Basics: The Application Wizard Revisited ............ .270 Spacewar3D .........................................................282 viii Contents The Game Proposal ................................................282 The Game Proj ect ..................................................283 Summary ............................................................323 Acknowledgments ...................................................323 Chapter 7 Adding Visual Effects to Spacewar3D ...... 325 Point Sprites .....................................................325 Step 10: Adding Thrust Effects to Spacewar3D ..................327 Step 11: Adding Explosion Effects to Spacewar3D ..............335 Step 12: Adding a Shockwave Effect to Spacewar3D .............336 Summary ............................................................338 Epilogue Taking Your Next Steps ......................... 341 Moving On ..........................................................341 Habits to Build ...................................................342 Things We Neglected to Tell you ................................346 Happy Trails ......................................................348 Bonus Chapter Porting . Nettrix to Pocket PC ........ 349 Programming for Mobile Devices ................................ ..350 Running Desktop PC Programs and Operating Systems on Mobile Devices .....................................354 The Game Proposal ................................................355 The Game Project ..................................................355 The Coding Phase ..................................................356 Adding the Final Touches ........................................366 Summary ............................................................367 Appendix A Suggested Reading ............................. 369 Game Programming ..................................................369 Math and Physics ................................................. .370 Computer Graphics ...............................................
Load more

Recommended publications
  • Course 3D MDX: 3D-Graphics with Managed Directx 9.0 Chapter C4: Standard Meshes = Primitives
    1 Course 3D_MDX: 3D-Graphics with Managed DirectX 9.0 Chapter C4: Standard Meshes = Primitives Copyright © by V. Miszalok, last update: 11-08-2006 Project mesh_primitive1 Form1, OnResize, OnTimer Exercises Project mesh_primitive1 Main Menu after starting VS 2005: File → New Project... → Templates: Windows Application Name: mesh_primitive1 → Location: C:\temp → Create directory for solution: switch it off → OK Delete the files Program.cs and Form1.Designer.cs and the content of Form1.cs, as described in the chapters 2DCisC1 to 2DCisC4. If You can't find a Solution Explorer-window, open it via the main menu: View → Solution Explorer. Inside the Solution Explorer-window click the plus-sign in front of mesh_primitive1. A tree opens. Look for the branch "References". Right-click References and left-click Add Reference.... An Add Reference dialog box opens. Scroll down to the component name: Microsoft.DirectX Version 1.0.2902.0. Highlight this reference by a left-click and (holding the Strg-key pressed) two more references: Microsoft.DirectX.Direct3D Version 1.0.2902.0 and Microsoft.DirectX.Direct3DX Version 1.0.2902.0 or 1.0.2903.0 or 1.0.2904.0. Quit the Add Reference dialog box with OK. Check if three references: Microsoft.DirectX and Microsoft.DirectX.Direct3D and Microsoft.DirectX.Direct3DX are now visible inside the Solution Explorer window underneath mesh_primitive1 → References. Form1, OnResize, OnTimer Write the following code to Form1.cs: using System; using System.Windows.Forms; using System.Drawing; using Microsoft.DirectX; using
    [Show full text]
  • DI PROTECT™ Release Notes 16 December 2019
    Release Notes Version 3.0 DI PROTECT™ Release Notes 16 December 2019 © 2019 COPYRIGHT DIGITAL IMMUNITY www.digitalimmunity.com COPYRIGHTS & TRADEMARKS The contents of this document are the ProPerty of Digital Immunity, Inc and are confidential and coPyrighted. Use of the Digital Immunity materials is governed by the license agreement accomPanying the DI Software. Your right to coPy the Digital Immunity Materials and related documentation is limited by coPyright law. Making coPies, adaptations, or comPilation works (excePt coPies for archival PurPoses or as an essential steP in the utilization of the Program in conjunction with the equiPment) without Prior written authorization from Digital Immunity, Inc is Prohibited by law. No distribution of these materials is allowed unless with the exPlicit written consent of Digital Immunity. U.S. Government Restricted Rights (Applicable to U.S. Users Only) Digital Immunity software and documentation is Provided with RESTRICTED RIGHTS. The use, duPlication, or disclosure by the government is subject to restrictions as set forth in Paragraph (c)(l)(ii) of the Rights in Technical Data ComPuter Software clause at DFARS 252.227-7013. The manufacturer of this Software is Digital Immunity, Inc, 60 Mall Road, Suite 309, Burlington, MA 01803. Protected by multiPle Patents. Other Patents Pending. DIGITAL IMMUNITY™ is a registered trademark Protected by trademark laws under U.S. and international law. All other Intellectual brand and Product names are trademarks or registered trademarks of their resPective owners. Product Release: 3.0 Last UPdated: 16 December 2019 © Copyright 2019 by Digital Immunity, Inc. All Rights Reserved DI PROTECT™ Release Notes v3.0 | © 2019 Digital Immunity 1 TABLE OF CONTENTS 1 Introduction ......................................................................................................................
    [Show full text]
  • Development of a Windows Device Driver for the Nintendo Wii Remote Entwicklung Eines Windows Treibers Für Die Nintendo Wii Remote
    Development of a Windows Device Driver for the Nintendo Wii Remote Entwicklung eines Windows Treibers für die Nintendo Wii Remote Julian Löhr School of Informatics SRH Hochschule Heidelberg Heidelberg, Germany [email protected] Abstract—This paper is about the development of a device The Wii Remote uses Bluetooth for its wireless driver for the Nintendo Wii Remote on Windows PC’s. communication and is thereby connectable with a pc[1]. Windows does recognize the Wii Remote as a game controller, Keywords—Windows driver development, Wii Remote, human but as shown in Fig. 1 no inputs are exposed. Therefore it is not interface device, game controller, Bluetooth usable without any third party support. There are various programs to enable the Wii Remote to be used within video I. INTRODUCTION games, but all of them just map the inputs to keyboard keys[2]. Many PC games do support game controllers. The So this is useful for some single-player games, but does not Nintendo Wii Remote is a wireless controller for the Nintendo support analog input[2]. Additionally if multiple controllers are Wii console and the Nintendo Wii U console. It features needed, e.g. for local multiplayer games like FIFA, this several buttons, acceleration sensors and an infrared sensor. solution is not sufficient enough[2]. Furthermore it is possible to expand the controller via an additional port with various attachments. Those attachments So the objective is to develop a device driver to enable it as are, i.e. the Nunchuk, a controller with additional buttons and a native game controller.
    [Show full text]
  • Program Details
    Home Program Hotel Be an Exhibitor Be a Sponsor Review Committee Press Room Past Events Contact Us Program Details Monday, November 3, 2014 08:30-10:00 MORNING TUTORIALS Track 1: An Introduction to Writing Systems & Unicode Presenter: This tutorial will provide you with a good understanding of the many unique characteristics of non-Latin Richard Ishida writing systems, and illustrate the problems involved in implementing such scripts in products. It does not Internationalization provide detailed coding advice, but does provide the essential background information you need to Activity Lead, W3C understand the fundamental issues related to Unicode deployment, across a wide range of scripts. It has proved to be an excellent orientation for newcomers to the conference, providing the background needed to assist understanding of the other talks! The tutorial goes beyond encoding issues to discuss characteristics related to input of ideographs, combining characters, context-dependent shape variation, text direction, vowel signs, ligatures, punctuation, wrapping and editing, font issues, sorting and indexing, keyboards, and more. The concepts are introduced through the use of examples from Chinese, Japanese, Korean, Arabic, Hebrew, Thai, Hindi/Tamil, Russian and Greek. While the tutorial is perfectly accessible to beginners, it has also attracted very good reviews from people at an intermediate and advanced level, due to the breadth of scripts discussed. No prior knowledge is needed. Presenters: Track 2: Localization Workshop Daniel Goldschmidt Two highly experienced industry experts will illuminate the basics of localization for session participants Sr. International over the course of three one-hour blocks. This instruction is particularly oriented to participants who are Program Manager, new to localization.
    [Show full text]
  • (RUNTIME) a Salud Total
    Windows 7 Developer Guide Published October 2008 For more information, press only: Rapid Response Team Waggener Edstrom Worldwide (503) 443-7070 [email protected] Downloaded from www.WillyDev.NET The information contained in this document represents the current view of Microsoft Corp. 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 guide is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY. 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, by any means (electronic, mechanical, photocopying, recording or otherwise), or for any purpose, without the express written permission of Microsoft. 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. 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.
    [Show full text]
  • Course 3D MDX: 3D-Graphics with Managed Directx 9.0 Chapter C2: Cylinder with Directional Light
    1 Course 3D_MDX: 3D-Graphics with Managed DirectX 9.0 Chapter C2: Cylinder with Directional Light Copyright © by V. Miszalok, last update: 26-04-2007 Project lights1 This chapter is a summary of a Direct3D-Tutorial from Microsoft: Tutorial4. You find the tutorial here: C:\DXSDK\Samples\Managed\Direct3D\Tutorials. Main Menu after starting VS 2005: File → New Project... → Templates: Windows Application Name: lights1 → Location: C:\temp → Create directory for solution: switch it off → OK Delete the files Program.cs and Form1.Designer.cs and the content of Form1.cs, as descibed in the chapters 2DCisC1 to 2DCisC4. If You find no Solution Explorer-window, open it via the main menu: View → Solution Explorer. Inside the Solution Explorer-window click the plus-sign in front of lights1. A tree opens. Look for the branch "References". Right-click References and left-click Add Reference.... An Add Reference dialog box opens. Scroll down to the component name: Microsoft.DirectX Version 1.0.2902.0. Highlight this reference by a left-click and (holding the Strg-key pressed) the reference Microsoft.DirectX.Direct3D Version 1.0.2902.0 somewhere below. Quit the Add Reference dialog box with OK. Check if both references Microsoft.DirectX and Microsoft.DirectX.Direct3D are now visible inside the Solution Explorer window underneath lights1 → References. If You use Visual Studio 2005 Professional You should switch off the vexatious automatic format- and indent- mechanism of the code editor before You copy the following code to Form1.cs (otherwise all the code will be reformatted into chaos): 1. Main menu of Visual Studio 2005 Professional: click menu "Tools".
    [Show full text]
  • Marc Eaddy, [email protected], Curriculum Vitae, 2/4
    155 E 49 th Street #6B New York, NY 10017 Marc +1 (212) 593-3583 [email protected] Eaddy www.columbia.edu/~me133 Research Interests I plan to make software easier to develop and maintain by enabling developers to better understand and modularize programs. My primary research area is Software Engineering, focusing on development tools, language design, program analysis, and empirical studies. Education 9/2003–5/2008 PhD in Computer Science, Columbia University, New York, NY GPA: 4.0 Thesis: An Empirical Assessment of the Crosscutting Concern Problem Advisor: Alfred Aho 5/2001 MS in Computer Science, Columbia University, New York, NY GPA: 4.0 4/1995 Dual BS in Electrical Engineering and Computer Science, GPA: 3.1 Florida State University, Tallahassee, FL Research Experience 6/2005–present Research Assistant, Columbia University, Prof. Alfred Aho, New York, NY Performed pioneering research on the crosscutting concern problem, i.e., the inability to effectively modularize the concerns (requirements, features, etc.) of a program. Created model to formalize the problem, methodology and tool (Java, 19,000 lines) for locating code related to a concern, and metrics to quantify the amount of crosscutting. Obtained empirical evidence indicating that as crosscutting increases so do defects. Created tools and language extensions for reducing crosscutting concerns, including Wicca (C#, 37,000 lines), the first dynamic aspect-oriented programming system to support source-level debugging, edit-and-continue, and fine-grained weaving using statement-level annotations. 6/2006–8/2006 Research Intern, Microsoft Research, Programming Languages and Tools Group, Redmond, WA Created program dependency analysis and visualization tool that refactors classes into open classes to eliminate compile-time dependency cycles.
    [Show full text]
  • Summary Both the Desktop Graphics And
    Summary Both the desktop graphics and animated film industries are striving to create spectacular, lifelike worlds. Film quality realism requires complicated per-pixel operations, previously impractical for desktop graphics which must render frames as fast as 60 times per second. The 3D Blaster GeForce2 GTS is the first Graphics Processing Unit (GPU) with the 3D performance and enhanced feature set necessary to approach this distinct level of realism. The 3D Blaster GeForce2 GTS is a State of the Art 3D Graphics Accelerator. The combination between Nvidia’s 2nd Generation Transform & Lighting (T&L) Architecture and the Nvidia Shading Rasterizer (NSR) produces one of the most stunning and realistic visuals ever seen on screen. The integrated NSR makes advanced per-pixel shading capabilities possible. This breakthrough technology has the ability to process seven pixel operations in a single pass on each of four pixel pipelines, simultaneously. The end result of this is to allow individual pixel control of colour, shadow, light, reflectivity, emissivity, specularity, loss, dirt, and other visual and material components used to create amazingly realistic objects and environments. Per-pixel shading delivers the next-generation of visual realism by going beyond the limited texture mapping techniques of previous graphics processors. • New HyperTexel architecture delivers 1.6 gigatexels per second for staggering frame rates and high- performance anti-aliasing • New NVIDIA Shading Rasterizer (NSR) delivers per pixel shading and lighting for rich,
    [Show full text]
  • 2 - Player Input Handling Csc 165 Computer Game Architecture Overview
    CSc 165 Lecture Notes 2 - Player Input Handling CSc 165 Computer Game Architecture Overview • Device Types • Device Abstractions 2 - Input Handling • Controllers • Input Handling Packages • Event Queues • Input Action Commands (making the inputs do things) 2 CSc 165 Lecture Notes CSc 165 Lecture Notes 2 - Player Input Handling 2 - Player Input Handling Types of Input Devices Input Handling Goals • Keyboard • Steering Wheel Keep games device-independent o Game shouldn’t contain hard-coded device details • Mouse • Dance Pad o Game shouldn’t fail when a particular device is absent • Joystick (“POV”) • Guitar (allow substitution) • “POV Hat Switch” • WiiMote Keep engine device-independent o Engine components should not contain hard-coded • Gamepad • Kinect device details • Paddle • others? … isolate details in an Input Manager 3 4 CSc 165 Lecture Notes CSc 165 Lecture Notes 2 - Player Input Handling 2 - Player Input Handling Device Abstractions “D-pad” (Directional-pad) Axes Two fundamental device types: Discrete axis devices D-pad o Can have either one or two axes . Button – returns pressed or not pressed Frequently represented as 1.0 or 0.0 Single-axis form: one component; U returns one value: L R . Axis – returns a float .25 D Two types of Axis: .125 .375 Dual axis form: two components; each returns a value: . Continuous: returns a value in a range 1.0 0 .5 e.g. { -1 … 1 } or { 0 … 1 } L N R X: . Discrete: returns a value from a set .875 .625 -1 0 +1 e.g. [ 0, 1 ] or [ -1, 0, 1 ] .75 D N U Can be absolute or relative N UL U UR R DR D DL L Y: -1 0 +1 0 .125 .25 .375 .5 .625 .75 .875 1.0 5 6 CSc 165 Lecture Notes CSc 165 Lecture Notes 2 - Player Input Handling 2 - Player Input Handling Controllers Controller Example: GamePad Most “devices” are really collections : o Keyboard: collection of (e.g.
    [Show full text]
  • Windows Presentation Foundation
    1538.book Seite 39 Mittwoch, 9. Juni 2010 4:40 16 Lehnen Sie sich zurück. In diesem Kapitel werden Sie »gebootet«. Nach einem Blick auf die WPF im .NET Framework und einem Schnelldurchlauf durch die Windows- Programmiergeschichte erfahren Sie mehr über die Architektur und Konzepte der WPF. 1 Einführung in die WPF 1.1 Die WPF und das .NET Framework Mit der Windows Presentation Foundation (WPF) steht seit der Einführung des .NET Frameworks 3.0 gegen Ende des Jahres 2006 ein modernes Programmiermodell für die Entwicklung von Windows- und Webbrowser-Anwendungen zur Verfügung. Als Teil des .NET Frameworks ab Version 3.0 ist die WPF Microsofts strategische Plattform für die Entwicklung von Benutzeroberflächen unter Windows. 1.1.1 Die WPF im .NET Framework 3.0 Das Ende 2006 eingeführte .NET Framework 3.0 besteht aus den Komponenten des .NET Frameworks 2.0 und vier umfangreichen Programmiermodellen. Dies sind WPF, Win- dows Communication Foundation (WCF), Windows Workflow Foundation (WF) und Win- dows CardSpace (WCS). Das auf Windows Vista standardmäßig vorinstallierte .NET Framework 3.0 wird auch auf Windows Server 2003 und Windows XP unterstützt (siehe Abbildung 1.1). Mit den vier eingeführten Programmiermodellen WPF, WCF, WF und WCS stellte Microsoft erstmals größere, in Managed Code implementierte Bibliotheken zur Verfügung. Für die Entwick- lung von Benutzeroberflächen unter Windows stellt die WPF das zukünftige Program- miermodell dar. 39 1538.book Seite 40 Mittwoch, 9. Juni 2010 4:40 16 1 Einführung in die WPF .NET Framework 3.0 Windows Windows Windows Windows Presentation Communication Workflow CardSpace Foundation Foundation Foundation (WCS) (WPF) (WCF) (WF) .NET Framework 2.0 Windows ADO.NET ASP.NET ..
    [Show full text]
  • To: Anthonys Darrylr Cc: Cameronm Tonyw Subject: Re: OLE Date: Wed Apt 29 16:48:08 PDT 1992
    2. Maples is really interested in having the Mac presented in a positive light at the conference ( as are we all I think). Can we see a copy of the agenda. I don’t think this warrants specific Mac sessions or anything as detailed as that, just some extension of what we discussed today regarding as proposed time frame foF implementation. Maples was interested in distributing 9ome sort of document that would "commit" us to doing this on the Mac. Do either of you have an opinion on that? If we can’t produce something that is solid in this short ti~e frame, I am in favor of not distributing anything. Random info is clearly not what we need floating around at this point. Please advise on this issue. Thanks, Lisa From greqw Fri Nov 30 10:59:44 1990 To: anthonys darrylr Cc: cameronm tonyw Subject: Re: OLE Date: Wed Apt 29 16:48:08 PDT 1992 Date: Fri Nov 30 11:42:20 1990 I will talk with Tony again. The bottomline was that we were not completely convinced that the API changes would he sufficient and would not require changes later after the initial release of the libraries. Therefore, we did not change the existing APIS. If TonyW did not let PhilipL k~1ow when we made the decision to stay with the existing APIs’, then we screwed up. I am willing to jerk the ISVs around if we can convince ourselves that the link management design will be effective. We do not have much time.
    [Show full text]
  • Microsoft Palladium
    Microsoft Palladium: A Business Overview Combining Microsoft Windows Features, Personal Computing Hardware, and Software Applications for Greater Security, Personal Privacy, and System Integrity by Amy Carroll, Mario Juarez, Julia Polk, Tony Leininger Microsoft Content Security Business Unit June 2002 Legal Notice This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. 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 White Paper 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. 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. 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.
    [Show full text]