Having done OO development for a while, using interface inheritance and delegation in VB6 allowed me to be relatively faithful to the OOP model. Even though I have used VB since VB4, when it came to migrating to VB.NET, I determined that VB.NET is like a "new" language. So I decided that if I was going to put in the effort to learn a new language, then I would put my effort into C# as it is very close to Java, which I use also.
The REAL learning curve, no matter which path you take will be the .NET framework! It is a killer!
Discussion on:
View:
Show:
I've written a number of n-tier products in vb6 using the Duwamish Books example method as mentioned by microsoft. However, there are no such examples for .net.
My problem is i'm trying to build an equipment hire application. I want to creat as one of my objects and equipment object that will sit in my middle layer. It will talk to sequel through ado.net. The 1st layer ie the GUI will simply validate and display date that will come from the Equipment object the 1st tier will instantiate. However, all examples show the display layer being bound directly to the the database through ado.net..you know the datagrid having an ado.net data set as a source. I want to see an example that uses the middle business layer to bind to the forms controls...I cannot find one..has Microsoft abandoned n-tier architecture ?
Some one who knows please tell me
Josef
My problem is i'm trying to build an equipment hire application. I want to creat as one of my objects and equipment object that will sit in my middle layer. It will talk to sequel through ado.net. The 1st layer ie the GUI will simply validate and display date that will come from the Equipment object the 1st tier will instantiate. However, all examples show the display layer being bound directly to the the database through ado.net..you know the datagrid having an ado.net data set as a source. I want to see an example that uses the middle business layer to bind to the forms controls...I cannot find one..has Microsoft abandoned n-tier architecture ?
Some one who knows please tell me
Josef
What do you do if you have a 35,000 line vb6 application that is still evolving. The time it would take to upgrade / rewrite something like this is just too scary. I just haven't seen a .net feature that warrents the huge redevelopment time and expense.
That's why there are still millions of lines of code out there (COBOL, RPG, BASIC, etc.), still working and still being maintained. Sometimes it's not worth the time and effort to rewrite.
I'm working on a monolithic DELPHI 5.0 app that will never be re-written or ported to another language. There just isn't a business case for it.
.Net is for new development, and for those apps that can justify the time and expense required to refactor.
Face it - VB6 is now a "legacy" language, and VB6 coders will soon be viewed as legacy programmers - kind of like COBOL coders. Lot's of maintenance programming, but not a lot of new development.
I'm working on a monolithic DELPHI 5.0 app that will never be re-written or ported to another language. There just isn't a business case for it.
.Net is for new development, and for those apps that can justify the time and expense required to refactor.
Face it - VB6 is now a "legacy" language, and VB6 coders will soon be viewed as legacy programmers - kind of like COBOL coders. Lot's of maintenance programming, but not a lot of new development.
If you are dealing with client side VB6 applications, then .NET will not give you a REAL advantage. You don't want to rewrite 35K lines of code, and get stuck with a HTML instead of your rich application.
For the dynamic nature of HTML, you can look for comanies like Navicula that gives your existing VB6 new life,
For the dynamic nature of HTML, you can look for comanies like Navicula that gives your existing VB6 new life,
If you designed your app as a collection of COM objects (which you should be doing anyway), then you can easily move to .NET. .NET can access those COM objects with no problem. So, all new dev can be done in .NET and all the "legacy" code can remain in place. You could then migrate the objects to .NET as needed (if ever).
But, if your app is just 35K lines of procedural code, then you're hosed
If that's what your dealing with, then you need to take a close look at your development environment. Aparently, somebody high up doesn't "get it".
just my $.02 worth.
______________________________
- David Lanouette
- DLanouette@Computer.org
- Lanouette Consulting, LLC.
But, if your app is just 35K lines of procedural code, then you're hosed
If that's what your dealing with, then you need to take a close look at your development environment. Aparently, somebody high up doesn't "get it".just my $.02 worth.
______________________________
- David Lanouette
- DLanouette@Computer.org
- Lanouette Consulting, LLC.
Do the words "vendor lock" have any meaning to you? Besides, VB coders are not going to become fossils overnight: there is still plenty of "legacy" VB development going on as we write.
I began -and learned- programming with VB4. By version 6, having lived through the alphabet soup of technologies that MS kept touting as the next greatest thing, I decided to pull up onto the sidewalk to look around. What a welcome sight it was to find out that: MS are rope salesmen (if you don't know what that is I'd advise you to look into the concept), Delphi\Kylix is a smarter investment in RAD development, and open source is a reality. If you’re an all-MS shop, then I’d hazard to guess you’ve made up your mind and gone XP-***-dot.net. Otherwise, I’d take a look around. Of course you’ll have to step off the treadmill to do so, but I think you’ll find life most interesting outside the box.
I began -and learned- programming with VB4. By version 6, having lived through the alphabet soup of technologies that MS kept touting as the next greatest thing, I decided to pull up onto the sidewalk to look around. What a welcome sight it was to find out that: MS are rope salesmen (if you don't know what that is I'd advise you to look into the concept), Delphi\Kylix is a smarter investment in RAD development, and open source is a reality. If you’re an all-MS shop, then I’d hazard to guess you’ve made up your mind and gone XP-***-dot.net. Otherwise, I’d take a look around. Of course you’ll have to step off the treadmill to do so, but I think you’ll find life most interesting outside the box.
That's all fine and dandy, but when I went .Net I was more interested in where Microsoft was going, now where they had been (it's not a pretty history). I made the right choice... I enjoy programming like I never have before.
But looking back to the original article, if a bunch of Web script kiddies can make the leap in short order, I seriously doubt it's that much of a barrier for VB6 folks!
But looking back to the original article, if a bunch of Web script kiddies can make the leap in short order, I seriously doubt it's that much of a barrier for VB6 folks!
During last year's budget meeting, I requested funding for exploratory development using Delphi/Kylix and Linux thin clients. The project got funded.
I've been programming using Access, VB, and Foxpro for 8 years now, and I'm sickened by the constant re-invention of the wheel that goes on and on at Microsoft.
Every new version seems to bring little in the way of value over the old. Indeed, many of the features we loved in previous version are dropped in the new. Each new version has lotsof "breaking code" forcing rewrites of prior code.
I'd appreciate any links to newsgroups or Web sites for Delphi developers.
I've been programming using Access, VB, and Foxpro for 8 years now, and I'm sickened by the constant re-invention of the wheel that goes on and on at Microsoft.
Every new version seems to bring little in the way of value over the old. Indeed, many of the features we loved in previous version are dropped in the new. Each new version has lotsof "breaking code" forcing rewrites of prior code.
I'd appreciate any links to newsgroups or Web sites for Delphi developers.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
