DOCSLIB.ORG

Windows Multi-DBMS Programming

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

• Windows Multi-DBMS Programming Using C++, Visual Basic®, ODBC, OLE2, and Tools for DBMS Projects Ken North John Wiley & Sons, Inc. New York • Chichester • Brisbane • Toronto • Singapore : . ... • - . Contents Preface XXV Chapter 1 Overview and Introduction 1 The Changing Face of Development 2 Overview 2 Required Hardware and Software 3 Chapter 2 Windows Software Development: Concepts and Issues Terms and Concepts 5 Windows Features and Database Applications 7 Processes, Tasks, and Threads 7 Multitasking 8 Protected Addresses and Safe Multitasking 8 Threads: NetWare and Win32 9 Scheduling 9 Windows Programming 10 Static and Dynamic Linking 11 Dynamic Link Libraries 12 INI Files 12 Resources and Help Files 12 Dialog Boxes 13 Custom Controls 14 Notation 14 Windows Developer's Notebook 15 Baselines 15 Version Control 16 Common Development Steps 16 VH viii Contents Pseudocode 17 Debugging 17 Visual Programming 19 Formal Development Methods 19 Crafting Code for Windows 20 GUI Design Considerations and Database Applications 20 Chapter 3 Database Applications: Concepts and Issues 22 Building Database Applications 22 Database Architectures 23 DBMS Evolution 23 ISAM 24 Network and Hierarchical Databases 24 SQL and Relational Databases 25 Desktop, File Server, and Client-Server 29 Terms and Concepts 30 SQL Concepts 38 Database Design 39 Network Database Design 40 Relational Database Design 40 Query Optimization 45 Issues 48 Sample Database and Applications 49 Info Enterprises 49 Sample Applications 50 Road Map for Database Developers 55 Tools for Developing Database Front Ends and Client Applications 56 Chapter 4 Solutions for Multidatabase Programming 57 Terms and Concepts 57 Gateways and Routers 58 Embedded SQL 59 APIs and CLIs 59 Standard Database APIs: A Historical Perspective and Future 60 Open Database Connectivity (ODBC) 61 INTERSOLV/Q+E Database Library 63 Contents ix EDA/CLI 64 Oracle Glue 65 ODBC Drivers 65 • Components and Custom Controls 66 Using Objects to Access Data 66 Data Access Objects 67 Interoperable Objects 67 Late Binding 68 Issues Affecting Interoperability 69 Distributed Objects and Remote Data Access 69 Formulating a Database Development Strategy 70 Chapter 5 Servers and Database Engines 71 SQL Server for Windows NT 72 • SQL Server Tools 74 Transact-SQL 76 Stored Procedures, Triggers, and Rules 78 Preparing for ODBC 80 INI Files 81 Creating Databases and Tables 84 Watcom SQL 91 Locking and Isolation Levels 93 Administering Watcom SQL 93 ODBC Setup 98 Programming Notes 98 Quadbase-SQL 105 VBQUERY 106 Quadbase-SQL XB/Server 107 SQL Scripts 108 Quadbase SQL Command Details 111 Microrim R:BASE and R:BASE SQL Engine 111 R.-BASE Functions 112 Raima Database Server 115 Database Administration 115 Database Navigation 115 • RDSSQL 120 ODBC and Raima SQL Functions 120 x Contents Oprifm'zaft'o« 122 Extension Module Programming 123 Gupta SQLBase 123 Transaction Logs and History Files 124 Configuration File 125 SQLBase Administration and SQLTalk 127 Data Organization 128 Networking, SQLGateway, and SQLRouter 130 SQLBase SQL Notes 130 Optimization, Query Plans, and Indexes 131 Stored Procedures, Triggers, and Events 132 С Programming API 133 Example Database 133 Information Builder's EDA / SQL 141 Programming EDA/SQL 141 Coromandel Integra VDB 143 Visual Data Manager 143 Visual Query Builder 146 Trigger Definition 146 Custom Controls 147 Page Ahead's Simba and ODBC Desktop Databases 155 Desktop Driver Notes 156 Conclusion 159 Chapter 6 Using ODBC 160 Г1*" v wein^ wwww Architecture 161 Components 163 Functions and Features 166 Conformance Levels 166 Relationship to the Windows API 166 Driver Manager Processing 171 Data Types 172 Installation 174 Setup 174 ODBC SDK 174 Files Used with ODBC 175 Contents xi ODBC Administrator 176 Tracing 177 Configuring Data Sources 178 ODBC SQL 184 SQL Extensions 185 Qualifiers, Owners, and Procedures I9l ODBC Programming 192 Handles 192 Options That Govern Behavior 192 Connections 194 Metadata, Catalog Information 196 Statements 197 Cursor Operations 200 Results Processing 201 Termination 204 Typical Processing Sequence 205 Referential Integrity 206 Asynchronous Processing 206 Transaction Processing and Concurrency 206 Cursor Library 208 Translation Libraries 211 Interoperable ODBC Applications 211 Л Fundamental Concept 211 Issues Affecting Interoperability 212 Interrogating for Available Features 217 Interrogating for Available Functions 217 Creating Databases and Tables 219 Interrogating for Available Data Types 219 Developer Guidelines 220 Linker Errors with C++ 221 Debugging and Testing 221 Development and Optimization Hints 223 ODBC or Access Engine ? 224 ODBC as a Tool 225 Why ODBC? 225 Supplemental Information 226 0ШС Benchmark Kit 226 xii Contents Chapter 7 Using INTERSOLV QELIB 228 Installation and Features 228 Multiple Access to Data Sources 229 QELIB Data Types 230 Required ODBC Functions 231 Dates 233 Format Strings 233 Joins 233 Functions 233 Connections and Statements 234 Parameter Queries 235 Transactions 236 Retrieving Data 237 Fetching and Caching Result Sets 238 Column Values Retrieval 239 Metadata and Catalog Functions 240 Column Functions 240 Processing Memo and BLOB Data 241 Modifying Records 241 Уег^гои Information and Initialization 243 £rror Handling and Debugging 243 Query Tools 244 Para'/ig 5ßL 246 ODBC Handle Conversion 246 Date-Time Functions 247 Data Conversion 247 Language Considerations 248 Programming Notes 249 0£L/S and ODBC 249 Portable SQL Functions for QELIB 249 Example Programs 250 T • i /-i ост Typical Query 252 Column Description Information 252 Chapter 8 Data Access and Data Presentation Tools 258 Gupta Quest 259 QuestWindow 260 Contents xiii Queries 260 Aggregate Functions Nonaggregate Functions ZOl Microsoft Excel 271 Setup 272 Accessing Data 272 ODBC Extensions 272 Executing Queries 274 Using Microsoft Query 275 Dynamic Data Exchange (DDE) 277 Microsoft Word for Windows 279 Setup 279 Accessing Databases 280 Executing a Query with Word 280 Using Attached ODBC Tables and Access 280 Word Developer's Kit and WordBasic 283 Using the ODBC Extensions 284 Example Report Macro 285 Mail Merge 287 InfoPublisher 288 Tables 288 Queries 289 InfoPublisher and Databases 290 Crystal Reports for Windows 290 Report Language Functions 291 _ 292 Pro Edition Indexes Report Layout Mode Zyi Print Engine Programming 293 Crystal Reports VBX Properties 298 Example Reports 301 305 Dynamic Queries 305 Form Designer 305 Links to Other Applications 306 Lotus 1-2-3 307 Lotus DataLens 309 DataLens Driver Notes 310 xiv Contents Chapter 9 Rules, Facts, and Objects 312 Asymetrix InfoModeler 312 Views and Modeling a Database 313 FORML 313 Repository, Versions, and Object Reuse 314 Predicates 314 Fact Compiler, Diagrammer, and Table Browser 315 Constraints 316 Mandatory Roles 316 Cardinality 317 Sample Populations 317 Quick Tour 317 Verbalizer and Fact Assistant 319 Driver Notes 320 Example Model 320 InfoEnterprise Tables 321 Using Rules and Databases 322 Rule-based Applications 323 Information Builders' LEVEL 5 OBJECT 323 Actions and RuleTalk 324 Knowledge Base and Inference Engine 325 Editors 325 Actions 327 Using Databases 328 Object Orientation and Object-Oriented Programming 330 Messages, Late Binding, Virtual Methods 332 Data Hiding 333 Object Limitations 335 Conclusion 336 Chapter 10 Tools for Software Developers 337 Developer Tool Roadmap 338 ProtoGen+ Workbench 339 ViewPaint 339 WinControl Library 341 ProtoView Screen Manager 341 Contents xv • SQLView 347 Field Controls 348 Methods 348 SQLView API Error Handling 353 Visual Development Example 353 Proto View's ProtoGen+ 355 Application Regeneration 355 Steps to Creating a User Interface 355 Proto View DataTable 357 Setup 358 Graphics Server SDK and ChartBuilder 358 Charting Features 359 Oracle Glue for Windows 360 Containers 361 Glue Architecture and API 361 Generic Glue DLL 362 SQL Glue Language 363 Palmtop Glue and Wizards 365 Visual Basic Glue Programming 367 WizLink Sample Application 368 Magic Fields 373 Magic Fields API 374 • WindowsMAKER Pro 376 Visual Screen Designer 376 Extended Functionality Modules 376 Quick Look 377 Visual AppBuilder 379 Visual Programming 379 Layout Window 380 Database ALM and the Database Object 382 Browser Object 382 Table Object 383 Other Database ALM Objects •JO.J Using AppBuilder Client-Server ALMs 389 Client-Server Example Program 389 xvi Contents Chapter 11 Client-Server Tool Suites 391 ObjectView 391 Database Interface 393 Visual SQL and Personal SQL 395 Workgroup Library 396 Other Features 397 Command Files 398 Development Cycle 399 Developing with ObjectView 399 ObjectView Scripts 400 Panel Events 401 ObjectView and the TODO List Example Application 402 Gupta SQLWindows 403 Objects and Data Types 404 Messages 405 SQL Programming 406 ReportWindows 408 EditWindows 409 TeamWindows 409 Data Dictionary 411 Creating a PERINFO Data Dictionary Using TeamWindows 412 Template Library 413 QuestWindow Example 413 SQLWindows 5.0 416 Powersoft PowerBuilder 419 Painters 420 PowerScript Programming 425 Libraries, Executables, and INI Files 429 ODBC Interface 430 PowerBuilder and OLE 432 Extending PowerBuilder *? 432 Advanced Developer Toolkit 433 Required Resources 433 Report Generation and PowerViewer 434 Example SQL Scripts 434 Creating a PERSINFO ToDo Example Browser 437 Contents xvii Chapter 12 Client or Client-Server (FoxPro and Access) 442 Microsoft FoxPro for Windows 442 Architecture 443 Screen Builder 443 Menu Builder and Report Writer 443 RQBE 444 Using Index Files 445 Creating FoxPro Tables
Recommended publications
  • Microsoft Macro Assembler Version 5.1.PDF

    Microsoft Macro Assembler Version 5.1.PDF

    Microsoft. Macro Assembler Version 5.1 • For the MS® OS/2 or MS-DOS® Operating System Microsoft Macro Asset bier version 5.1 puts all the speed and power of assembly-lar uage programming within easy reach. Make your programs run faster by linking assembly-language subroutines to your Microsoft QuickBASIC, BASIC compiler, C, FORTRAN, and Pascal programs. Technical Highlights If you're accustomed to programming beyond the level of documentation the correct model for your subroutine, in a high-level language like Microsoft supplied with previous versions of just use the MODEL directive and choose QuickBASIC, BASIC compiler, QuickC, Microsoft Macro Assembler. This totally the model you need. To start your data C, FORTRAN, or Pascal, Microsoft revised guide provides a complete and segment, just add a DATA directive; Macro Assembler version 5.1 is the bridge well-organized explanation of Microsoft to create a stack, add a STACK directive; you've been looking for to the assembly- Macro Assembler and the instruction and to begin writing instructions, use language environment. You can, for sets it supports. the CODE directive. example, use the powerful graphics func- What's more, the Mixed-Language High-level language interface tions of Microsoft QuickBASIC or the Programming Guide included with Micro- macros help you declare your subroutines, efficient math functions of Microsoft soft Macro Assembler version 5.1 con- set up stack parameters, and create local FORTRAN and then add time-critical tains complete, easy-to-follow instructions variables. In addition, version 5.1 offers routines in Microsoft Macro Assembler. on how to call assembly-language sub- MS-DOS interface macros that make it Easier to learn and use.
  • MASM61PROGUIDE.Pdf

    MASM61PROGUIDE.Pdf

    Introduction (C) 1992-1996 Microsoft Corporation. All rights reserved. Programmer's Guide Microsoft® MASM Assembly-Language Development System Version 6.1 For MS-DOS® and Windows™ Operating Systems Microsoft Corporation Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document maybe reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. ©1992 Microsoft Corporation. All rights reserved. Microsoft, MS, MS-DOS, XENIX, CodeView, and QuickC are registered trademarks and Microsoft QuickBasic, QuickPascal, Windows and Windows NT are trademarks of Microsoft Corporation in the USA and other countries. U.S. Patent No. 4,955,066 Hercules is a registered trademark of Hercules Computer Technology. IBM, PS/2, and OS/2 are registered trademarks of International Business Machines Corporation. Intel is a registered trademark of Intel Corporation. NEC and V25 are registered trademarks and V35 is a trademark of NEC Corporation. Document No. DB35747-1292 Printed in the United States of America. Macro Assembler 6.1 (16-bit) - MSDN Archive Edition Page 1 MASM Features New Since Version 5.1 (C) 1992-1996 Microsoft Corporation. All rights reserved. Introduction The Microsoft® Macro Assembler Programmer’s Guide provides the information you need to write and debug assembly-language programs with the Microsoft Macro Assembler (MASM), version 6.1. This book documents enhanced features of the language and the programming environment for MASM 6.1. This Programmer’s Guide is written for experienced programmers who know assembly language and are familiar with an assembler.
  • Chapter 9 Transact-SQL This Chapter Introduces the Many Options

    Chapter 9 Transact-SQL This Chapter Introduces the Many Options

    Transact-SQL Page 1 of 53 Chapter 9 Transact-SQL This chapter introduces the many options available for working with the SQL query language, along with the extensions and special features of Microsoft SQL Server/MSDE’s SQL dialect. The SQL standard was developed by the American National Standards Institute (ANSI) and the International Organization for Standardization (ISO). Today there are several standards whose names include the year in which they were released: SQL-89, SQL-92, and so on. The different standards vary in language functions and performance. Database vendors have fully or partially implemented the SQL standards in their products. Unfortunately, they have not yet agreed on a unified standard. Almost all have added their own extensions to the SQL implementations, so there are some significant differences among the SQL variations of individual products. Microsoft Access 2000 and Microsoft Access 2002 use Jet Engine 3.6—the database core for Access mdb databases—to support SQL-89 Level 1 with several extensions, as well as SQL-92 (albeit not completely) if you are using Jet Engine 4 with the ADO database interface. SQL Server/MSDE supports SQL-92, which for the most part conforms to the ANSI/ISO standard. The SQL language functions consist of two parts: The Data Definition Language (DDL) and the Data Manipulation Language (DML). With DDL, you can create, edit, and delete table structures and define indexes. The DML is used to query data or to edit and delete data. In Access, you usually only work with the DML, as tables and indexes are created with the tools available in Access.
  • Docstar SQL Edition

    Docstar SQL Edition

    DocSTAR SQL Edition Technical Documentation Chapter 1 Requirements ..................... 1-3 Requirements ...................................................1-4 Hardware ........................................................ 1-4 Software .......................................................... 1-4 Chapter 2 Setup.................................. 2-1 General Setup Guidelines .............................2-2 Installation Scenarios ................................... 2-2 Summary of Steps......................................... 2-3 Installation Steps for Scenarios .................. 2-5 DocSTAR Setup Routine ............................ 2-6 Log files.......................................................... 2-7 Individual Setup Steps ...................................2-9 Prepare Existing DocSTAR Host............... 2-9 Setup NT Server............................................ 2-9 Setup SQL Server ....................................... 2-10 Copy existing DocSTAR 2.3 data to new NT server 2-12 Configure SQL Database Structures........ 2-12 Install ODBC Drivers................................. 2-12 Install DocSTAR SE.................................. 2-13 Database Activity (Initialize, Update, or Upsize) 2-19 Restore DocSTAR SE Data on a Bare NT Server 2-25 Final DocSTAR Steps................................ 2-25 Copy Setup Routines to Host.................... 2-26 Manual Processes......................................... 2-29 Manually Configure SQL Database Structures 2-29 Manually Edit Data Source Names.......... 2-34 Convert Jet
  • Programming in Assembler – Laboratory

    Programming in Assembler – Laboratory

    Programming in Assembler – Laboratory Exercise No.1 Installing MASM 6.14 with Programmers Workbench environment During the Exercise No.1 students are to install and configure Microsoft assembler MASM 6.14 with full environment for program writing and debugging. Environment consists of: - The Microsoft Macro Assembler (MASM) - Editor - Debbuger CodeView - A project management („make”) utility - A source-level browser - A complete online reference system All parts of this environment should be installed. They all are intergated with one shell tool - The Programmer’s WorkBench (PWB). To install the MASM 6.14 environment the following are needed: - Instalation version of the MASM 6.11 - Patch to update the MASM 6.11 to 6.14 - Documentation of the environment All needed materials can be accessed from location D:\lab_assembler\ Step by step guide for installation: - Read the documents in Getting Started folder – they describe installation process - Read the packing.txt file – it describes files to be installed - Install the MASM 6.11 running setup.exe from DISK1 folder with default parameters - Refer to documentation for help about installing parameters - Unpack the MASM 6.14 update running the ml614.exe - Refer to documentation in readme.txt file for updating process - Update MASM 6.11 to 6.14 running the patch.exe To run the PWB environment first set the environment variables using the new-vars.bat located in the BINR directory. Now it is possible to correctly run the pwb.exe. After installation test the functions of the tools writing simple assembler program. TITLE HELLO .MODEL small, c, os_dos ; Could be any model except flat .DOSSEG ; Force DOS segment order .STACK .DATA ; Data segment msg BYTE "Hello, world.", 13, 10, "$" .CODE ; Code segment .STARTUP ; Initialize data segment and ; set SS = DS mov ah, 09h ; Request DOS Function 9 mov dx, OFFSET msg ; Load DX with offset of string ; (segment already in DS) int 21h ; Display String to Standard Out .EXIT 0 ; Exit with return code 0 END .
  • Universal Subscription End-User License

    Universal Subscription End-User License

    Universal Subscription End-User License Agreement DEVELOPER EXPRESS INC DEVEXPRESS .NET Controls and Frameworks Copyright (C) 2000-2021 Developer Express Inc. Last revised May, 2021 END-USER LICENSE AGREEMENT FOR ALL SOFTWARE DEVELOPMENT PRODUCT(S) INCLUDED IN THIS DISTRIBUTION IMPORTANT - PLEASE READ THIS END-USER LICENSE AGREEMENT (“AGREEMENT”) CAREFULLY BEFORE DOWNLOADING OR USING THE SOFTWARE DEVELOPMENT PRODUCT(S) INCLUDED IN THIS DISTRIBUTION/INSTALLATION. This Developer Express Inc ("DEVEXPRESS") AGREEMENT constitutes a legally binding agreement between you or the business and/or entity which you represent ("You" or "LICENSEE") and DEVEXPRESS for all DEVEXPRESS products, frameworks, widgets, source code, demos, intermediate files, media, printed materials, and documentation ("SOFTWARE DEVELOPMENT PRODUCT(S)") included in this distribution/installation. By purchasing, installing, copying, or otherwise using the SOFTWARE DEVELOPMENT PRODUCT(S), you acknowledge that you have read this AGREEMENT and you agree to be bound by its terms and conditions. If you are representing a business and/or entity, you acknowledge that you have the legal authority to bind the business and/or entity you are representing to all the terms and conditions of this AGREEMENT. If you do not agree to any of the terms and conditions of this AGREEMENT or if you do not have the legal authority to bind the business and/or entity you are representing to any of the terms and conditions of this AGREEMENT, DO NOT INSTALL, COPY, USE, EVALUATE, OR REPLICATE IN ANY MANNER, ANY PART, FILE OR PORTION OF THE SOFTWARE DEVELOPMENT PRODUCT(S). All SOFTWARE DEVELOPMENT PRODUCT(S) is licensed, not sold. 1. GRANT OF LICENSE.
  • Microsoft Symbol and Type Information Microsoft Symbol and Type Information

    Microsoft Symbol and Type Information Microsoft Symbol and Type Information

    Microsoft Symbol and Type Information Microsoft Symbol and Type Information ii Formats Specification for Windows Tool Interface Standards (TIS) Version 1.0 Microsoft Symbol and Type Information Table of Contents 1. Symbol and Type Information............................................... 1 1.1. Logical Segments .......................................................................................1 1.2. Lexical Scope Linkage ...............................................................................1 1.3. Numeric Leaves .........................................................................................2 1.4. Types Indices .............................................................................................3 1.5. $$SYMBOLS and $$TYPES Definitions...................................................3 $$TYPES Definition.............................................................................................................3 $$SYMBOLS Definition ......................................................................................................4 2. Symbols ................................................................................... 5 2.1. General.......................................................................................................5 Format of Symbol Records .................................................................................................5 Symbol Indices ......................................................................................................................6 2.2. Non-modal
  • Lab # 1 Introduction to Assembly Language

    Lab # 1 Introduction to Assembly Language

    Assembly Language LAB Islamic University – Gaza Engineering Faculty Department of Computer Engineering 2013 ECOM 2125: Assembly Language LAB Eng. Ahmed M. Ayash Lab # 1 Introduction to Assembly Language February 11, 2013 Objective: To be familiar with Assembly Language. 1. Introduction: Machine language (computer's native language) is a system of impartible instructions executed directly by a computer's central processing unit (CPU). Instructions consist of binary code: 1s and 0s Machine language can be made directly from java code using interpreter. The difference between compiling and interpreting is as follows. Compiling translates the high-level code into a target language code as a single unit. Interpreting translates the individual steps in a high-level program one at a time rather than the whole program as a single unit. Each step is executed immediately after it is translated. C, C++ code is executed faster than Java code, because they transferred to assembly language before machine language. 1 Using Visual Studio 2012 to convert C++ program to assembly language: - From File menu >> choose new >> then choose project. Or from the start page choose new project. - Then the new project window will appear, - choose visual C++ and win32 console application - The project name is welcome: This is a C++ Program that print "Welcome all to our assembly Lab 2013” 2 To run the project, do the following two steps in order: 1. From build menu choose build Welcome. 2. From debug menu choose start without debugging. The output is To convert C++ code to Assembly code we follow these steps: 1) 2) 3 3) We will find the Assembly code on the project folder we save in (Visual Studio 2012\Projects\Welcome\Welcome\Debug), named as Welcome.asm Part of the code: 2.
  • Developing Multiuser and Enterprise Applications

    Developing Multiuser and Enterprise Applications

    26_0672329328_ch22.qxd 5/3/07 3:28 PM Page 909 CHAPTER 22 IN THIS CHAPTER . Why This Chapter Is Important Developing Multiuser . Designing Your Application with Multiuser Issues in Mind and Enterprise . Understanding Access’s Applications Locking Mechanisms . Understanding the Client/Server Model . Deciding Whether to Use the Client/Server Model Why This Chapter Is Important . Understanding the Roles That Many people forge right into the application development Access Plays in the Application process with little worry about the scalability of the appli- Design Model cation. Even a simple application that begins as a single- . Learning the Client/Server user application can develop into a multiuser or Buzzwords enterprise-wide application. Unfortunately, the techniques . Upsizing: What to Worry About you can get away with in the single-user application can wreak havoc in a network or client/server environment. It . Proactively Preparing for is therefore necessary to think about the future when you Upsizing design any application. Although the initial development . Using Transaction Processing process might be more complex, if written properly, the . application will survive any growth that it experiences. Practical Examples: Getting Your Application Ready for an This chapter focuses on writing applications that transition Enterprise Environment easily from the single-user environment through the enter- prise client/server environment. Designing Your Application with Multiuser Issues in Mind When you develop applications that multiple users will access over the network, you must make sure they effec- tively handle sharing data and other application objects. Many options are available for developers when they design multiuser applications, and this chapter covers the pros and cons of these options.
  • Migrating ASP to ASP.NET

    Migrating ASP to ASP.NET

    APPENDIX Migrating ASP to ASP.NET IN THIS APPENDIX, we will demonstrate how to migrate an existing ASP web site to ASP.NET, and we will discuss a few of the important choices that you must make during the process. You can also refer to the MSDN documentation at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/ html/cpconmigratingasppagestoasp.asp for more information. If you work in a ColdFusion environment, see http: //msdn. microsoft. com/library I default.asp?url=/library/en-us/dnaspp/html/coldfusiontoaspnet.asp. ASP.NET Improvements The business benefits of creating a web application in ASP.NET include the following: • Speed: Better caching and cache fusion in web farms make ASP.NET 3-5 times faster than ASP. • CompUed execution: No explicit compile step is required to update compo­ nents. ASP.NET automatically detects changes, compiles the files if needed, and readies the compiled results, without the need to restart the server. • Flexible caching: Individual parts of a page, its code, and its data can be cached separately. This improves performance dramatically because repeated requests for data-driven pages no longer require you to query the database on every request. • Web farm session state: ASP.NET session state allows session data to be shared across all machines in a web farm, which enables faster and more efficient caching. • Protection: ASP.NET automatically detects and recovers from errors such as deadlocks and memory leaks. If an old process is tying up a significant amount of resources, ASP.NET can start a new version of the same process and dispose of the old one.
  • Evoluzione Degli Strumenti Di Sviluppo Microsoft

    Evoluzione Degli Strumenti Di Sviluppo Microsoft

    Evoluzione degli strumenti di sviluppo Microsoft Massimo Bonanni Senior Developer @ THAOS s.r.l. [email protected] http://codetailor.blogspot.com http://twitter.com/massimobonanni Agenda • Gli IDE questi sconosciuti • All’inizio era BASIC! • Anni ‘70-’80: compilatori e poco più • Anni ’90: frammentazione degli strumenti di sviluppo • Ultimi 10 anni: l’ecosistema .NET • Conclusioni IDE, questo sconosciuto • IDE è l’acronimo di Integrated Development Environment; • Un insieme di applicazioni (di solito abbastanza complesso) a supporto di chi produce software; • Generalmente consiste di: – Un editor di codice sorgente – Un compilatore e/o interprete – Un debugger – Un tool di building – Vari tools a supporto IDE, questo sconosciuto • Gli IDE possono essere multi-linguaggio o singolo linguaggio; • Alcuni IDE sono espandibili tramite plug-in o estensioni; • Negli ultimi anni gli IDE sono diventati parte di ecosistemi anche molto complessi che contemplano anche gestione del ciclo di vita delle applicazioni; IDE, a cosa serve Lo scopo di un IDE non è banalmente quello di permettere allo sviluppatore di scrivere codice ma dovrebbe permettere allo stesso di aumentare la propria produttività in tutti le fasi della realizzazione di un sistema software. IDE, a cosa serve In sintesi: “At every juncture, advanced tools have been the key to a new wave of applications, and each wave of applications has been key to driving computing to the next level.” Bill Gates La storia di Microsoft Possiamo suddividere l’evoluzione degli strumenti di sviluppo in tre fasi: – Anni ‘70-’80 : poco più che compilatori a riga di comando ed editor di base; – Anni ’90 : primi IDE a finestre (grazie all’arrivo di Windows); – Dal 2000 ad oggi: l’ambiente di sviluppo si trasforma in una vera piattaforma di sviluppo.
  • Ptc Objectada® Version 10.0 Release Announcement

    Ptc Objectada® Version 10.0 Release Announcement

    ptc objectada® for Windows ptc objectada® 64 for Windows Version 10.0 Release Announcement New native Ada compiler release implements Ada 2012 language features and supports Microsoft Visual Studio 2017 and Windows 10 Software Development Kit (SDK) Needham, MA – June 8, 2018 –– PTC (NASDAQ: PTC) today announced the release of version 10.0 of its popular PTC® ObjectAda for Windows and PTC ObjectAda64 for Windows Ada compiler products. This new release introduces support for a substantial initial subset of Ada 2012 language features and support for development of native Windows 32-bit or 64-bit applications using the Microsoft Visual Studio 2017 development tools and libraries from the Windows 10 Software Development Kit (SDK). The Ada 2012 features implemented in this release include the dynamic contracts (preconditions and postconditions for subprograms), aspect specifications, new flexible forms of expressions, and new predefined program library packages. In addition, with this new release, ObjectAda can be configured to use any installation of the Visual Studio 2017 tools and Windows 10 Software Development Kit (SDK), thereby enabling development using the latest releases from Microsoft®. ObjectAda version 10.0 is a major new release incorporating these enhancements: – Compiler, runtime, debugger, and IDE upgrades – New Ada 2012 language support – Ada 95, Ada 2005, and Ada 2012 compiler operation modes – Windows 10 compatibility, also works with Windows 7 or later – Ada bindings to Windows APIs based on Windows 10 SDK – Development using Visual C++ 2017 tools & Windows 10 SDK libraries – Ada Development Toolkit (ADT) Eclipse interface upgrade – works with latest Eclipse versions “ObjectAda for Windows v.10.0 is the first in a series of releases PTC has planned in its phased implementation strategy for Ada 2012 language feature support.” stated Shawn Fanning, Software Development Director at PTC.