I apologize for this: https://github.com/stephenegriffin/mfcmapi/issues/29. Large icons were not intentional. As evidenced from looking at every other application I’ve looked at, high DPI is hard.

Please continue to report issues on Github. Codeplex is only being used to host our download. Issues reported there may or may not ever be seen (if I could turn off issue reporting on Codeplex I would)..

Enjoy.

So – I managed somehow to let a year go by without a new release. I hadn’t stopped hacking on MFCMAPI. To the contrary – I completely rewrote all of the string handling to something a bit more modern than naked LPSTR. I also fixed that nasty bug some of you may have seen on Windows 10 – the empty error dialog when you roll over the wrong menu item.

More importantly though, I’ve overhauled my build and publication process. MFCMAPI source is no longer hosted on Codeplex (sniff). You’ll find it over on Github now:

https://github.com/stephenegriffin/mfcmapi

Fortunately, I was able to migrate the complete source history, so it barely stung at all when I checked in the deletion of the source on Codeplex. Feel free to head on over to Github and party. I’m open to pull requests. This is my first project on github, so if I’m not doing things “the right way” just let me know.

I’ve also migrated my build process up to Visual Studio Team Services. I had intended to set this up on a public server, but I see now it’s still private. I’ll have to look in to migrating it. But what I’ve gained is:

• Continuous integration: I get a build on every check in
• Nightly builds: I build every possible variation of the project every night
• One click build and publication to Codeplex

That last one is the crown jewel. In one action I can kick off build, package, and deploy to Codeplex. All I have to do then is check it over, write the blog post, and unhide it. Now I have zero excuses for not publishing updates more often.

I’ll forgo the change list. You can see what I’ve done up on Github.

Enjoy.

It’s amazing – how much I don’t get to work on MFCMAPI when I’m no longer in Developer Support. That’s no excuse for leaving it alone for a year! I did patch quite a bit in the past year.

Here's a change list - see the Issue Tracker and ChangeSets on Codeplex for more details:

• SmartView: Completely rewrote the engine to be much more modular and easier to maintain
• MrMAPI: Fixed several crashes, leaks, and hangs
• Migrated a metric ton of old CString and manual string handling to wstring
• Performance: Did a whole bunch of performance tweaks – everything should be much snappier

Enjoy.

Suppose you wanted to use this to output the display name of each account in the profile. You could do this (note that 0x3001001F is PR_DISPLAY_NAME):

C:\>ProfileProp.exe 0x3001001F Profile Property Tool Profile: Outlook Property: 0x3001001F Examining account Microsoft Exchange         Located property                 Property tag: 0x3001001F                 Value: sgriffin@example.com Examining account Microsoft Exchange         Located property                 Property tag: 0x3001001F                 Value: sgriffin@example.example.com

I haven’t implemented property name lookup like in MrMAPI, and I probably won’t. You can get the sample here.

Enjoy!

It’s been a chaotic half year and I haven’t been able to get my builds out as often as I’d like, though I did do a ton of work on MFCMAPI.

This month we get a totally rebuilt MAPI property parsing engine. As it’s an engine change, you shouldn’t notice much different in MFCMAPI itself, but all of my XML exports get an upgrade.

Here's a change list - see the Issue Tracker and ChangeSets on Codeplex for more details:

• Property Parsing engine rebuilt
• MrMAPI: Fixed malformed XML in profile list when no profiles exist
• Adding attachments is now possible
• MrMAPI: Can now dump the receive folder table
• Export now includes large props by defalt
• SmartView: Understands PR_PREDECESSOR_CHANGE_LIST

Enjoy.

https://mha.azurewebsites.net/manifest.xml

For the rest, I’ll put some instructions together later.

Enjoy!

This script, set through Image File Execution Options, attaches Procdump.exe to your process every time it starts, so it can listen for exceptions and write dump files when interesting ones occur. It also captures Procdump’s debug spew in a log file which you can use to identify first chance exceptions that you'd also like to get dumps for. Once enabled, you'll just need to visit the user's machine periodically to collect the dumps and logs for analysis.

To use this script, create a file called DoProcDump.cmd and place it in c:\tools alongside procdump.exe (you can configure these paths differently if you like, but you’ll need to modify the script) and then create an entry under Image File Execution Options. Next time the user starts the process, Procdump will attach and listen for exceptions. There are a number of ways you can change up the data collection, such as enabling first chance exceptions, or getting dumps on process shutdown (useful for silent exits, though this is even better). Look at the comments in the script to see how to enable and configure these.

To disable this script, just remove the reg key you created under Image File Execution Options.

BTW, I got the unique file name code from here: http://blogs.msdn.com/b/myocom/archive/2005/06/03/creating-unique-filenames-in-a-batch-file.aspx

Enjoy!

@ECHO off
REM *****DoProcDump.cmd*****
REM Configure this in Image File Execution Options like so:
REM [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\Outlook.exe]
REM "Debugger"="cmd /c c:\\tools\\DoProcdump.cmd"
REM (Double \\ are how \ are represented in .reg files. If setting this value manually, use single \.)

REM Change these paths to reflect the location of Procdump and the location to which the output files should be written.
REM Data collection should include .dmp files and all procdumpOutput*.txt files written to the out path.
set PDOutPath="C:\tools"
set PDExe="C:\tools\Procdump.exe"

REM Only enable one of the following.
REM Use this filter to catch only second chance exceptions.
Set PDFilter=/e
REM Enable this filter to catch specific first chance exceptions in addition to second chance exceptions.
REM Set PDFilter=/e 1 /f "System.Threading.ThreadAbortException" /f "System.AccessViolationException"

REM Configure the maximum number of dumps to gather here.
Set PDNumDumps=5

REM Enable this also gather dumps on process shutdown.
REM Set PDTerm=/t

set PDCfg=/ma /n %PDNumDumps% %PDTerm% %PDFilter% /x

@ECHO *************************************************************
@ECHO *                                                           *
@ECHO *               DO NOT CLOSE THIS WINDOW!                   *
@ECHO *                                                           *
@ECHO * This window will close automatically  when Outlook exits. *
@ECHO *                                                           *
@ECHO *************************************************************
@ECHO.
@ECHO Running: %PDExe% %PDCfg% %PDOutPath% %*

REM This generates a good file name for our log file.
for /f "delims=/ tokens=1-3" %%a in ("%DATE:~4%") do (
   for /f "delims=:. tokens=1-4" %%m in ("%TIME: =0%") do (
      set LOGFILE=%PDOutPATH%\procdumpOutput-%username%-%%c-%%b-%%a-%%m%%n%%o%%p.txt
   )
)

@ECHO %* > %LOGFILE%
@ECHO Current time %TIME: =0% >> %LOGFILE%
@ECHO Running: %PDExe% %PDCfg% %PDOutPath% %* >> %LOGFILE%

%PDExe% %PDCfg% %PDOutPath% %* >> %LOGFILE% 2>&1