IT Employment

General discussion


Help us design a guide to VB.NET

By RexWorld ·
We're pulling together a getting-started guide to Visual Basic .NET, and we'd love to get your feedback on what things you'd find useful. We're thinking a "Hello, World" app of course to show you the basic steps for building a VB.NET app, and a guide to the basic syntax (pardon the pun).

But what else would you like to see in this sort of getting-started guide? And if we made the guide into a PDF, would you prefer we use large fonts (so it looks good on the screen) or a smaller font (so it doesn't take up too many pages when you print it out)?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Help us design a guide to VB.NET

by brabo In reply to Help us design a guide to ...

I would like to understand at a high level where material differences to the equivalent code in C# may exist. C# is the preferred language of my .NET developers but as a novice less accessible to me than VB.

Collapse -

Any specifics?

by RexWorld In reply to Help us design a guide to ...

You mention "material differences"--are you after just differences in syntax, or differences in capabilities (i.e., it's easier to twiddle low-level bits in C# than it is in VB).

Collapse -

Material differences

by brabo In reply to Any specifics?

Where C# might offer a different approach as well as major syntactactical differences, if any.

Collapse -

PDF Print Size

by austina In reply to Help us design a guide to ...

Large print please.

Collapse -

LIT instead of PDF

by Bucky Kaufman (MCSD) In reply to PDF Print Size

Since Microsoft Reader .LIT files are Microsoft's answer to PDF's - I'd want to see it published as a .LIT file. Besides which, "PDF" has special meaning in .NET - totally unrelated to Macromedia's file format of the same name.

Collapse -

RE: Help us design a guide to VB.NET

by bgibilaro In reply to Help us design a guide to ...

I would think that creating a PDF with smaller fonts would be better since it would be a lot easier to have the guide printed out and on hand instead of having to refer to a .PDF all the time.

As far as what to include, I think custom server controls are a must. The potential for reusability and extended functionality are so critical to improving your apps.

I also think caching would be another major subject to cover, particulary relating to how you can use it to improve the performance of your apps.


Bob Gibilaro
Have Keyboard, Will Travel

Collapse -

Advanced vs. Beginner?

by RexWorld In reply to RE: Help us design a guid ...

Okay, you made some great suggestions on what to include but to me they sound like they belong in an advanced guide. This is our first attempt at any kind of VB.NET guidebook so shouldn't we focus for now on the beginner stuff?

Or is there some way to include this information you're after while still providing good coverage for the beginner info?

Collapse -

Good point - focus on the beginner

by brabo In reply to Advanced vs. Beginner?

As an introductory text the focus should be on the beginner however it can have broader appeal and aid the beginner if there is an indication of steps to move to next level e.g. using stringbuilder versus & as covered in one of your articles.

Collapse -


by RJClawson In reply to RE: Help us design a guid ...

Here are a few items that I would like to see in your Guide:

Toolbox. Hold your own clips of data. This saves time from looking in past projects for useful code.


Version numbers



Stored procedures

Dll use

Setup and Deployment Project

I had to deal with all of these.

God bless you!

Collapse -

Tasbar Icon, Database Access, WinForms and WebForms

These are the three things I'd want to see:
1. How to manage a taskbar icon.
2. How to connect, query, update and disconnect databases.
3. How to create Windows Forms that are similar to accompanying Web Forms.

Related Discussions

Related Forums