DOCSLIB.ORG

Driver Download Logs Creating a Driver Verification Log

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Driver Download Logs Creating a Driver Verification Log driver download logs Creating a Driver Verification Log. Certain programs of the Windows Hardware Certification Program require a Driver Verification Log (DVL) for all driver submissions. The DVL contains a summary of the results from the Code Analysis (CA), Static Driver Verifier (SDV), and CodeQL log files. The DVL does not contain any source information. You must run the Code Analysis tool and Static Driver Verifier prior to creating a DVL for your driver. To create a driver verification log. Before running the Code Analysis tools, be sure that you can build and link your driver using the latest Windows Driver Kit (WDK). For the Driver Solution, make sure that you have selected a Release configuration as the Solution Configuration and x64 as the Solution Platform. Run Static Driver Verifier. For information about creating the log file, see Creating a log file for Static Driver Verifier and Using Static Driver Verifier to find defects in drivers. Run the Code Analysis tool for drivers. Address and fix any defects that are found. See Creating a log file for the code analysis tool and How to run Code Analysis for Drivers. For more information about code analysis, see Analyzing C/C++ Code Quality by Using Code Analysis. Run CodeQL. Address and fix defects that are found. Certification will fail if defects that are deemed "Must-Fix" are not corrected. For more information about CodeQL and the Static Tools Logo Test, see CodeQL and the Static Tools Logo Test. Create the Driver Verification Log. From the Driver menu, select Create Driver Verification Log. Verify that the Code Analysis Log, Static Driver Verifier Log, and CodeQL Log files are detected. Select Create . The driver verification log has the file name extension .DVL.XML. The log is created in the project folder, for example, \ myDriverProject \ myDriverName .DVL.XML. Note SDV performs a clean rebuild of the driver, which removes the Code Analysis log. As such, please be sure to run SDV before running CA. Note When you are ready to test your driver using the Windows Hardware Lab Kit, you need to copy the driver verification log to the %systemdrive%\DVL directory on the test computer. Be sure to delete the contents of the directory on the test computer before you copy the new driver verification log. Remarks. For the most up-to-date information about the Code Analysis tool, Static Driver Verifier, and the Driver Verification Log, refer to the WDK Release Notes. The Release Notes are available on the Windows Driver Kit (WDK) download page. Important Timeouts, spaceouts, and other non-successful results in the DVL file are acceptable for certification submission. This will not cause the Static Tools test in HLK to fail. You can also create the driver verification log from a Visual Studio Command Prompt window, either by the Visual Studio Native Tools Command Prompt installed with Visual Studio or via the Enterprise Windows Driver Kit (EWDK): Creating a Driver Verification Log Outside of msbuild or Visual Studio. Microsoft ships as part of the Windows Driver Kit (WDK) and Enterprise WDK (eWDK) a component called dvl.exe which can be used to generate Driver Verification Logs (DVLs) via command-line. Starting in WDK/eWDK preview versions 21342 and above, it is possible to generate a DVL from the command line outside of the context of msbuild or Visual Studio. Follow the steps below to create the DVL via command-line: Place the results that need to be consumed to create the DVL in a single directory. Typically for drivers intended to be certified for Windows Client, this is the CodeQL SARIF file. For Windows Server certification, this may also include the Code Analysis and Static Driver Verifier (SDV) results files. Check the WHCP requirements documents for specific details on which tools are required to be run for device driver certification. CodeQL SARIF files and Code Analysis XML files should be placed in the top level of the directory. The SDV DVL.xml file should be placed in a “sdv” subfolder. From the command line, navigate to the top-level directory which contains the CodeQL SARIF file. Locate dvl.exe from the WDK or a mounted eWDK. Call dvl.exe by passing the /manualCreate flag, a driver name, and a desired architecture. For example: One of the following strings should be used for your driverArchitecture string: X86 X64 ARM ARM64. Do not include ".sys" as part of your driverName string. Inspect the generated DVL to ensure that it was generated correctly. This usage is primarily intended for generating DVLs with CodeQL results, but can also be used for SDV and CA results. Databricks - How can I copy driver logs to my machine? I can see logs using %sh command on databricks driver node. How can I copy them on my windows machine for analysis? %sh cd eventlogs/4246832951093966440 gunzip eventlog-2019-07-22--14-00.gz ls -l head -1 eventlog-2019-07-22--14-00 Version":"2.4.0","Timestamp":1563801898572,"Rollover Number":0,"SparkContext Id":4246832951093966440> 1 Answer 1. There are different ways to copy driver logs to your local machine. Option1: Cluster Driver Logs: Go to Azure Databricks Workspace => Select the cluster => Click on Driver Logs => To download to local machine. The direct print and log statements from your notebooks and libraries goes to the driver logs. The logs have three outputs: The log files are rotated periodically. Older log files appear at the top of the page, listed with timestamp information. You can download any of the logs for troubleshooting. Option2: Cluster Log Delivery: When you create a cluster, you can specify a location to deliver Spark driver and worker logs. Logs are delivered every five minutes to your chosen destination. When a cluster is terminated, Databricks guarantees to deliver all logs generated up until the cluster was terminated. The destination of the logs depends on the cluster ID. If the specified destination is dbfs:/cluster-log-delivery, cluster logs for 0630-191345- leap375 are delivered to dbfs:/cluster-log-delivery/0630-191345-leap375. To configure the log delivery location: On the cluster configuration page, click the Advanced Options toggle. At the bottom of the page, click the Logging tab. Select a destination type. Enter the cluster log path. To Download the Cluster Logs to Local Machine: Install the Databricks CLI, configure it with your Databricks credentials, and use the CLI's dbfs cp command. For example: dbfs cp dbfs:/FileStore/azure.txt ./azure.txt. If you want to download an entire folder of files, you can use dbfs cp -r <DBFS Path> <LocalPath> . Open cmd prompt. Install Python: https://www.python.org/downloads/ Install Databricks: pip install databricks-cli. Copy the host and Generated access token. Databricks configure: Run the datbricks configure. Password: paste Access token. Repeat for confirmation: paste Access token. Now Run the below cmdlet to copy logs to local machine. dbfs cp -r dbfs:/cluster-logs/0731-081420-tees851/driver C:\Users\Azure\Desktop\Logs. 50 Printable Driver’s Daily Log Books [Templates & Examples] A drivers daily log is a type of document used to monitor and document the daily trips and activities that drivers do. The types of drivers who use this document are bus drivers, train drivers, company drivers, and taxi drivers. They need to record everything they’re doing to ensure that they’re doing their jobs well. The log will also serve as a basis for the drivers’ salary much like a work log sheet. Table of Contents. Drivers Daily Logs. What does a drivers daily log typically contain? Usually, a drivers daily log contains four major parts which 24 boxes each to represent the number of hours in a day. The four sections represent the shifts of the drivers which are: on-duty (not on the road) driving sleeper off-duty. When filling up the driver log sheet, draw a line across the hours in the proper section which represents your shift for that day. A drivers log book template also includes sections for the name of the driver, the employee number, tractor numbers, shipping numbers, and the number of hours the driver worked from the past week. Driver Log Sheets. Steps to follow when completing the drivers daily log. Drivers should never handle vehicles without enough rest. This can be a very dangerous thing. As a matter of fact, federal laws require tired drivers to stay off the road. The Federal Motor Carrier Safety Administration attempts to ensure that drivers follow these rules by documenting their daily activity on a drivers daily log. Not maintaining an accurate log can result in severe consequences like the driver’s license getting suspended or other penalties. If you want to use the log properly, follow these steps: Before you start driving Layouts of a drivers log book template may vary as long as they all contain the required information. Even before you start driving, you should start filling out the form with the basic information including the name and address of your motor carrier, the number of your truck, any shipping documents and details, and more. While you’re driving As aforementioned, logs have grids which span for 24 hours. You can document all of your activities appropriately. Use the log’s grid to document these activities from the start of your shift to the end. Let’s say that your shift starts at 9 in the morning. At the off-duty section, draw a line from 12:00 midnight to the time you start your shift. Allot at least half an hour before the time of your departure for your pre-trip inspection.
Load more

