Freigeben über

Upgrading VB6 to VB.Net

  • Artikel

This just in. . . a page dedicated to porting VB6 apps to VB.Net

Now that the .Net Framework will be included in each copy of Windows Vista, porting from VB6 to .Net is the last

big pain point I've heard from the MicroISV (Shareware) developers.

Let me know what you think about this!

Comments

  • Anonymous
    January 17, 2006
    The comment has been removed
  • Anonymous
    January 17, 2006
    Oops meant index starting at 0.
  • Anonymous
    February 14, 2006
    I'm glad that Vista is shipping with .NET, but why not new versions of XP? What about 2000, and 98? Those are "officially" supported MS platforms..

    I still have customers using Windows 98, which is still officially supported by Microsoft even 8 years after it's first public appearance. Many more customers use Windows 2000 and the vast majority, XP. .NET hasn't shipped with any of those. I can't imagine everyone is going to switch over to Vista right away so (going by past observation) I'm looking at another decade supporting XP.

    With the release of .NET 2.0, we've started the .NET framework deployment counter all the way back to zero. There is no way Micro ISVs can afford to sell software that requires an additional 20 meg download and fairly complex installation when their competitors don't. Customers are going to take one look at the 30+ meg download or .NET dependency and run away!

    Only with tools like Salamander and Thinstall is developing for the .NET platform going to be feasible for shareware developers and even then we're starting off at a disadvantage because of the huge file sizes.

    Don't get me wrong, I think .NET is the best programming platform I've ever seen. For web app development it's hands down the best, but for desktop applications it is still really hard for anyone to deploy a .NET application on a large scale. I don't understand Microsoft's continued insistance that .NET is the future while making sure that .NET programs won't work on everyone's computer.

    Possible interim solutions :

    Make a native compiler. If Hui at RemoteSoft.com can do it, I know you guys can.

    Forget the compiler, just make a linker. If Hui at RemoteSoft.com can do it, I know you guys can! :-)

    Make a real protector. Again, if Hui at RemoteSoft.com can do it, I know you guys can! :-)

    And the solution to everyone's problem :

    Make the .NET framework a required update and start bundling it with new installs of XP. It won't fix the problem right away but it's a step in the right direction.
  • Anonymous
    September 02, 2006
    PingBack from http://www.microisv.com/archives/2006/01/27/upgrading-vb6-apps-to-net/
  • Anonymous
    June 08, 2009
    PingBack from http://jointpainreliefs.info/story.php?id=2044