DirectX 8 and Visual Basic Development
| Author | : | |
| Rating | : | 4.31 (558 Votes) |
| Asin | : | 0672322250 |
| Format Type | : | paperback |
| Number of Pages | : | 480 Pages |
| Publish Date | : | 2013-02-05 |
| Language | : | English |
DESCRIPTION:
Real world examples explain how to use these tools effectively, professionally, and quickly.. DirectX 8 and Visual Basic Development fills an unmet need in the marketplace as the first book to explain how to use Visual Basic .NET and DirectX 8 to create sophisticated multi-media applications. Topics include networked games, 3D multimedia applications, enable Force Feedback joystick devices in their own applications, multimedia applications that allow for multiple user input devices, and multimedia applications that use music and sound
Topics include networked games, 3D multimedia applications, enable Force Feedback joystick devices in their own applications, multimedia applications that allow for multiple user input devices, and multimedia applications that use music and sound. Real world examples explain how to use these tools effectively, professionally, and quickly. From the Back CoverDirectX 8 and Visual Basic Developmentfills an unmet need in the marketplace as the first book to explain how to use VB.NET and DirectX 8 to create sophisticated multi- media applications.
Essential reading for the VB6->.NET programmer. Keith Sink, DirectX8 and Visual Basic Development (Sams, 2002)It's 2003, now, and the world is slowly migrating to Microsoft's .NET standard (well, those who aren't using Linux, anyway). Here's a prediction, built on past observation of the process: companies who have been developing apps in Visual Basic for years will get copies of VB.NET, expecting a no-brainer transition from one to the other. Their programmers will import the programs, and immediately die of massive aneurysms at seeing the number of errors (especially the number of seemingly unfixable errors, if you . A Customer said Rehash of SDK Documentation. I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information."Rehash of SDK Documentation" according to A Customer. I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the bookRehash of SDK Documentation I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.Rehash of SDK Documentation A Customer I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.4. Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . Key concepts are not extended beyond the SDK examples. This is particularly notable for the DirectRehash of SDK Documentation I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.Rehash of SDK Documentation A Customer I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.4. Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. D section concerning lights, matrices, and vertices.Rehash of SDK Documentation A Customer I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.4. Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . No CD with the bookRehash of SDK Documentation I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.Rehash of SDK Documentation A Customer I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.4. Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . Key concepts are not extended beyond the SDK examples. This is particularly notable for the DirectRehash of SDK Documentation I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.Rehash of SDK Documentation A Customer I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.4. Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. D section concerning lights, matrices, and vertices.Rehash of SDK Documentation A Customer I am disappointed in this book because it is little more than a warmed-over version of the VBSDK for DirectX 8. Here are some specific weaknesses:1. Much of the sample code is taken directly from the SDK samples with little value-added information.2. No CD with the book3. Key concepts are not extended beyond the SDK examples. This is particularly notable for the Direct3D section concerning lights, matrices, and vertices.4. Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. . Many advanced topics are dealt with in an extremely light-weight manner. We are told that matrices are hard to understand and that classes are cool be. Excellent Learning and future reference A Customer I found I was unable to get anywhere with the SDK docs. This book pointed out several errors in the SDK docs as well as a few I was creating. Another thing about this book that differs from the MS SDK, The sample code actually works!!! When a book says something it should be responsable for its content. This book is. Additionally, I liked the .NET sidebars. When is the .NET version of this book comming out?!? I will buy that one too. One other thing that was key in this book, you can use it as a cover to cover read or a straight reference. A short history of computer gra
Keith has been animating and writing video games since the TRS-80 programming days in the early 1980s, and enjoys restoring classic video games. Keith Sink is a Senior Technical Engineer for Capital Stream, a financial software company in Seattle, WA, where he has been involved in the design, development, and architecture of a number of successful applications. Keith has been a prof