ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro

ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro

ePUB Windows Forms Programming in C# MOBI Ü Windows Forms  Ü spectekhnika.pro

❮KINDLE❯ ✽ Windows Forms Programming in C# Author Chris Sells – Spectekhnika.pro As a fairly public figure in the Windows developer community I often get asked if I think thatNET is going to take off I always answer the same thing; it's not a matter of if it's a matter of when MicAs a fairly public figure in the Windows developer community I often get asked if I think thatNET is going to take off I always answer the same thing; it's not a matter of if it's a matter of when Microsoft'sNET Framework has so many benefits that even as a grizzled old CWin32 guy I wasn't able to resist the siren song of a managed development environment It's ironic that the temporary dip in the economy has caused folks to avoid anything new just whenNET comes along to deliver significant reductions in time to market and cost while simultaneously increasing code uality The organizations that have already adoptedNET know that it's going to have a long and happy life especially as it gets pushed further and further into Microsoft's own plans for the future of the Windows platform both on the server and on the client The primary server side technology inNET is ASPNET which provides the infrastructure needed to build web sites and web services ASPNET provides the reach to deploy web sites to anyone by aiming at the baseline of features provided by the middle generation web browsers To provide the highest level of functionality possible ASPNET does most of the work on the server side leaving the client side HTML as a thin wrapper to trigger server side reuests for new pages of data The server side handles practically everything from data manipulation to user preferences to the rendering of simple things like menus and toolbars This model provides the greatest availability across operating systems and browsers If on the other hand your targeted customers are Windows users an HTML based experience limits the users to a lowest common denominator approach that is unnecessary In fact in an attempt to provide a richer client side experience many organizations that know they're targeting Windows users reuire specific versions of Microsoft's Internet Explorer IE web browser However as soon as that happens IE becomes less of a browser andof an HTML based application runtime And for that purpose the HTML object model is fairly primitive often reuiring a lot of work to do things that are normally simple like keeping track of a user's session state If you're going to be targeting Windows users theNET Framework provides a much richer set of objects for building interactive user interfaces This brings me to the subject of this book Windows Forms WinForms WinForms is the face ofNET on the client providing a forms based development environment meant to provide the best of the UI object models that have come before it In addition it provides one feature that no Windows based development framework has provided to date the deployment features of HTML based web applications The ability to combine the richness of Windows applications with the deployment of web applications signals a completely new world for Windows developers; one that makes methan happy to give up the mess of unmanaged code Audience When writing this book I had two target audiences in mind I wanted to provide real world WinForms coverage for both the programmer that had already programmed inNET as well as for the programmer that hadn't Towards that end I do briefly introduce coreNET topics as they come up However theNET Framework itself is a large area that this book doesn't pretend to cover completely Instead when I thinkinformation would be useful to the reader I reference another work that provides the full details In particular I find that I've referenced EssentialNET by Don Box with Chris Sells a great deal making it a good companion to this book In this same category I can also recommend Pragmatic ADONET by Shawn Wildermuth AdvancedNET Remoting by Ingo RammerNET Web Services by Keith Ballinger and Applied MicrosoftNET Framework Programming by Jeffrey Richter Two coreNET topics are of special importance to WinForms programmers and I cover them indetail in Appendix B Delegates and Events and Appendix C Serialization Basics The coverage of delegates and events is particularly important if you're new toNET although I don't recommend diving into that topic until you've got a WinForms specific frame of reference which is provided about 13rd of the way through Chapter 1 Hello Windows Forms I'd like to provide one other note for potential readers Many years ago I wrote my first five day training course The topic was Windows 95 and included a few hours of coverage on the new controls; what they looked like what their properties methods and events were and how to program against them Those hours seemed to take days for both me and for the students The details of a particular control are only interesting when you're putting that control to use and when that time comes the control specific documentation and IntelliSense do a marvelous job of giving you the information you need Towards that end this book covers none of the standard controls completely Instead as each control is interesting the context of the current topic like the DataGrid control in Chapter 13 Data Binding and Data Grids that control is covered appropriately Also Chapter 8 Controls and Chapter 9 Design Time Integration introduces the broad range of categories of controls that WinForms provides including the category of non visual controls called componentsinNET Finally to give you a visual to go with all of the controls and components and to introduce you to the major functionality of each of them Appendix D Standard WinForms Components and Controls provides a list of the standard controls and components I wouldn't think to waste your time by attempting to bethorough that that reference documentation that comes with theNET Framework SDK and Visual StudioNET Instead this book focuses on the real world scenarios that aren't already covered in detail elsewhere Conventions For those of you that have decided to take the plunge with this book I'd like to thank you for your faith and express my hope that I live up to in To aid you in reading the following text I want to let you in on some conventions I use in my writing First and foremost the wonderful thing about WinForms is how visual it is which is why I use a lot of figures to illustrate its features Some of those pictures really need to be color to make the point so be sure to check the color pages at the center of this book for those figures As useful as figures are I think primarily in code Code will be shown in mono faced type SystemConsoleWriteLine Hello WinForms ; Console application activation will also be shown in mono faced type C cscexe hellocs When a part of a code snippet or a command line activation is of particular interest I mark it in bold and often provide a commentNotice the use of theNET System namespaceSystem ConsoleWriteLine Hello WinForms ; When I want to direct your attention to a piece of code evenfully I'll replace superfluous code with ellipses class MyFormSystemWindowsFormsForm fields private void MyFormLoad object sender SystemComponentModelEventArgs eMessageBoxShow Hello from MyForm ; Further to make the printed codereadable I'll often drop namespaces and protection keywords when they don't provide additional informationShortened SystemWindowsFormsForm base class class MyFormForm fieldsRemoved private specifier and SystemComponentModel namespace void MyFormLoad object sender EventArgs eMessageBoxShow Hello from MyForm ;When showingNET attributes I use their full name SerializableAttribute class MyCustomTypeSome languages like C# allow the Attribute suffix to be dropped for convenience but that makes it hard to find the details of the attribute class in the online documentation Also I sometimes take error checking out of the printed code for clarity but try to leave it in the sample code that comes with this bookIn the prose itself I often put a word or phrase in italics to indicate a new term that I'm about to define As an example of this kind of term and its definition hegemony is preponderant influence or authority as well as a useful business practice Finally I often mention keyboard shortcuts because I find them convenient The ones I mention are the default Visual Studio Developer key bindings If you're not using those key bindings you'll need to map the keyboard shortcuts to your own settings Contact The up to date information for this book including the source code and the errata are maintained at This site also provides a way for you to send feedback to me about the book both complimentary and less so 0321116208P05022003.

