Some ideas about "classical VB"

Recently, this topic has been in the "newsgroups" (er, at least in a lot of blogs), I have been thinking about how to reply to everyone ... But in fact, I have no need to reply at all, because Dave Totzke has done it for me. He mentioned one point in the article: we should let C + + continue to exist, because Office is written in C + + ... I'm not too flattering about this, because the reason for this is actually that the managed world cannot replace our need to write local code for the underlying hardware and operating system. We need at least one solution to make graphics software, device drivers, network information filters and so on work efficiently ... As a result, we still need unmanaged C + +. But for VB6 change, there is no such need.

Sure, it's pretty hard to upgrade a complex code base, but installing vb.net doesn't mean you have to delete VB6. You can keep your existing code base while in the. NET to write new code, and then let the two worlds work when necessary. In MSDN, you can find an Access application that pops up a new form when you click on certain buttons ... You can also find VB6 plug-ins for Outlook and Word, but they are. NET code packaging material, is a VB6 code and vb.net code of the mix.

There are a lot of things that can be found in the VB6 but not included in the vb.net, which I think is not very good, but I think they can be introduced into the vb.net in the form of. NET components, ActiveX components, or Visual Studio Plug-ins. For example, DDE (Dynamic data exchange, runny note), it is not. NET Framework, so I envision if there is a small component that makes us in. NET can directly access DDE, when new data arrives can raise events, and so on ... That's a lot better. I really hope that people are committed to building (or making a request to build) such a component, rather than shouting desperately to do something is not a good idea. At the very least, people should try to get it listed in the process of upgrading and development. We'd better get someone to build a tool that's not just a wizard, it's a job for upgrades, and it includes a whole bunch of additional libraries to transform old code. This would be a huge project, but its results would be more satisfying than a few complementary improvements to VB6.

By the way, I've always wanted to tell you, I really think that. The net world still lacks some things so far. We need to be. NET provides a tool similar to the Access interface ... It can't be like the tool in VB6, because it's too hard to use for the level of developers I see ... It should be an application creation tool that supports database drag-and-drop, like access, FileMaker Pro, HyperCard, and so on ... It should be able to generate automatically behind these settings. NET code, so that we can use this tool, with code created by vb.net or C #, to extend a simple application. I think I'll give it a name, access.net:)

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The following is the original text for netizens to reference, if you want to go to Mr. Duncan's homepage read the text, please click here.

This is topic has been in the ' News ' lately (OK, at least in the blogs) and I ' ve been considering ... replying it but Out I don ' t have to, because Dave Totzke has do it for me. I Don ' t really agree with he comment that we ' ve kept C + + alive because Office is written in it ... it is actually because The managed world doesn ' t replace the need to write native code against the underlying hardware and OS. We need to have at least one avenue for folks to write the high-performance graphic, software device, drivers pack ET filters, etc .... So we need unmanaged C + + to stay. There isn ' t a similar need for new development on VB6.

Yes, it is hard to upgrade complex code bases, but when you install vb.net it doesn ' t uninstall copy of your. It is possible to maintain a existing code base while your write new code in. NET and then interop as necessary between th E Two worlds. Within MSDN, we have Access applications that pop-up Windows Forms when you click certain buttons ... we have vb6-based add -ins for Outlook and Word this are simple wrappers around. NET code and some-are-a mix of VB6 code and vb.net code ...

There are some things that were in VB6 and are not available in vb.net that I feel still need to be available, but I They could is made available as. NET components, ActiveX components, or add-ins to Visual Studio. Take DDE For example, it just isn ' t part of the. NET Framework, so I-I-I-I-I-I-I-it would be nice if we had a small component th At allowed me-access DDE from within. NET, fired events when new data arrived, etc ... I wish that people would put their effort towards building/requesting this types of components instead of advocating Thing that just isn ' t a good idea. At the very least, push for more effort to is put in the upgrade process, lets get someone to builds more than just a Wiz ARD, build a tool that does the upgrade and includes a ton of additional libraries to help with transitioning code. That's would be a lot of work, but the "end" is still better than the just doing incremental development on VB6.

By the way, the it is as good of as, as, as, the. D right now. We need an access-like tool for. NET ... not what VB6 is, which is really much too to the level of complicated I ' m thinking of ... but something that is a Drag-and-drop database form focused application creation tool. Like Access, FileMaker Pro, HyperCard, etc ... But producing. NET code behind the scenes so, can extend simple applications created using this tool with Code Pro duced out of vb.net/c#. I'll call it access.net:)