Books: Develop Web Solutions With VB.NET -- Visual Studio Magazine

Books: Develop Web Solutions With VB.NET

VB.NET offers an improved palette for creating Web-based software. Programming the Web with Visual Basic .NET is a complete reference book that gives you all the info you need.

By Joel Semeniuk
04/26/2004

Visual Studio .NET and the enhancements to the Visual Basic language give you a new and improved palette for creating Web-based software. However, these new tools come at a significant cost of learning. Having experience in previous versions of Visual Basic or a Web development environment won't necessarily make you immediately proficient at building Web applications with VB.NET. The authors of Programming the Web with Visual Basic .NET have worked hard to significantly lessen this burden.

If you're looking for a complete reference book for building Web applications with VB.NET, this book should be on your list. It begins with a general discussion of Web applications, taking you from the creation of simple Web pages and Web server controls to the development of XML Web services. A large part of the book discusses how to access data and provides you with details on how to build and deploy your Web applications. The book features a lot of quality sample code and illustrations, and the four detailed appendices do a good job of filling in some of the foundation knowledge that will increase your overall understanding of HTML, XML, and development server configurations. You won't be a software architect after reading this 900-page, 15-chapter book, but you will have all the information you'll need to be proficient at developing and managing Web solutions built with VB.NET.

Programming the Web with Visual Basic .NET
by Lynn Torkelson, Constance Petersen, and Zac Torkelson
Apress
ISBN: 1590590279
Price: $59.95
Quick Facts: Shows you how to build Web applications and services using Visual Basic .NET; written for experienced Web programmers.
Pros: Excellent appendix chapters on Web design tips, HTML quick reference, XML quick reference, and server configurations.
Cons: Thick and intimidating.

About the Author

Joel Semeniuk is a founder of Imaginet Resources Corp., a Canada-based Microsoft Gold Partner. Currently, Joel is also serving as an Executive VP of Agile Project Management Tools at Telerik. He is also a Microsoft Regional Director and MVP Microsoft ALM, with a degree in Computer Science. With more than 18 years of experience, Joel specializes in helping organizations around the world realize their potential through maturing their software development and information technology practices. Joel is passionate about Application Lifecycle Management tooling, techniques and mindsets, and regularly speaks at conferences around the world on a wide range of ALM topics.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.