dll and dep file problems while building project,, HELP !

[locutus]

I have recently downloaded the latest comctl32.dll from the microsoft site and installed on my machine.
When I try to use the set up wizard to build and create dependancy file for the project I get the message,
"The dependency file for the following components is out of date.
You should exit the wizard now and rebuild each of the dependency files for these components, using this wizard."

I am stuck how do I do this, I spoke to a college in my office who also has had this happen, he said that it is because the dep file and the dll file for the components do not have the same date , I looked in the system32 dir and this is the case. Is this what is causing the problem ? also why doesn't the microsoft patch include the dep file ?

How do I get round this problem , any help would be appreciated.


also, having had a few problem with VB lately I have become slightly disalusioned with the whole package. Its not writing code thats the problem, its what happens afterwards with incompatabilities between machines running the same apps written in the same version of VB but on different machines, problems with dll's , ocx files etc. There just seem to be a lot of hassles that go with VB.
I don't want to upset you guys ! as you are obviously VB professionals and enthusiasts but do you thing a large company like mine should go down the VB applications route for shop floor systems or should we go with delphi or C++ with a builder front to develop our next generation applications. Would they be more robust ?
We had a development meeting recently to discuss the future applications and it is open ended.
Any experiences or comments would help a lot, personally I have never had much bother with delphi or C++, I am only now starting to use c for accessing api's so will no doubt uncover some more problems there!.

Thanx Locutus

[bsmith]

I understand your problem. At my compay we have the same problem with DLL's overwritting others and applications not running because another was installed. It is not a VB problem. You'll run into this problem no matter what you use. The only thing I can suggest about using VB is when a project starts make sure that all developers have the same versions of software and SP's applied to their machine. When it comes time to distribute the application, build the install from one machine. You might also try a third part like Install Shield for building installs.


As far as your problem with .dep file, I usually try to find a machine that has the correct .dep file and copy it to my machine.


Good Luck