windows pdf forms book programming ebok Windows Forms book Programming in free Forms Programming in book Windows Forms Programming in C# PDFAs a fairly public figure in the Windows developer community I often get asked if I think thatNET is going to take off I always answer the same thing; it's not a matter of if it's a matter of when Microsoft'sNET Framework has so many benefits that even as a grizzled old CWin32 guy I wasn't able to resist the siren song of a managed development environment It's ironic that the temporary dip in the economy has caused folks to avoid anything new just whenNET comes along to deliver significant reductions in time to market and cost while simultaneously increasing code uality The organizations that have already adoptedNET know that it's going to have a long and happy life especially as it gets pushed further and further into Microsoft's own plans for the future of the Windows platform both on the server and on the client The primary server side technology inNET is ASPNET which provides the infrastructure needed to build web sites and web services ASPNET provides the reach to deploy web sites to anyone by aiming at the baseline of features provided by the middle generation web browsers To provide the highest level of functionality possible ASPNET does most of the work on the server side leaving the client side HTML as a thin wrapper to trigger server side reuests for new pages of data The server side handles practically everything from data manipulation to user preferences to the rendering of simple things like menus and toolbars This model provides the greatest availability across operating systems and browsers If on the other hand your targeted customers are Windows users an HTML based experience limits the users to a lowest common denominator approach that is unnecessary In fact in an attempt to provide a richer client side experience many organizations that know they're targeting Windows users reuire specific versions of Microsoft's Internet Explorer IE web browser However as soon as that happens IE becomes less of a browser andof an HTML based application runtime And for that purpose the HTML object model is fairly primitive often reuiring a lot of work to do things that are normally simple like keeping track of a user's session state If you're going to be targeting Windows users theNET Framework provides a much richer set of objects for building interactive user interfaces This brings me to the subject of this book Windows Forms WinForms WinForms is the face ofNET on the client providing a forms based development environment meant to provide the best of the UI object models that have come before it In addition it provides one feature that no Windows based development framework has provided to date the deployment features of HTML based web applications The ability to combine the richness of Windows applications with the deployment of web applications signals a completely new world for Windows developers; one that makes methan happy to give up the mess of unmanaged code Audience When writing this book I had two target audiences in mind I wanted to provide real world WinForms coverage for both the programmer that had already programmed inNET as well as for the programmer that hadn't Towards that end I do briefly introduce coreNET topics as they come up However theNET Framework itself is a large area that this book doesn't pretend to cover completely Instead when I thinkinformation would be useful to the reader I reference another work that provides the full details In particular I find that I've referenced EssentialNET by Don Box with Chris Sells a great deal making it a good companion to this book In this same category I can also recommend Pragmatic ADONET by Shawn Wildermuth AdvancedNET Remoting by Ingo RammerNET Web Services by Keith Ballinger and Applied MicrosoftNET Framework Programming by Jeffrey Richter Two coreNET topics are of special importance to WinForms programmers and I cover them indetail in Appendix B Delegates and Events and Appendix C Serialization Basics The coverage of delegates and events is particularly important if you're new toNET although I don't recommend diving into that topic until you've got a WinForms specific frame of reference which is provided about 13rd of the way through Chapter 1 Hello Windows Forms I'd like to provide one other note for potential readers Many years ago I wrote my first five day training course The topic was Windows 95 and included a few hours of coverage on the new controls; what they looked like what their properties methods and events were and how to program against them Those hours seemed to take days for both me and for the students The details of a particular control are only interesting when you're putting that control to use and when that time comes the control specific documentation and IntelliSense do a marvelous job of giving you the information you need Towards that end this book covers none of the standard controls completely Instead as each control is interesting the context of the current topic like the DataGrid control in Chapter 13 Data Binding and Data Grids that control is covered appropriately Also Chapter 8 Controls and Chapter 9 Design Time Integration introduces the broad range of categories of controls that WinForms provides including the category of non visual controls called componentsinNET Finally to give you a visual to go with all of the controls and components and to introduce you to the major functionality of each of them Appendix D Standard WinForms Components and Controls provides a list of the standard controls and components I wouldn't think to waste your time by attempting to bethorough that that reference documentation that comes with theNET Framework SDK and Visual StudioNET Instead this book focuses on the real world scenarios that aren't already covered in detail elsewhere Conventions For those of you that have decided to take the plunge with this book I'd like to thank you for your faith and express my hope that I live up to in To aid you in reading the following text I want to let you in on some conventions I use in my writing First and foremost the wonderful thing about WinForms is how visual it is which is why I use a lot of figures to illustrate its features Some of those pictures really need to be color to make the point so be sure to check the color pages at the center of this book for those figures As useful as figures are I think primarily in code Code will be shown in mono faced type SystemConsoleWriteLine Hello WinForms ; Console application activation will also be shown in mono faced type C cscexe hellocs When a part of a code snippet or a command line activation is of particular interest I mark it in bold and often provide a commentNotice the use of theNET System namespaceSystem ConsoleWriteLine Hello WinForms ; When I want to direct your attention to a piece of code evenfully I'll replace superfluous code with ellipses class MyFormSystemWindowsFormsForm fields private void MyFormLoad object sender SystemComponentModelEventArgs eMessageBoxShow Hello from MyForm ; Further to make the printed codereadable I'll often drop namespaces and protection keywords when they don't provide additional informationShortened SystemWindowsFormsForm base class class MyFormForm fieldsRemoved private specifier and SystemComponentModel namespace void MyFormLoad object sender EventArgs eMessageBoxShow Hello from MyForm ;When showingNET attributes I use their full name SerializableAttribute class MyCustomTypeSome languages like C# allow the Attribute suffix to be dropped for convenience but that makes it hard to find the details of the attribute class in the online documentation Also I sometimes take error checking out of the printed code for clarity but try to leave it in the sample code that comes with this bookIn the prose itself I often put a word or phrase in italics to indicate a new term that I'm about to define As an example of this kind of term and its definition hegemony is preponderant influence or authority as well as a useful business practice Finally I often mention keyboard shortcuts because I find them convenient The ones I mention are the default Visual Studio Developer key bindings If you're not using those key bindings you'll need to map the keyboard shortcuts to your own settings Contact The up to date information for this book including the source code and the errata are maintained at This site also provides a way for you to send feedback to me about the book both complimentary and less so 0321116208P05022003.


