First in a series on how to update old legacy VB.NET applications, while the application stays up an available throughout the process.

1. Updating Legacy VB.NET
Applications
http://www.Bradirbyassociates.com/

2. http://www.Bradirbyassociates.com/

3. First Things First: Project Options
If you’ve ever worked with a VB.NET project that has
been around since the early days of .NET 1.1, you
probably had a lot of cleanup to do before applying any
of the latest technologies.
http://www.Bradirbyassociates.com/

4. Option Explicit = On
The first thing to do is ensure Option Explicit is turned on. This is a
property in the VB.NET Compile project page that requires all
variables to have an explicit declaration – a DIM statement. When
this option is set to Off, variables can be created and used on-the-fly
without a formal declaration. This is bad because with Option
Explicit = Off, a simple typo in a variable name will cause the
compiler to create a new variable by that name, resulting in bugs
that are very hard to find.
http://www.Bradirbyassociates.com/

5. Option Strict = On
After setting the Option Explicit = On for all projects, set Option
Strict = On. This option enforces valid type conversions (called
Widening Conversions) and can catch a lot of bugs that are difficult
to find later on. After setting this option, you’ll most likely see a lot
of error appear in the Error List of Visual Studio.
http://www.Bradirbyassociates.com/

6. Reengineering
When your software needs modernized, we enhance or
rebuild your application to take advantage of modern
technology while you continue to use your existing
application – No down time, no stress, you never need to
shut down your existing application.
http://www.Bradirbyassociates.com/

7. Thank You
http://www.Bradirbyassociates.com/