|
|||
|
Migrating to .NET
Migration - Creating Services in .NET - 12/29/2003 In VB6, writing a service was usually done by the C++ gurus. Also, watching directories for file creation, movement, etc., was not easy, to say the least. Under .NET, a breeze! more... Why Migrate - .NET Eases The Task of Accessing the Registry - 12/26/2003 Unlike VB6, the .NET framework provides base classes for accessing the registry. This article provides a wrapper class for the NET base classes. more... Serializing a ListView to XML - 12/23/2003 Why should I migrate to .NET? Another reason is Serialization (saving objects to files) to XML is so simple in NET. more... DataBinding VB6 vs. VB.NET - 12/18/2003 Most business related applications, in one way or another, involve controls that were populated from a database. Even in instances where they aren't populated by a database, things have changed dramatically FOR THE BETTER in .Net. For instance, many times you may know that only x number of choices should even be in a Listbox control, and it's totally appropriate to hard code them in the IDE (a listbox full of all 50 States comes to mind). After all, if you go to the database to fill the listbox, you will incur some overhead associated with database access. On the other hand, you get flexibility, if the Puerto Rico were to become a state for instance, you wouldn't have to recompile your app. On the other hand, if you hard coded the states, you'd gain performance at the expense of some scalability. However, conisdering the likelihood and frequency of new states becomming members of the US, the tradeoff is probably worth it. Suffice to say that it really depends on the needs of your app. Nonetheless, let's look at the old VB6 way of dealing with this: more... |
|
 |
|
|