I talked to my local Guru on windows / visual studio,
but here is a link even better:
http://www.codeproject.com/cpp/vcredists_x86.asp
the exe for redistributing MSVCRT80.dll is missing from the visual
studio express version. but MS has it for download, so the workaround
on that page isn't nece
Andreas Jellinghaus wrote:
Douglas, you experimented with the ID Ally CSP and got it
working with opensc, right? If so, could you tell me:
a) the CSP documentation states that not only the CSP but also
all dll's used by the CSP need to be signed by microsoft. I think
that is wrong, and
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.
th
Andreas Jellinghaus wrote:
How important is support for windows before XP?
If we would use VC8 with SxS directories for DLLs
and all those goodies, we would depend on windows installer 3.1
which to my knowledge is only for Win XP SP2, or would at least
require installing it on other plattform
On Tue, Aug 15, 2006 at 11:35:52PM +0200, Andreas Jellinghaus wrote:
> sorry, I'm still quite confused: manifests, SxS directory,
> windows installer 3.1 requirement, new CRT lib, etc.
I don't like any of those cherries very much, but I do like least
common denominator.
I may just be too Windows
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 informat
How important is support for windows before XP?
If we would use VC8 with SxS directories for DLLs
and all those goodies, we would depend on windows installer 3.1
which to my knowledge is only for Win XP SP2, or would at least
require installing it on other plattforms.
Also SxS directories only w
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.
--
Douglas E. Engert <[EMAIL PROTECTED]>
Argonne Nat
Wolfgang Glas wrote:
Am Montag, 14. August 2006 16:28 schrieb Douglas E. Engert:
Andreas Jellinghaus wrote:
Wolfgang Glas wrote:
1) Are there any good reasons to install the opensc dlls twice? (SCB
install directory and C:\WINDOWS\System32) Installing then only in the
SCB install direct
This is not the right way. You can learn a lot about the re-
distribution phase of the mentioned dll from msdn forums and just by
using google. Just 'putting it somewhere' is supposed to cause more
problems than it solves.
On 14.08.2006, at 23:27, Wolfgang Glas wrote:
My experience showed
Am Montag, 14. August 2006 16:28 schrieb Douglas E. Engert:
> Andreas Jellinghaus wrote:
> > Wolfgang Glas wrote:
> >> 1) Are there any good reasons to install the opensc dlls twice? (SCB
> >> install directory and C:\WINDOWS\System32) Installing then only in the
> >> SCB install directory should
Andreas Jellinghaus wrote:
Wolfgang Glas wrote:
1) Are there any good reasons to install the opensc dlls twice? (SCB
install directory and C:\WINDOWS\System32) Installing then only in the
SCB install directory should be IMHO sufficient, because all dlls on
which the opensc libs depeand a
I don't know any more what the issues exactly were, but I gave mingw a
try and didn't get very far. I guess we would need native windows header
files or something like that, and maybe a lot more from vs/vc, so there
would be no legal advantage in using mingw.
currently scb contains openssl, open
Wolfgang Glas wrote:
1) Are there any good reasons to install the opensc dlls twice? (SCB install
directory and C:\WINDOWS\System32) Installing then only in the SCB install
directory should be IMHO sufficient, because all dlls on which the opensc
libs depeand are installed alongside in the sa
On Sat, Aug 12, 2006 at 10:35:49AM +0200, Wolfgang Glas wrote:
> Therefore, it would be more feasible to use either mingw (is this
> fully supported by now?)
I also think this is a good idea. I would have made some experiments
but haven't found the time.. Please feel free to try it out.
If it wo
Hi,
I installed SCB-0.7 from the homepage and updated the contained opensc
library to the current SVN by compiling opensc on my own using VC++ 8.
Everything went fine, until I tried to use opensc-pkcs11.dll from within
JAVA, which did not work.
After several hours banging my head against a
16 matches
Mail list logo