As a fairly public figure in the Windows developer community I often get asked if I think thatNET is going to take off I always answer the same thing; it's not a matter of if it's a matter of when Microsoft'sNET Framework has so many benefits that even as a grizzled old CWin32 guy I wasn't able to resist the siren song of a managed development environment It's ironic that the temporary dip in the economy has caused folks to avoid anything new just whenNET comes along to deliver significant reductions in time to market and cost while simultaneously increasing code uality The organizations that have already adoptedNET know that it's going to have a long and happy life especially as it gets pushed further and further into Microsoft's own plans for the future of the Windows platform both on the server and on the client The primary server side technology inNET is ASPNET which provides the infrastructure needed to build web sites and web services ASPNET provides the reach to deploy web sites to anyone by aiming at the baseline of features provided by the middle generation web browsers To provide the highest level of functionality possible ASPNET does most of the work on the server side leaving the client side HTML as a thin wrapper to trigger server side reuests for new pages of data The server side handles practically everything from data manipulation to user preferences to the rendering of simple things like menus and toolbars This model provides the greatest availability across operating systems and browsers If on the other hand your targeted customers are Windows users an HTML based experience limits the users to a lowest common denominator approach that is unnecessary In fact in an attempt to provide a richer client side experience many organizations that know they're targeting Windows users reuire specific versions of Microsoft's Internet Explorer IE web browser However as soon as that happens IE becomes less of a browser andof an HTML based application runtime And for that purpose the HTML object model is fairly primitive often reuiring a lot of work to do things that are normally simple like keeping track of a user's session state If you're going to be targeting Windows users theNET Framework provides a much richer set of objects for building interactive user interfaces This brings me to the subject of this book Windows Forms WinForms WinForms is the face ofNET on the client providing a forms based development environment meant to provide the best of the UI object models that have come before it In addition it provides one feature that no Windows based development framework has provided to date the deployment features of HTML based web applications The ability to combine the richness of Windows applications with the deployment of web applications signals a completely new world for Windows developers; one that makes methan happy to give up the mess of unmanaged code Audience When writing this book I had two target audiences in mind I wanted to provide real world WinForms coverage for both the programmer that had already programmed inNET as well as for the programmer that hadn't Towards that end I do briefly introduce coreNET topics as they come up However theNET Framework itself is a large area that this book doesn't pretend to cover completely Instead when I thinkinformation would be useful to the reader I reference another work that provides the full details In particular I find that I've referenced EssentialNET by Don Box with Chris Sells a great deal making it a good companion to this book In this same category I can also recommend Pragmatic ADONET by Shawn Wildermuth AdvancedNET Remoting by Ingo RammerNET Web Services by Keith Ballinger and Applied MicrosoftNET Framework Programming by Jeffrey Richter Two coreNET topics are of special importance to WinForms programmers and I cover them indetail in Appendix B Delegates and Events and Appendix C Serialization Basics The coverage of delegates and events is particularly important if you're new toNET although I don't recommend diving into that topic until you've got a WinForms specific frame of reference which is provided about 13rd of the way through Chapter 1 Hello Windows Forms I'd like to provide one other note for potential readers Many years ago I wrote my first five day training course The topic was Windows 95 and included a few hours of coverage on the new controls; what they looked like what their properties methods and events were and how to program against them Those hours seemed to take days for both me and for the students The details of a particular control are only interesting when you're putting that control to use and when that time comes the control specific documentation and IntelliSense do a marvelous job of giving you the information you need Towards that end this book covers none of the standard controls completely Instead as each control is interesting the context of the current topic like the DataGrid control in Chapter 13 Data Binding and Data Grids that control is covered appropriately Also Chapter 8 Controls and Chapter 9 Design Time Integration introduces the broad range of categories of controls that WinForms provides including the category of non visual controls called componentsinNET Finally to give you a visual to go with all of the controls and components and to introduce you to the major functionality of each of them Appendix D Standard WinForms Components and Controls provides a list of the standard controls and components I wouldn't think to waste your time by attempting to bethorough that that reference documentation that comes with theNET Framework SDK and Visual StudioNET Instead this book focuses on the real world scenarios that aren't already covered in detail elsewhere Conventions For those of you that have decided to take the plunge with this book I'd like to thank you for your faith and express my hope that I live up to in To aid you in reading the following text I want to let you in on some conventions I use in my writing First and foremost the wonderful thing about WinForms is how visual it is which is why I use a lot of figures to illustrate its features Some of those pictures really need to be color to make the point so be sure to check the color pages at the center of this book for those figures As useful as figures are I think primarily in code Code will be shown in mono faced type SystemConsoleWriteLine Hello WinForms ; Console application activation will also be shown in mono faced type C cscexe hellocs When a part of a code snippet or a command line activation is of particular interest I mark it in bold and often provide a commentNotice the use of theNET System namespaceSystem ConsoleWriteLine Hello WinForms ; When I want to direct your attention to a piece of code evenfully I'll replace superfluous code with ellipses class MyFormSystemWindowsFormsForm fields private void MyFormLoad object sender SystemComponentModelEventArgs eMessageBoxShow Hello from MyForm ; Further to make the printed codereadable I'll often drop namespaces and protection keywords when they don't provide additional informationShortened SystemWindowsFormsForm base class class MyFormForm fieldsRemoved private specifier and SystemComponentModel namespace void MyFormLoad object sender EventArgs eMessageBoxShow Hello from MyForm ;When showingNET attributes I use their full name SerializableAttribute class MyCustomTypeSome languages like C# allow the Attribute suffix to be dropped for convenience but that makes it hard to find the details of the attribute class in the online documentation Also I sometimes take error checking out of the printed code for clarity but try to leave it in the sample code that comes with this bookIn the prose itself I often put a word or phrase in italics to indicate a new term that I'm about to define As an example of this kind of term and its definition hegemony is preponderant influence or authority as well as a useful business practice Finally I often mention keyboard shortcuts because I find them convenient The ones I mention are the default Visual Studio Developer key bindings If you're not using those key bindings you'll need to map the keyboard shortcuts to your own settings Contact The up to date information for this book including the source code and the errata are maintained at This site also provides a way for you to send feedback to me about the book both complimentary and less so 0321116208P05022003.

