Discussion Locked

Help us design a guide to VB.NET

0 helpful
26 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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)?

26 replies

by brabo

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.

by rexworld

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).

by brabo

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

by bucky kaufman (mcsd)

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.

by bgibilaro

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.

Thanks.

Bob Gibilaro
Have Keyboard, Will Travel

by rexworld

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?

by brabo

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.

by rjclawson

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.

StringBuilder

Version numbers

GetEnvironmentVariables

Threads

Stored procedures

Dll use

Setup and Deployment Project

I had to deal with all of these.

God bless you!

by bucky kaufman (mcsd)

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.

by abthin

I think this is a great idea. There are so many different facets that can be added to this to help programmers and non programmers alike.
1. special section for standards that would be usefull to beginners. i.e. naming conventions, screen layouts and so forth.
2. access to database, DAO and any database related items.
3. Maybe even do a project to show how to create a transactional system and an informational or even a PIM (Personal Information Mgr) site.
I found that using an application sample is the most effective way to learn.

Thanks for your time.

by superj42

I wouldn't mind seeing the document published as a PDF, or a LIT.
I also think a font size of 11 or 12 would be good. A 12 point font, in my opinion, would be a happy medium between going with a too small, or too big of font.
As a beginner to VB.NET, I was pretty happy that this document is in the works, especially with a collaborative process in place.
I agree with the items concerning proper naming conventions, database connectivity (connecting to and closing connections), toolbar activity, etc.

by chuckr314159

I don't care about the font size. But here are some of my ideas based on the troubles I've had so far and expect to have. First, I think different users need different types of help based on the path they've taken to get to VB.NET. In my case, I migrated from DOS QuickBasic, gradually got into event-driven programming with the VB and Office VBA versions, which naturally led to web programming with ASP, and am now moving to VB.NET/ASP.NET because debugging ASP is a pain. And kicking and screaming all the way, I've incrementally been picking up the thought process behind OOP, classes, inheritance. Here's what I would like to see...

* Intro to Microsoft Data Engine (MSDE) - All the walkthroughs/samples in Help assume you have and know how to use the MSDE. What a pain, trying to figure out how to download, install, create databases, set permissions (on both desktop and server), find and learn to use the OSQL utility, use Access ADP frontend to manage the DB, etc. It's probably simple for those use to dealing with real DBs and writing SQL, but for those of us who's first and only DB was Access, it's a whole new world. There is no concise source for help on this that I could find. MS seems to want us to migrate away from Access, but I need help doing so.

* As others have mentioned, then I'd like to see intro's to dataadapters, data connections, datasets, simple reading and updating, stored procedures, backing up, security, uploading to a server, etc. The VS Help concentrates on binding DBs to controls, but I think their samples are impossible to understand until you first just learn how to read and write to a DB without binding.

* What to use and why? DAO, ADO, ODBC, ADO.NET, etc. Then for text file reading/writing there seems to be at least three ways - FSO, .NET classes, ...etc?

* In VB, I set references from the menu. Now I add references to the Solution Explorer and I add things like "Imports System.Data.SqlClient" to my declaration sections. I get things to work, but I'm not sure I understand what I'm doing yet.

* System Generated Code - When I need to worry about it and when I can ignore it? Discuss.

* Extremely simple Hello World examples of doing various tasks. For example, setting up a class (DLLs, different types of classes?), setting up properties, methods, etc. Then perhaps a simple example of how inheritance works.

* New ways of doing things - Should I/why should I switch from the way I do it now? For example, new ways of defining and using strings.

* Deploying applications - Do I still need programs like InstallShield? Will I still experience DLL Hell?

* XML - I understand the basics of what XML is. But can I live a full life using VB.NET/ASP.NET without becoming an expert and using it directly?

* Along the lines of the XML question - In general, it would be good to get help prioritizing what you need to learn. Since the new stuff is overwhelming. For example, if you want to write a Web Service, these are the areas you need to tackle. If you want to write apps for PDAs and cellphones, these are the things you need to tackle.

I'm sure I can think of more, but this is long enough for now.

by rexworld

I just wanted to thank you, and everyone, for your great ideas on this thread. I'm not sure we're going to be able to satisfy all these requirements but it's certainly fodder for future editions as well.

Thanks again, we'll turn loose the editorial team to get working on these ideas.

by surajprabhu

Since you are making this guide.. i would also like you to include some pointers ( if possible details) on the architecture of Client server and Web based application using VB.net, which clearly suggest where the business logic lies and where the validation lie etc etc with examples coz the existing patters and archi's in MSDN are very confusing and very comprehensive which is very boring to go through.

by rjclawson

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

Toolbox. Show how to add a new tab and save your own clips of data; you can save a word, line, function, sub, or an entire Module. This saves time from looking in past projects for useful code. This is much faster and easier than using Macros to save code.

StringBuilder

Version numbers

GetEnvironmentVariables

Threads

Stored procedures

Dll use

Setup and Deployment Projects

Some of these may be advanced but they are necessary.

by rjclawson

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

Toolbox. Show how to add a new tab and save your own clips of data; you can save a word, line, function, sub, or an entire Module. This saves time from looking in past projects for useful code. This is much faster and easier than using Macros to save code.