Recommended publications
  • TK Backman, Jason Yang, SW Development at MS
    T.K. Backman Jason Yang [email protected] [email protected] Principal Development Lead Principal Development Lead Debugging and Tools Group Analysis Technologies Team Windows Engineering Desktop Windows Engineering Desktop Microsoft Corporation Microsoft Corporationnnn Code on a massive scale Developers on a massive scale Tight constraints on schedules University of Washington 3/2/2011 2 ◦ Company structure Why the world is not just about developers ☺ ◦ Innovation strategy How we actually improve software over time ◦ Dynamic tension When people are involved, everything changes ◦ Development cycles How we build software products in cycles ◦ Program analysis How we push quality upstream ◦ Windows engineering system How we build large-scale products University of Washington 3/2/2011 3 ◦ Total size: ~89,000 employees ◦ Windows & Office – “perfect org structure” PM – program managers Dev – software developers Test – software developers in test ◦ Around 1000 PM+Dev+Test feature teams on 100s of products University of Washington 3/2/2011 4 ◦ Team size: ~10,000 employees ◦ Sales & marketing ◦ Project managers / product managers ◦ 30 feature teams 1500 Devs 1500 Testers 1000 PMs ◦ Customer support engineers ◦ Build engineers University of Washington 3/2/2011 5 “I often say that when you can measure what you are speaking about, and express it in numbers, you know something about it; but when you cannot measure it, when you cannot express it in numbers, your knowledge is of a meager and unsatisfactory kind; it may be the beginning
    [Show full text]
  • Scheduling, Thread Context, and IRQL
    Scheduling, Thread Context, and IRQL December 31, 2020 Abstract This paper presents information about how thread scheduling, thread context, and a processor’s current interrupt request level (IRQL) affect the operation of kernel- mode drivers for the Microsoft® Windows® family of operating systems. It is intended to provide driver writers with a greater understanding of the environment in which their code runs. A companion paper, “Locks, Deadlocks, and Synchronization” at http://www.microsoft.com/whdc/hwdev/driver/LOCKS.mspx, builds on these fundamental concepts to address synchronization issues in drivers. Contents Introduction ....................................................................................................................... 3 Thread Scheduling ............................................................................................................ 3 Thread Context and Driver Routines .................................................................................. 4 Driver Threads .................................................................................................................. 5 Interrupt Request Levels .................................................................................................... 6 Processor-Specific and Thread-Specific IRQLs .............................................................. 8 IRQL PASSIVE_LEVEL ............................................................................................ 8 IRQL PASSIVE_LEVEL, in a critical region ..............................................................
    [Show full text]
  • Intel® Quickassist for Windows*
    Intel® QuickAssist for Windows* Release Notes Package Version: QAT1.3.0-0009 April 2020 Revision 003US Document Number: 337758-003US You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com. Intel technologies may require enabled hardware, specific software, or services activation. Check with your system manufacturer or retailer. The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmaps. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Intel does not control or audit third-party benchmark data or the web sites referenced in this document. You should visit the referenced web site and confirm whether referenced data are accurate. Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548-4725 or by visiting www.intel.com/design/literature.htm.
    [Show full text]
  • Run-Commands-Windows-10.Pdf
    Run Commands Windows 10 by Bettertechtips.com Command Action Command Action documents Open Documents Folder devicepairingwizard Device Pairing Wizard videos Open Videos Folder msdt Diagnostics Troubleshooting Wizard downloads Open Downloads Folder tabcal Digitizer Calibration Tool favorites Open Favorites Folder dxdiag DirectX Diagnostic Tool recent Open Recent Folder cleanmgr Disk Cleanup pictures Open Pictures Folder dfrgui Optimie Drive devicepairingwizard Add a new Device diskmgmt.msc Disk Management winver About Windows dialog dpiscaling Display Setting hdwwiz Add Hardware Wizard dccw Display Color Calibration netplwiz User Accounts verifier Driver Verifier Manager azman.msc Authorization Manager utilman Ease of Access Center sdclt Backup and Restore rekeywiz Encryption File System Wizard fsquirt fsquirt eventvwr.msc Event Viewer calc Calculator fxscover Fax Cover Page Editor certmgr.msc Certificates sigverif File Signature Verification systempropertiesperformance Performance Options joy.cpl Game Controllers printui Printer User Interface iexpress IExpress Wizard charmap Character Map iexplore Internet Explorer cttune ClearType text Tuner inetcpl.cpl Internet Properties colorcpl Color Management iscsicpl iSCSI Initiator Configuration Tool cmd Command Prompt lpksetup Language Pack Installer comexp.msc Component Services gpedit.msc Local Group Policy Editor compmgmt.msc Computer Management secpol.msc Local Security Policy: displayswitch Connect to a Projector lusrmgr.msc Local Users and Groups control Control Panel magnify Magnifier
    [Show full text]
  • Unit OS6: Device Management
    Lab Manual - OS6 Device Management Unit OS6: Device Management 6.4. Lab Manual Windows Operating System Internals - by David A. Solomon and Mark E. Russinovich with Andreas Polze 1 Lab Manual - OS6 Device Management Copyright Notice © 2000-2005 David A. Solomon and Mark Russinovich These materials are part of the Windows Operating System Internals Curriculum Development Kit, developed by David A. Solomon and Mark E. Russinovich with Andreas Polze Microsoft has licensed these materials from David Solomon Expert Seminars, Inc. for distribution to academic organizations solely for use in academic environments (and not for commercial use) 2 2 Lab Manual - OS6 Device Management Roadmap for Section 6.4. Lab experiments investigating: Viewing Security Processes Looking at the SAM Viewing Access Tokens Looking at Security Identifiers (SIDs) Viewing a Security Descriptor structure Investigating ordering of Access Control Entries (ACEs) Investigating Privileges 3 This Lab Manual includes experiments investigating the the I/O system mechanisms and concepts implemented inside the Windows operating system. Students are expected to carry out Labs in addition to studying the learning materials in Unit OS6. A thorough understanding of the concepts presented in Unit OS6: Device Management is a prerequisite for these Labs. 3 Lab Manual - OS6 Device Management Lab: Viewing the Installed Driver List View the list of System Drivers in the Software Environment section of the Windows Information utility (Msinfo32.exe) Note: the distinction between File System Drivers and Kernel Drivers is from the Type value in the driver’s Registry key. This distinction is meaningless. 4 Lab objective: Viewing the Loaded Driver List You can see a list of registered drivers on a Windows 2000 system by going to the Drivers section of the Computer Management Microsoft Management Console (MMC) snapin or by right-clicking the My Computer icon on the desktop and selecting Manage from the context menu.
    [Show full text]
  • Windows Kernel Internals II Windows Driver Model University of Tokyo – July 2004*
    Windows Kernel Internals II Windows Driver Model University of Tokyo – July 2004* Dave Probert, Ph.D. Advanced Operating Systems Group Windows Core Operating Systems Division Microsoft Corporation © Microsoft Corporation 2004 1 Windows I/O Model Asychronous, Packet-based, Extensible Device discovery supports plug-and-play — volumes automatically detected and mounted — power management support (ACPI) Drivers attach to per device driver stacks — Drivers can filter actions of other drivers in each stack Integrated kernel support — memory Manager provides DMA support — HAL provides device access, PnP manages device resources — Cache manager provides file-level caching via MM file-mapping Multiple I/O completion mechanisms: —synchronous —update user-mode memory status —signal events —callbacks within initiating thread —reaped by threads waiting on an I/O Completion Port © Microsoft Corporation 2004 2 IO Request Packet (IRP) IO operations encapsulated in IRPs IO requests travel down a driver stack in an IRP Each driver gets an IRP stack location which contains parameters for that IO request IRP has major and minor codes to describe IO operations Major codes include create, read, write, PNP, devioctl, cleanup and close Irps are associated with the thread that made the IO request © Microsoft Corporation 2004 3 Object Relationships Driver Object Device Object Device Device Device Object Object Object Volume Device Object Driver Object File Object File Object © Microsoft Corporation 2004 4 Layering Drivers Device objects attach one on top of another
    [Show full text]
  • Windows Internals, Sixth Edition, Part 2
    spine = 1.2” Part 2 About the Authors Mark Russinovich is a Technical Fellow in ® the Windows Azure™ group at Microsoft. Windows Internals He is coauthor of Windows Sysinternals SIXTH EDITION Administrator’s Reference, co-creator of the Sysinternals tools available from Microsoft Windows ® The definitive guide—fully updated for Windows 7 TechNet, and coauthor of the Windows Internals and Windows Server 2008 R2 book series. Delve inside Windows architecture and internals—and see how core David A. Solomon is coauthor of the Windows Internals book series and has taught components work behind the scenes. Led by a team of internationally his Windows internals class to thousands of renowned internals experts, this classic guide has been fully updated Windows developers and IT professionals worldwide, SIXTH for Windows 7 and Windows Server® 2008 R2—and now presents its including Microsoft staff. He is a regular speaker 6EDITION coverage in two volumes. at Microsoft conferences, including TechNet As always, you get critical, insider perspectives on how Windows and PDC. operates. And through hands-on experiments, you’ll experience its Alex Ionescu is a chief software architect and internal behavior firsthand—knowledge you can apply to improve consultant expert in low-level system software, application design, debugging, system performance, and support. kernel development, security training, and Internals reverse engineering. He teaches Windows internals courses with David Solomon, and is ® In Part 2, you will: active in the security research community.
    [Show full text]
  • Download Windows 10 Iso Preview Can't Leave Insider Program
    download windows 10 iso preview Can't leave insider program. My Acer notebook came with fully licensed Windows 8. I joined the insider program before the release of Windows 10 to preview it. During the previews I had problems, my PC wouldn't boot at one stage and I reset the system which wiped all my drivers and Acer software. Now I am stuck with Windows 10 Home Insider Preview build th2_release 10532 core. I wish to leave the insider program and continue with the release version of Windows 10. Settings>Windows Update>Advanced Options says "We need to restart your PC before you can start getting Insider Builds" but I have repeatedly restarted my PC (both from the Power menu and clicking the "Restart now" button, and this never changes. Get Insider Builds -- Error 0x80070005. Build 10547 is installed on my Surface Pro 2. However, the ADVANCED OPTIONS of UPDATE tells me the error message: "Your Microsoft Account requires attention to get Insider builds." However, when I click on Fix Me, I get "Sorry, something went wrong" and it has the error code 0x80070005. How do I fix my Account? Subscribe Subscribe to RSS feed. Report abuse. Thank you for posting your query in Microsoft Community. Regrets the inconvenience caused. Let us know few things to help you in this regard. Which account are you using to perform this action? Either Local account or Microsoft account? The error code 0x80070005 usually means that you do not have enough permission to perform actions or install updates. Ensure that you have administrative privileges for the account which you're logged in.
    [Show full text]
  • Pdflib Tutorial 9.2.0
    ABC PDFlib, PDFlib+PDI, PPS A library for generating PDF on the fly PDFlib 9.2.0 Tutorial For use with C, C++, COM, Java, .NET, Objective-C, Perl, PHP, Python, RPG, Ruby Copyright © 1997–2019 PDFlib GmbH and Thomas Merz. All rights reserved. PDFlib users are granted permission to reproduce printed or digital copies of this manual for internal use. PDFlib GmbH Franziska-Bilek-Weg 9, 80339 München, Germany www.pdflib.com phone +49 • 89 • 452 33 84-0 If you have questions check the PDFlib mailing list and archive at groups.yahoo.com/neo/groups/pdflib/info Licensing contact: [email protected] Support for commercial PDFlib licensees: [email protected] (please include your license number) This publication and the information herein is furnished as is, is subject to change without notice, and should not be construed as a commitment by PDFlib GmbH. PDFlib GmbH assumes no responsibility or lia- bility for any errors or inaccuracies, makes no warranty of any kind (express, implied or statutory) with re- spect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for par- ticular purposes and noninfringement of third party rights. PDFlib and the PDFlib logo are registered trademarks of PDFlib GmbH. PDFlib licensees are granted the right to use the PDFlib name and logo in their product documentation. However, this is not required. PANTONE® colors displayed in the software application or in the user documentation may not match PANTONE-identified standards. Consult current PANTONE Color Publications for accurate color. PANTONE® and other Pantone, Inc. trademarks are the property of Pantone, Inc.
    [Show full text]
  • Dan's Motorcycle Windows Commands
    1 Complete List of Run Commands in Windows XP, Vista, 7, 8 & 8.1 ¶ People can get stuck if they are attacked with viruses or in any way can’t access different Applications in Windows. Sometimes it gets difficult to find the commands to start the applications directly. Knowing the Run Command for a program in different Windows versions can be very useful. if you’d like to start a program from a script file or if you only have access to a command line interface this can be helpful. For example, If you have Microsoft Word installed (Any version of Microsoft Office®) rather then searching or clicking the start icon, locating the Microsoft Office folder and then clicking the Microsoft Word. You can use the Windows Run Box instead to access the application directly. Just Click Start and Click Run or press "Window Key + R" and type "Winword" and press enter, Microsoft Word will open immediately. Here is a, hopefully, Complete list of RUN Commands in Windows XP, Vista, 7, 8 and 8.1 for your quick and easy access. Description of Applications Run Command 32-bit ODBC driver under 64-bit platform = C:\windows\sysWOW64\ odbcad32.exe 64 bit ODBC driver under 64-bit platform = C:\windows\system32\ odbcad32.exe Accessibility Controls access.cpl Accessibility Options control access.cpl Accessibility Wizard accwiz Copyright © 1999-2016 dansmc.com. All rights reserved. Adapter Troubleshooter (Vista/Win7) AdapterTroubleshooter 2 Add Features to Windows 8 Win8 windowsanytimeupgradeui Add Hardware Wizard Win8 hdwwiz Add New Hardware Wizard hdwwiz.cpl Add/Remove
    [Show full text]
  • License Agreement/Product Use Rights
    Microsoft Volume Licensing License Agreement/Product Use Rights August 2012 Table of Contents INTRODUCTION ..................................................................................... 4 Project 2010 Professional 28 UNIVERSAL LICENSE TERMS .............................................................. 7 Project 2010 Standard 28 Definitions 7 Publisher 2010 29 Your Use Rights 8 Rental Rights for Office 29 Rights to use other versions 8 SharePoint Workspace 2010 29 Third Party Software 9 Streets & Trips 2013 30 Pre-release Code 9 Visio 2010 Premium 30 Updates and Supplements 9 Visio 2010 Professional 30 No Commercial Hosting 9 Visio 2010 Standard 30 Technical Limitations 9 Word 2010 30 Other Rights 9 Word for Mac 2011 30 Documentation 9 DESKTOP OPERATING SYSTEMS (PER COPY PER DEVICE) ......... 31 License Reassignment 9 Windows 8 Professional 32 Product Activation 10 Rental Rights for Windows 33 Additional Functionality 10 SERVERS: PROCESSOR/CAL (PROCESSOR LICENSE + CAL + Using More than One Product or Functionality Together 10 OPTIONAL EXTERNAL CONNECTOR) ............................................... 34 Font Components 11 Windows Server 2012 Datacenter 35 .NET Framework and PowerShell Software 11 Windows Server 2012 Standard 36 Benchmark Testing 11 SERVERS: SERVER / CAL (SERVER LICENSE + CAL + OPTIONAL Products That Include SQL Server Technology 11 EXTERNAL CONNECTOR) .................................................................. 38 SQL Server Reporting Services Map Report Item 11 Bing Maps Server 39 Multiplexing 11 Bing Maps Server with Enhanced Content Pack 40 Management Packs 11 Business Intelligence Appliance 2012 40 Distributable Code 11 Duet Enterprise for Microsoft SharePoint and SAP 1.0 41 Software Plus Services 13 Duet for Microsoft Office and SAP 1.5 41 The following license terms apply to your use of products in the Exchange Server 2007 Standard for Small Business 42 Microsoft Servers licensing models.
    [Show full text]
  • Silverlight Deployment Guide V4
    Silverlight Deployment Guide v4 Microsoft Corporation Published: April 2010 Author: David Tesar Editor: Nick Kramer Abstract This guide helps you to plan and carry out a corporate deployment of Silverlight. The guide describes the system requirements and deployment methods, as well as the techniques to maintain and support Silverlight after deployment. 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 document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, 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. 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]