CAPICOM has finally been deprecated, and it won't be supported on Windows 7. This link is up to date and proposes alternatives to CAPICOM classes by using .NET classes and CryptoAPI: Alternatives to Using CAPICOM.The following article may help if you were using CAPICOM in your web site and you are planning on using .NET now: Writing an ActiveX Control in .NET.
I hope this helps.
Alex (Alejandro Campos Magencio)
Can you please tell me whether we can redistribute the Windows 7 version of SignTool.exe with our software?
We created a win32 application using capicom.dll for using webservices. Windows 7 does not support capicom.dll is said, but strange is that a lot of windows 7 users do not have any problem using our application and capicom.dll (even 64 bit) and some other do have problems. Is there a difference in windows 7 versions, upgrades?
Non-supported mainly means that it may work or not, but if it doesn't, there is nothing we can do.
Additionally, non-supported products won't get i.e. updates.
As far as I can tell, there is no story on how to move to using e.g. SignerSignEx - no C++ sample code and especially no .NET P/Invoke sample code.
The framework can't read certificates directly from smartcard but from localmachine area. This is a problem when more users work on the same computer because this area mantains the certificates.