CAPICOM throwing FileLoadException

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm trying to do a foreach loop of each Certificate in a Certificates
collection. Note: This worked perfectly yesterday, and today it
started throwing a bunch of exceptions.

basically C# says that CAPICOM.CertificatesClass.GetEnumerator() is
throwing the exception, saying that "Unverifiable code failed policy
check. blah blah blah"

What is going on here?


heres the code:

foreach(Certificate currentCert in certs)
{
try
{
localMachineStore.Remove(currentCert);
}
catch (System.Exception e)
{
writeToLogFile(e.Message);
}
}

.

Relevant Pages

  • Re: Damn you, FEDEX! or Nikon D40 lost in Springfield, MO blackhole.
    ... the 2 mp Mavica he had been using with a Nikon D40. ... After shopping around, he got me to order one for him. ... The shipper had it insured, but from what I have read it could take weeks to sort this crap out. ... You may get your insurance from FedEx and a couple weeks later they find it and deliver it. ...
    (alt.photography)
  • [Fwd: Re: [Full-Disclosure] MCSE training question]
    ... A certificate is not just like a degree. ... , blah blah blah ... closer attention to the candidate with those letters. ...
    (Full-Disclosure)
  • Re: Templates not showing in Web enrollment
    ... Now if I go into Webenrollment and click Request a Certificate it goes ... Submit a certificate request by using base-64- blah blah ... I click the "Create and Submit and request" and the only template option I ...
    (microsoft.public.security)
  • Re: ContextSwitchDeadlock error in VS2005
    ... Choose Debug from the categories list and drag ... Then, close the dialog, click Exceptions and uncheck ContextSwitchDeadlock ... under Managed Debugging Assistants. ... Exceptions, blah blah blah ...
    (microsoft.public.vsnet.debugging)
  • Re: ContextSwitchDeadlock error in VS2005
    ... You can add the Exceptions menu item to your Debug menu by clicking Tools-Customize. ... Then, close the dialog, click Exceptions and uncheck ContextSwitchDeadlock under Managed Debugging Assistants. ... Exceptions, blah blah blah ...
    (microsoft.public.vsnet.debugging)