I thought that I would report my solution to Microsoft CAPICOM versus Apache Xerces
incompabilities. I learned how to call a C++ DLL from Visual Basic, then wrote a
small C++ DLL wrapper to streamline use of the Xerces functionality I needed.
Short answer: I'm no longer using MS CAPICOM. :)
A
cc: (bcc: David N Bertoni/Cambridge/IBM)
Has anyone attempted to use Xerces' Base64 output with another Base64 encoder? I have
a Visual Basic project which is forcing me to use Microsoft's CAPICOM Base64 encoding,
and I'm getting some strange results. I can take CAPICOM-encoded output and
successfully decode it with
gzilla/show_bug.cgi?id=7243
Base64 encoding is not working
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=7243
Base64 encoding is not working
--- Additional Comments From [EMAIL PROTECTED] 2002-03-19 17:06 ---
Andreas,
The fix to the bug is available in the CVS repository, please help verify
and close the bug if it works, thanks.
Rgds,
P
gzilla/show_bug.cgi?id=7243
Base64 encoding is not working
[EMAIL PROTECTED] changed:
What|Removed |Added
Summary|Base64 encoding ist not |Base64 encoding
gzilla/show_bug.cgi?id=7243
Base64 encoding ist not working
Summary: Base64 encoding ist not working
Product: Xerces-C++
Version: 1.7.0
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority:
