VB 6 and Vista? 1

[pungy]

Current OS: Windows XP Professional SP3; Visual Basic 6 Enterprise Edition; Crystal Reports XI Developers Edition

I sure this subject has been beaten to death but I still here of conflicts.

I have developed and installed VB apps that were developed in VB6. Many of these apps call Crystal Reports. These applications are installed at a customer site that has Windows XP (Home and Professional editions).

My question is: If I, on my developement PC, update to Vista Home, will I still be able to use VB6 without any problems? Will I be able to develop apps on a system who's OS is Vista and will those apps be able to be executed on a system that has Windows XP (Home and Professional editions)?

I am a retired individual and only have one PC. Either I stay with Windows XP or go with Vista.

Thanks,
Sam

 

[ousoonerjoe]

Personally, i'd stay with XP Pro for now. Since most of your customers are using XP. When your client base becomes primarily Vista, THEN I would adapt to meet the needs of my clients. Till then, "if it ain't broke, don't fix it" applies.

"If I were to wake up with my head sewn to the carpet, I wouldn't be more surprised than I am right now.

 

[dilettante]

There are several things that almost require development under Vista in order to create a proper Vista program.

For example the DHTMLEdit control was withdrawn due to vulnerabilities, and later a hardened version was released for post-installation into Vista. However the package for this new DHTMLEdit control will not install under XP or 2000. So unless you develop under Vista you can't build a setup package using DHTMLEdit that can install on both XP and Vista - at least not legally.

Another advantage of development under Vista is it will encourage you to adopt long-standing Windows guidelines that were not enforced by the OS until Vista. So a program developed under XP might work for Vista users after Vista applies appcompat shims but it might not, or it might work with a few quirks.

I have found that it is much easier to develop under Vista if I expect to have any Vista users. I also use VirtualPC which lets me test deployment and operation against a clean image of Vista, XP, and Win2K - and in one case even Win95. You need the extra OS licenses, but not a pile of physical machines.

This also means I can incorporate new Vista features, and in most cases sense the OS and "downgrade" where necessary. It also opens up possibilities that didn't exist until Vista. For example there are new Shell Integration options like the Explorer Preview Pane that you cannot develop for under XP.

 

[pungy]

dilettante: You supplied me with some very good information. I use to teach VB and was certified by MS for VB 3,4,5,and 6. SO I am aware of what you are saying.

For the past couple years I have been retired and now only do developement on a part-time basis. I've decided, for now, I am going to stick with Windows XP Professional. I'll leave the newer stuff to the younger generation.

Again, I would like to thank you and ousoonerjoe for responding.

Sam