VNET_Tutorial_2_en -- dll is not found ?

[Joakim Schramm]

Hi, 

> -----Original Message-----
> From: valentina-bounces at lists.macserve.net 
> [mailto:valentina-bounces at lists.macserve.net] On Behalf Of 
> Ruslan Zasukhin
> Sent: 03 July 2006 14:09
> To: Decoster Jean Louis; valentina at lists.macserve.net
> Subject: Re: VNET_Tutorial_2_en -- dll is not found ?
> 
> On 7/3/06 2:32 PM, "Decoster Jean Louis" <j.decoster at se-dd.com> wrote:
> 
> Hi Jean,
> 
> > Hi Ruslan,
> > 
> > It was for me of a great help. I have used depens.exe utility and 
> > could immediately see something very interest. The failure 
> occurs on 
> > the machines where the following dll are already stores on 
> the directory Windows\system32:
> > -icudt30.dll 08.März.2005
> > -icuin30.dll 08.März.2005
> > -Icuuc30.dll 08.März.2005
> 
> Interesting...
>  
> 
> > Are there problems for valentina software by storing these 
> dll's from 
> > system32?
> 
> ? 
> 
> Your dlls have 30, so generally speaking should work ...
> We also use 30 currently...
>  
> Note, that in your FINAL release, you should prefer put all 
> Valentina and ICU dlls into EXE folder, so they will not 
> conflict to other dlls.
> 

I don't totally agree about this, System32 is the folder to put dll's in
used by several instances of the system and a databse product I think is a
strong candidate for being used by more then one program.

I personally have 5 programs that will use Valentina and putting the dlls in
each of the programs exe dir is a waste of users disc resurses I cannot
defend, expecially with the big size forprint these dll's have.

A proper setup program should install only newer versions of dll's according
to file version label, and new versions should always be backward compatible
as long as same name is used. I suppose this is the true case with Valentine
dll's?

I have been thinking of this myself as I am approaching release time, wether
to put them in System32 OR a subdir of System32... The COM docs "Deployment
of your application" say as second suggestion:

2) Valentina folder is located in the system area.
This way is the same as you have it now during development. VComponents
folder is
located in the central place of OS where any application can find it.
This way can be choosed if you develop several small applications that all
use Valentina.
Using this way you have VComponents folder only in one place on a user
computer. 

Is this your recommendation to put the whole folder in System32 rather then
just the files? I would like to hear who others using com dll's deal with
this? It would be good to have an "offical standard" to avoid putting dll's
"all over the place"...

I am aware of the so called "dll hell", but I personally think this is more
a problem with badly written installers then dll's and system32 it self. The
windows regestry have a reference count of installed and uninstalled
programs incl. dll's so if setup is don't correctly there is no "hell".

Regards,
Joakim