Firetrust Support Forums

Cannot create instance of 'CustomDataGridControl' defined in assembly 'MailWasherPro, Version=1.0.6.0, Culture=neutral, PublicKeyToken=null'. Exception has been thrown by the target of an invocation. Error at object 'GrdMailGrid' in markup file 'MailWasherPro;component/mailgridandpreview.xaml'.

MessageBox at startup. Win7. Hmm?

Hi there

Try repairing your .NET install. In Control Panel >> Programs and Features >> look for the Microsoft .NET Framework entry, likley version 3.5 >> select Change/Uninstall >> you will get the option to remove or repair >> select Repair and follow on screen prompts >> reboot afterwards >> try MailWasher...

You may already have M$ .NET Framework 4 Client Profile installed. It seems to override any previous versions of .NET Framework. I am running W7 Premium 64 bit and it came installed. Just a hint.

Damned computers (tm). Tried repairing the .net 4 client profile. No joy. Uninstalled/reinstalled MW. No joy. Went on vacation. Joy.

The current situation is: boot computer. Try launching MW2010. Error message. Launch again. Error message. Do some work, surf the net. Launch MW again. Works. Can close down and restart MW until next boot when it all happens again. WTF, mate? This behavior is consistent for some days now.

Cache? GAC issues? Have half a mind to try gacutil to get the Xceed DLLs into the GAC. I have enough experience to know that some things are not easily explained. Another thing is that this machine is my own development box, so there are even more unknowables.

Well, MW 10.5x still works and they both coexist. Sigh.

In your C:\Users\[username]\AppData\Roaming\Firetrust\MailWasher there will be an error.log file, if you can send us this to [email protected].

Though no doubt you'll make more sense of it than I would, but the programmer will hopefully have some ideas

Mea culpa. Mea maxima culpa.

Error log is the clue.

Run a startup program I wrote, kills selected cookies, flash cookies, clears tmp directory. Oops. Under certain circumstances, it removes the directory pointed to by %tmp and %temp. And oops, MW uses that and dies a horrible death if it can't find it. After computer booted for a while, other programs recreate that directory, MW runs fine. Explains all. Fixed my program, all is well.

My bad. Error log good.

We use the temp folder ? ....

Actually I don't think MW does per se, but as the problem was related to creating an instance of the Xceed grid control, it might attempt to set something up in temp directory during initialization. Computers are dark and mysterious beasts.