This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, We have been intermittently experiencing 15 sec Dispatcher hangs on instantiating Mindscape components on XP machines. Here is the stack trace of the lock up: at System.Security.Cryptography.X509Certificates.X509Utils._GetOidFromFriendlyName(String oid) at System.Security.Cryptography.CryptoConfig.MapNameToOID(String name) at System.Security.Cryptography.X509Certificates.X509Utils.OidToAlgId(String oid) at System.Security.Cryptography.RSACryptoServiceProvider.VerifyHash(Byte[] rgbHash, String str, Byte[] rgbSignature) at System.Security.Cryptography.RSACryptoServiceProvider.VerifyData(Byte[] buffer, Object halg, Byte[] signature) at #Yc.#Zc.#od(LicenseContext context, Type type, String licenseKey) at #Yc.#Zc.GetLicense(LicenseContext context, Type type, Object instance, Boolean allowExceptions) at Infralution.Licensing.PublicEncryptedLicenseProvider.GetLicense(LicenseContext context, Type type, Object instance, Boolean allowExceptions) at System.ComponentModel.LicenseManager.ValidateInternalRecursive(LicenseContext context, Type type, Object instance, Boolean allowExceptions, License& license, String& licenseKey) at System.ComponentModel.LicenseManager.Validate(Type type, Object instance) at #lu.#Zd.#1d(Object sender, RoutedEventArgs e) at #lu.#Zd.#de(Type type, FrameworkElement instance) at Mindscape.WpfElements.NumericTextBox.#7d() at Mindscape.WpfElements.NumericTextBox..ctor() at System.Xaml.Schema.XamlTypeInvoker.DefaultCtorXamlActivator.InvokeDelegate(Action`1 action, Object argument) ..................... Investigating it seems to be this issue: http://www.pcreview.co.uk/forums/thread-3428177.php It looks like we can workaround it by adding the XML from the article to the machine.config file. This is only on a machine by machine basis. Is there anything you guys can do? Thanks, David Anderson
|
|
|
|
|
Hello Dave, Unfortunately from looking at the analysis at the link you pointed to, I don't think there's anything we can do about this issue. Worse still, whoever wrote the CryptoConfig class decided to hardwire it to look at machine.config rather than using the normal .NET configuration hierarchy (thanks, Microsoft), so you can't even work around it by putting the entries in app.exe.config where you can deploy them alongside your application. The best solution therefore depends on your deployment method. If you are deploying via an installer or Group Policy, you can make the machine.config changes as part of that. If you are deploying via xcopy, you can check for the machine.config entries during app startup, and if they're not there then write them into machine.config before the window constructor runs (I think this will be early enough... if not then the app may need to restart itself after writing the entries). The latter will require admin privileges which is why doing it at install time may be preferable, though if you're only seeing the problem on XP then this may be less of an issue. |
|
|
|
|
Hi Ivan, We've had a machine now that editing machine.config doesn't fix. I've found this KB article: http://support.microsoft.com/kb/948080 Are you able to use the fix from the article? Thanks, David |
|
|
|
|
It's fixed in your 2.0 version :) |
|
|
|
