We have a software application that uses the Xceed Zip Compression Library. For several versions of our software we have not included the code to register the XCeedZip object that we use – because we were unaware that we were supposed to use the “.Register” method. However, now we are having problem with an XP machine where it is requiring us to us the “.Register” method.
This leads me to the question of fixing the problem. When exactly do you need to use the “.Register” method?? Is it only on XP machines?? The more information I know about this, the less headache I will have in knowing who this might have effected – and who might need to run a service pack.
Imported from legacy forums. Posted by pjflickinger (had 2924 views)
I figured it out! and it is a simple answer to a dumb question.
The problem is not XP-specific, it is all the OSs I install with. I traced the problem down to the fact that the new version of the EXE was compiled on someone else’s machine. So there is two possible solutions.
1) That person’s machine either did not have the XCeed library installed or registered 2) they had it registered with a different License Key then I did – and I create the install – so the dll we repackaged for distribution did not match the License Key that must be compiled into the EXE.
Therefore, I do not really believe it is necessary to use the “.Register” method. It was just an error we received due to bad development.
Sorry for any headaches! Hopefully someone will learn from our mistakes.
Imported from legacy forums. Posted by pjflickinger (had 320 views)