StringBuilder

Version numbers

GetEnvironmentVariables

Threads

Stored procedures

Dll use

Setup and Deployment Projects

Some of these may be advanced but they are necessary.

by max.figueredo

How about writting windows services with vb.net ?, or including some how-to's about using the Microsoft Building Blocks (there are already some articles on this at builder).

by dmcopa

If your going to make a Hello world you could also make it in an MDI Parent thus showing how to open forms within an MDI Container form. There is absolutely no good information on this. I personally took me several days of playing around to get the child form to show up within the confines of the Parent. Of course it makes sense now but for new programmers or VB6 programmers wishing to use MDIs, its rather irritating to not have the child property anymore with nothign to tell you how to make it a child form.

by smithj7

Home you are right. I can't figure out how to do this. I've done all kind of strange things, create the main form a couple times, and create a brand new form with the name of the form I just wanted to display. I am currently trying to find this information and can't. Till the guide is developmed can you send me in the right direction?

by semi-adult

Size DOES matter. Why can't we have multiple sizes? Isn't the output format supposed to be relatively independent of content? If you have your content, why can't you send it out in whatever wrapper works for the purpose? That is, let's have 8 or 9 point type in a PDF for printing, and 12 or 14 point type in another PDF for viewing... just make them selectable in some convenient manner.

Do the same for the LITs, or any other format that will work for users.

Let's not get caught in the 'how cheap can we make things' trap. The purpose of everything we do in IT is to serve the users' interests. This time we're the users, with a variety of interests.

by miles

Who prints this stuff out anymore? Make it larger type on the screen so its readable. Who cares if its a few more pages. Provide a table of contents to navigate and presto!

by tongloo

I think the guide should include the following:
a) Explaination of VB.net Archictecture
b) Benefits of using VB.net compared to other programming languages such as C#
c) Information on what to things when migrating from VB to VB.net
d) VB.net functions syntax and explaination

Lastly, I would like to thanks for such a good initiative of compiling the guide, it would be useful for developers.

by lucho_con_cerveza

There is one post in this discussion that the author suggested that s/he got things done, but wasn't sure their approach was correct. That is the way I feel most of the time.

You search and search, just glad to find something that works, so you take it, use it, and get the results you want, so the task gets accomplished, not knowing that perhaps further in the search there is a method or code segment that accomplishes the same thing fast and better.

With all of the complex languages today, it is not knowing how to use the language, but how to use the documentation and manipulate the help searches that make a good programmer. Unless one is an ubergeek, there is no way to know a language like we used to know 'C' or Basic.

Anyway, I think it would be best to structure your content towards this thinking. Divide it up into sections like.
1. What is VB .NET (include flow diagrams for those of us that are graphic) and how does it differ from VB 6.0.
2. How to use the objects, properties and methods (whatever these are in .NET speak.
3. How to use Help and searches to find out how to do what you want to do, and how to determine that you have found the right way to do it.
Appendix A. A living library of objects that accomplish the mundane programming functions; open/manipulate/close various file structions, communications between applications, common routines that we all re-invent most of the time.

With the complexity of the lanuages, I predict that the next step in programming will be a GUI where there is a sequence line (not for sequential programming, but to bring order to the process) and you grab the icon for an object that is labeled "start application" from a pallet and put it on the line, then grab a "decision" object icon, and drop it next to the "start...", and get prompted with a fill-in-the-blank text in readable text to tell what the decision is, what the prompt is, and what to do with the decision.

Again, languages like VB .NET are well-meaning, but TOO complex to be used efficiently.

Sorry for the rant, but this subject is near and dear to my heart at the moment as I struggle to decide the best objects to use for a minor communication between two programs.

TKs, and good luck with your effort.

And I agree with the consenus; size does not matter re:PDF - if we want it bigger or smaller, we will find a way to display or print (who does print anymore?) it that way.

by bryancallahan

This might not be a good idea for a basic guide to VB.NET. But since I have started working with VB.net I'd like to see more information about how to Class and subclass. Perhaps tips and tricks of communicating between classes within classes. Thanks for the great newletters, btw. Take it easy all!

by drunyan8315

My current focus is learning how to use Datasets, and so that is what I would want covered extensively... how do I take the SQL skills I have and apply them to a program that uses Datasets to be independent of a DBMS?

More generally, I would like to see a "learning strategy" that would help the beginner understand the best sequence of topics to study in order to achieve proficiency for specific types of development situations. Perhaps a decision tree type approach would work?

Finally, advice on best practices, from "what every program should have" to more topic-specific. Even the intro material in a lot of the books contains such turgid techno-speak that it does not really lead you into the topic, but simply forms the first barrier! Introductory material, written by folks who know how to communicate in writing, and omitting nothing as "obvious", would be priceless! How about each chapter has one intro page for the new programmer, a next intro page for non-OO programmers, and then an intro page for VB6 folks, and then the main intro. Then you could start where you felt comfortable. A lot of work? Yes, indeed, but it would kickstart so many more good programmers into .Net.

This discussion is closed to new replies.