Recently, this topic has appeared in the "news group" (, at least have appeared in a lot of blog), I have been considering how to reply to everyone ... But in fact, I have no response, because Dave Totzke has already I did it for me. He mentioned it in the text: we should let C continue to exist, because office is written with C ... About this point I don't dare to compliment, because this reason should actually be - this hosted world can't replace We write the needs of local code for the underlying hardware and operating system. We at least one program that allows graphics software, equipment drivers, network information filters, and the like to operate efficiently ... so we still need unmanaged C . But for the change of VB6, there is no similar need.
Indeed, the upgrade complex code base is quite difficult, but installed VB.NET does not mean you have to delete VB6. You can keep your existing code base, and write new code in .NET, then let these two worlds work in each other when necessary. In MSDN, you can find an Access application, when you click some of the specific buttons, it will pop up a new form to ... You can also find VB6-based plugins for Outlook and Word, in fact they are. The NET code packaging material is a mixture of VB6 code and VB.NET code.
There are still many things, they can be found in VB6, but they are not included in VB.NET, I think this is not very good, but I think they can pass .NET components, ActiveX components, or Visual Studio plug-ins. Introduced VB.NET. For example, DDE (dynamic data exchange, 淌 注), it is not part of the .NET framework, so I envision if there is a small component, so that we can directly access DDE directly in .NET, reach new data It is possible to trigger an event, such as ... that is much more. I really hope that people can be committed to building (or committed to requesting construction), rather than desperate, do something, is not a good idea. At least at least, people should also work hard to be listed in the process of upgrading. It is best to let someone build such a tool, but this tool is more than just a wizard, but can compete for upgraded work, and contain a lot of additional libraries, let this turn old code. This will be a huge project, but it is more satisfactory than the improvement of the VB6 to make some additional reunification.
By the way, I have always want to tell you, I really think that some things are still lacking in .NET world. We need to provide a tool like an Access interface ... it can't be like the tool in VB6, because it is too difficult to use for the level of developers in my eyes ... it should be a support Database Drag and drop app creation tool, like Access, FileMaker Pro, Hypercard, and so on ... It should be able to automatically generate .NET code behind these settings, so we can use this tool, fit by VB. The code created by NET or C # extends simple applications. I think I will give it a name, access.net :)
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@8 For netizens, please click here to read the text on Mr. Duncan. THIS TOPIC HAS BEEN in The 'News' Lately (Well, At Least In the Blogs) and i've been considering replying .... But it Turns Out I don't have to, Because Dave Totzke Has Done it for me. I do not really agree with his comment that we've kept C alive because Office is written in it ... it is actually because the managed world does not 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, network packet filters, etc .... so we need unmanaged C to stay. There is not a similar need for new development on VB6 .
Yes, it is hard to upgrade complex code bases, but when you install VB.NET it does not uninstall your copy of VB6. It is possible to maintain an existing code base while you write new code in .NET and then interop as necessary between the 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 that are simple wrappers around .NET code and some that 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 think they could be 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 Think It Would Be Nice Id A Small Component That Allowed Me To Access Dde from With, Fired Events When New Data Arrived, ETC .. . I wish that people would put their effort towards building / requesting these types of components instead of advocating something that just is not a good idea. At the very least, push for more effort to be put into the upgrade process, lets get someone to build more than just a wizard, build a tool that does the upgrade and includes a ton of additional libraries to help with transitioning older code. that would be a lot of work, but the end result is still better than just doing incremental development on Vb6.by the way, this is as good of time as any to point out That I do believe That there is something missing in. NET World Right Now. We need. NOT What VB6 WAS, Which Was Really Much Too Complicated for the Level Of Developer 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 that you can extend simple applications created using THIS TOOL with CODE PRODUCED OUT OF VB.NET/C#. I think'll call it access.net :)