ePUB Windows Forms Programming in C# MOBI Ü Windows Forms  Ü spectekhnika.pro

ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro

10 thoughts on “Windows Forms Programming in C#

  1. MonsieurCanon MonsieurCanon says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFIt's been useful even though it's for a much earlier version of Visual Studio and C# I've not utilized but a small portion of the information It wasn't very expensive; it was used but was in excellent condition


  2. W Boudville W Boudville says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFThe book divides naturally into two parts Both use theNET forms package that Microsoft developed to simplify low level coding The first part is very straightforward graphics programming Someone who has used X11 on unix or java's AWTSwing or of course earlier MFC graphics will see no surprises Font properties drawing of curves pens etc are all here A very complete graphics packageBy placing the above discussion as the first part the author lets you have easy immediate visual feedback if you choose to code the examples It is always good for readers to tinker; helps retentionThe second half is slightly abstract Issues like resources internationalisation of lab


  3. A. Avrashow A. Avrashow says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFThis book is one of the finest technical books written I'm not just saying that I've read about half of it and I can't tell you how many times I read something and thought how would I use that or when would I use that featureoverloadoption? and found a clear example in the next sentence or paragraph explaining the differences or usefulness of that featureThis book is in the Addison WesleyNET series so it doesn't coverNET from the ground up instead it explains every nook and cranny of Windows Forms applications It is so packed with info tha


  4. Serge Shimanovsky Serge Shimanovsky says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFThis is an excellent book covers the entire C#WinForms part ofNET about as well as any single book could Unlike other books this one is intended for those who are able to digest the MSDN and wish to take their C#WinForms knowledge even further After browsing through countless books that introduce me to WinForms basics it is refreshing to find a book that dives right into some real hard core programming This book is not for beginners but is indispensible for experienced C#NET programmers who are looking to improve their skills This is without a doubt the best and most useful C# WinForms book I have ever read I would suggest this book to be an essential reading for every seriousNETWinFroms developer who wants to work smarter instead of harder Absolutely no fluff here every page contains interesting and useful info and the book as a whole is full


  5. Thomas B. Gross Thomas B. Gross says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFI bought this based on the rave reviews on but I must say after a couple of weeks I am very disappointed by this book I had hoped it would be a convenient and uick reference to such uestions as how do I use FolderBrowserDialog andor OpenFileDialog to open a file in my C# program? but although these standard components are indexed in the book the discussion of them in the book is shorter than this review I am writing What I would want is some kind of sample code maybe a step by step description of how to add the components to my program I am left wondering what exactly is filling up the 658 pages of this book I much p


  6. Scott Galloway Scott Galloway says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFif you're looking to learn Windows Forms programming in itheNET framework this is really the only book you'll need This has comprehensive coverage of all the main techniues THe coverage of using Visual StudioNET is wonderful Charles Petzold's book is pretty good but it is all code no IDE stuff is mentioned


  7. LB LB says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFE' un testo molto lungo che spiega fin nei dettagli come usare i controlli di Visual C# Non tratta il linguaggio come dichiara il titolo Non più tanto recente è del 2002 ma ancora utile


  8. saintgr8 saintgr8 says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFOrdered for this book only to be given a novel


  9. Michael Mccloskey Michael Mccloskey says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFIf you are currently or aspire to be a seriousNET developer then buy this book Buy it now Do not hesitateAfter fully assimilating Francesco Balena's Programming Visual BasicNET coming from a VB6 background and Jeff Prosise's ProgrammingNET during my C#


  10. E. Mitchell E. Mitchell says:

    ePUB Windows Forms Programming in C# MOBI Ü Windows Forms Ü spectekhnika.pro windows pdf, forms book, programming ebok, Windows Forms book, Programming in free, Forms Programming in book, Windows Forms Programming in C# PDFNo where in the title cover or product description does it explain that this covers a very old version of Windows Forms programming that is no longer relevant today I had not looked for the publication date when choosing this book silly me The author put the manuscript to bed in April 2003 and the book was published in September of 2003If you are completely new to Windows Forms realize that this book was written to about Visual Studio 2003NET standards Huge changes have been made to Visual Studio andNET since then major revision being Visual Studio 2005 and 2008When you read the assorted reviews here on you'll note that most reviews are dated around 2004 or soThis book should be fully updated to a new edition or taken off the market Being six years old and withNET and Visual Studio both having undergone several revisions since then this book has limited relevancy in 2009 I regret that I purchased this book


Leave a Reply

Your email address will not be published. Required fields are marked *