porting VB6.0 Apps from Server 2003 to Server 2008

[ahoodin]

Anybody ever ported a suite of VB 6.0 Apps from 2003 to 2008? Is it like porting from XP to 7? The 32 bit apps are have ethernet and serial communications. Any advice will be helpful.

[HanneSThEGreaT]

I don't think it'd be too difficult. It is definitely not like Porting from XP to Windows 7. I'd suggest port one app at a time, so that you can test each one as you go. That's what I would do. Maybe the more clever people here will give better advice.

Good luck

[ahoodin]

Hi Hannas! Well the issue is that all the applications work on the same solution together, so not only do they have to work individually, they have to work in concert. Ok well if the port is not as big as XP to 7, that is great, but as you say there is still development effort necessary.

Yes I need luck. I did not write these apps, but I have to work on them.

[dglienna]

Security is locked down, a LOT tighter. The more you know, the easier it becomes. I'd suggest contacting Microsoft Support, and pay for a session. You pay once, and they finish it before closing the ticket. If there IS a way, they can find it. Otherwise, how about in a Virtual Machine? You can run ANY OS in Hyper-V and remote into it.

[ahoodin]

Well thank you Dgi, that is great. So it is mostly an act of getting the security correct on your Server. Well the virtual thing would not work because the server is a unit that is bought and shipped on-site to run machinery. Probably wouldn't fly with the End Customers.

[GremlinSA]

Quick question.. You continuing the Dev in VB6 ???

I've only ever done VB.NET apps on Server 2003 & 2008 , and they've been Services with out forms..

But previous experience has always shown that if you Compile the VB6 App on the OS you want it to run on (With out code changes) you have a Higher likely hood of it working without issues...

[ahoodin]

Quick question.. You continuing the Dev in VB6 ???

The company I am working for is. Why they never upgraded is probably because it was easier and
cheaper not to in the short run.

I've only ever done VB.NET apps on Server 2003 & 2008 , and they've been Services with out forms..

Oh wow. Wish these were....lol. Nope, some services, some full form based apps too.

But previous experience has always shown that if you Compile the VB6 App on the OS you want it to run on (With out code changes) you have a Higher likely hood of it working without issues...

Thanks, this is a good point!

[dglienna]

If you're shipping Windows Server 2008 R2, it includes HYPER-V. Just ADD the feature. Copy in the .VHD file, and configure it to start automatically. (I've done this remotely)

[dglienna]

btw - LogMeIn Resuce won't run on Windows Home Server (W2K8R2), nor W2K8R2 Server. Runs on any other OS, if you start with a browser based session...

EDIT: Also, there are NO supported sound cards for W2K8R2