Deploying VB Apps

I have a general question about deploying VB apps to run on a variety of platforms.  

I gather this is a complex issue, yes?  no?

I ran into a problem deploying a VB app built on my XP Pro machine, when I tried putting it onto a Windows 98.  My installation package included a DLL that would not run on Windows 98.  The specific DLL is the Microsoft C Runtime Library (msvcrt.dll).  I assume this is just one example of the general problem of managing VB apps to run on a variety of platforms.

I assume there must be some well-known basic approach to managing this problem.  Can anyone provide the ABCs for how to do this?

As always, any information will be gratefully appreciated.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It sounds as if the .dll you supplied wasn't backwardsly compatible, which I think is a big irritation caused by Microsoft.

I wish I had a clear answer for you, other than to say yes it is a complex issue.  Supposedly to be improved by .net technology though.
DanimalAuthor Commented:
That is good to know I am not completely uninformed to think this is a tough issue.

But, there must be some standard way of dealing with this, yes?  It is that standard approach I am looking for.
Richie_SimonettiIT OperationsCommented:
Welcome to "dll hell" :(
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

DanimalAuthor Commented:
I thought I noticed a sign saying "dll hell" as I entered into this question..  lol :-)

I have a feeling I got off fairly easy with my dll problem this morning.....

....still no suggestions on the basics for coping?

Software companies seem to ship software that installs do they do it?

Deploy Ur Program on Win 98

resulting setup file will work 'EASily' on XP
as Package & deployment wizard will not over write New DLLs
Richie_SimonettiIT OperationsCommented:
Bahnass, not a bad idea but i think you did want to say:
"package" your app in win98, is that right?

Anyway, sometimes the setup program doesn't likes to install some dll (in fact, msvcrt.dll is one of them), if they are in use.
Maybe that dll is backward compatible but since it is in use... ( and i hope that setup not overwrites new one with old one!!)
Richie_SimonettiIT OperationsCommented:
Other way could be not package that dll since it is present on almost any Windows OS ("Done" by Bill Gates, i mean)
>Software companies seem to ship software that installs ok

No, they have many problems.

>But, there must be some standard way of dealing with this, yes?

MS standard way is ... to break their own COM rules.  You don't want to go that way.

If there is a known conflict (newer version of some component is not compatible with previous version) - the best way is:
- give older version in setup package and provide newer version of the component via your web site

Companies often go the other route - "always install the last version of everything and force users to do the same" but that can break other people's software.
DanimalAuthor Commented:
ameba, I think you are starting to get at what I am looking for.  However, I want to make sure I understand:

Almost any software I install on my puter runs fine.  I basically never have a problem.  I am running XP Pro.  That fits with what you are saying, because I have all the latest stuff (at least for now)?  

People running Windows 98 run into probs with new software all the time?  

Regarding the practice of always giving the older version in setup package....what happens if someone has a newer version on their machine already?  The installation will skip that file?  How can you rely on the installer to do that and not replace the newer version with the older one?

One more thing:  what is the reason for putting the latest version of the dlls on your website?  How does that help your customers?

Look into using the Visual Studio Installer. With this you can include the WinNT or Win98 (or what ever) drivers and only install the ones that apply to the OS you are installing in.

This selective install is controlled using the "Condition" field for the file you are trying to install.

If your DLL is an ActiveX DLL there may be more issues and late binding may be required (using CreateObject) If it is a standard DLL and the WinNT version is not named the same as the Win98 version you will have to do some conditional compiling and make 2 different executables to release (not sure on any way to conditionally declare different dll files without creating 2 or more exe files.

If you end up with more than one exe, you can use the "Condition" field to install the proper version in your single installer pack.

>Regarding the practice of always giving the older version in setup package

It is not that simple. There isn't any "always" you can simply use.

>Almost any software I install on my puter runs fine.

You are just being lucky, there are many, many problems with XP.

>what happens if someone has a newer version on their machine already?

During install, if newer version is found on computer, older version will not be installed automatically.

The problem is if there is an old version on PC, and NEW version, which did NOT RESPECT RULES, is to be installed - this will be done automatically *WITHOUT* asking user "You have version 1, do I overwrite it with version 2 ?"
After version 2 is installed, all the software which worked correctly with version 1, will stop working!  One different interface definition and ciao...

Of course, new software, just installed, will work with the new version.
Old software will be invalid, killed by the new, shiny app.  Is this fair?  Whose fault is this?
Component producer made a mistake, of course.  But if you know the component will cause big problems, e.g. some important applications will stop working, using it is also YOUR FAULT.

What to do:
If new bad component is in use on 95% computers, the minimum trouble you'll have if you go with the new bad version.
If you received complaints on other applications destroyed:
   "We paid $100000 for XY app, and now your free Calculator prevents it from running"
- ship old component in setup
- this will not cause other applications to stop working and this is THE MOST IMPORTANT THING
- your application will not work if there is already new bad version installed
   - you are aware of the problem and you make a FAQ and a special download

"PS We do not include MFC version 6 DLLs in the default setup of SAGE-CRISP
as they are likely to cause problems for other third party applications."

Of course, the best route is not to use any component which cannot be controlled.  Make all the components yourself.  From MS you should use only SYSTEM COMPONENTS.  Forget MSChart, MS Calendar, FSO,... or expect trouble.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DanimalAuthor Commented:
Thanks for the intro to the topic....

just what I was looking for....

...sounds like a lot of bad news...

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.