Andreas Jellinghaus wrote:

Douglas E. Engert wrote:

P.S. Here is a nice blog about the dll hell problem, VC++8.0
and WinSxS

http://blogs.gotdotnet.com/martynl/archive/2005/10/13/480880.aspx

It also meantions Inno and NSIS instal packages, that don't
know how to handle the assemblies.


thanks, that link was very informative!

so it looks to me like we should better wait with manifests and
SxS installation of DLLs until the tools know how to do that
properly and other people have written examples/howto/docs
about all that. no need to get bloody noses by trying the latest
stuff (unless anyone volunteers - I don't want to stop you :).

Best choice might be VC++ 6.0 for the next release.

Then wait untill the installer people figure out how to install the
VC++8.0 runtime.


can we use VC8 with traditional means? i.e. only compile the
dlls and programs as we used to and install them like always?
would the manifest help in this case? or cause a problem?

I have not seen a magic switch on VC++ 8.0 to not use the
manifest to locate the msvcrt80.dll, and it might not be a good
idea to just copy msvcrt80.dll to system32.


sorry, I'm still quite confused: manifests, SxS directory,
windows installer 3.1 requirement, new CRT lib, etc.
not sure which part depends on which and if we can
cherry pick some and leave out others etc.

Regards, Andreas



--

 Douglas E. Engert  <[EMAIL PROTECTED]>
 Argonne National Laboratory
 9700 South Cass Avenue
 Argonne, Illinois  60439
 (630) 252-5444
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to