.NET version issue in crypto?

cryptographic service provider (csp) for this algorithm...

[realmofillusions]

Are there known version problems in the csp module? Second time this has come up. Nothing unusual in the code, uses the DES algo. Problem as follows:
System.Security.dll
compilation machine version = 1.0.3705.0
target install machine version = 1.1.4322.573

exception thrown = "Cryptographic service provider (csp) for this algorithm could not be found."

rather than force enforce .net compatibility (wasnt .net supposed to banish this bugaboo from the kingom forever?), im thinking the better solution is to reference the library directly, and set to 'copy local'
If this works Id like any information anyone has on why the incompatibility exists, and what is considered to be the most recent stable version of the library.

Thanks.

VLG
r.i. software developers

[Ocean10000]

Dot.net System.Security Namespace relies on the unmanaged Crypto Providers installed on the machine. So my understanding is that on the machine you are running this app on, the Crypto Provider is not installed or was not abled to be used for some reason.

[realmofillusions]

Thanks,

You probably saved me another 1000 failed attempts. Server is a fresh 2000 install, but there are service pack discrepancies between the development machine and the target. Any wisdom written on how to handle this possibility in commercial applications? I can update the service pack on the test server, but was hoping to avoid any dependencies in the installer.

Sincerely

VLG

[Ocean10000]

Well I usually put a disclaimer in the documentation in an odvious spot that the server that my software is being installed on should be of xyz service pack level. And provide a link on how to check if the server has any service packs installed and what version they have. Aka I keep my installers dumb as I can, and just make sure the person installing has some brains.

[realmofillusions]

"and just make sure the person installing has some brains. "

Well, there go my government contracts...LOL

That was it by the way. Interestingly, it only seems to affect the 3DES csp. Another app using MD5, works on the base install. Im going to backtrack and see if I can find any references to exactly what the change to the library was, while I ponder whether or not It might not be better to write a 3DES module.

Thanks again,

VLG

[Ocean10000]

My Guess it was added to the Crypto Libs after the intial release, and later only include in a service pack once it passed review, and testing. I rather have them get the crypto stuff right the first time. Crypto stuff is way too easy to get wrong if done in haste.