Friday, June 18, 2004

IMF Archive Manager 2.0 Beta

I've been working on IMFAM during my spare time to address the feedback I've been getting. I believe the Beta is now ready, but as fate would have it, GotDotNet appears to be having problems.

So for now you will just have to salivate over what is going to be in it as opposed to trying it out:

Delete Key mapped to Delete Button for those that are mouse imparied (like myself).

Several rendering bug fixes for particular (corrupt?!?) messages.

Automatic Refresh time exposed in the xml configuration file. In addition, Automatic refresh no longer reloads the message pane, so if you are editing a message, you won't loose your changes.

NEW VIEW! I've added the ability to switch from the original tree view to a new list view. The new list view allows column reordering, column sorting, and multiselect. Multiselect actions are limited to delete at this point.

Better loading experience. For both the old view and the new view I added a Application.DoEvents() in the loop that populates the views. This will allow you to start working without waiting for everything to reload. One additional feature for the ListView is the entire list is not reset during automatic refresh, just new items are added.

Wednesday, June 16, 2004

Intelligent Message Filter Release Notes

Intelligent Message Filter Release Notes

For those running into issues with IMF, an updated README has now been published. This includes a FAQ that covers most issues you may have.

Thursday, June 10, 2004

MissingManifestResourceException

What a pain in the butt! I was working on getting the IMF Archive Manager working for globalization when I suddenly ran into this. I have two forms, main and report. The main report I took care of without a hitch, but as soon as I turned localization = true on the report form, the app would throw a MissingManifestResourceException when it loaded.

There were several articles that I read that could cause this problem, but none of them offered a solution or the solution didn't apply. After some digging I realized that my main form resource file was being generated as Microsoft.Exchange.Tools.IMFArchiveManger.frmMain.resources where my report form was being generated as IMFFilterManger.Report.resources.

The fix was as simple as going into the project settings and changing the default namespace from IMFFilterManager to Microsoft.Exchange.Tools.IMFArchiveManager and then suddenly everything started working.

God I hate dumb things like that! :P