Mike Hodnick

Awesome.  I often find myself cracking open NotePad and dragging a file into an untitled document, which was easy enough.  But this makes it that much easier and I'll be doing this from now on.  Make sure you don't type a space in "SendTo" like I did my first time.  That directory doesn't exist ;)

heh, we tried...

I'll remember to make lots of Office Space references if I'm ever interviewed by you ;)

It has been a long time since I interviewed people, but I used to always ask candidates if they had any questions for me, and they almost always said "no". I didn't look very favorably on this - especially since I typically was conducting the technical interview, and their time with me was their best opportunity to find out what it was really like to work at our company. Candidates who could actually ask me thoughtful questions scored much higher marks with me than those who said "uh, no thanks".

Your question is good, and I agree that candidates should be better prepared for it!

When I was interviewing I like listening to what they have to say about their passions... so I always ask about their favorite classes, favorite things about development, favorite projects.

I love working with passionate people...

If you don't click on something right away Tom gets kind of impatient.  Kind of funny...

Worked perfectly. In fact, I simply used the detect and repair option and Hodnick's suggestion worked. THANK YOU!

Thank you very much for the clear and great help! it works perfect

Cool - worked perfectly thanks

Mike, you are THE Office STUD!!!  Can't thank you enough....

Alternatively, go to C:\Program Files\Common Files\System\MSMAPI\1033 and delete MSMAPI32.dll and restart Outlook. It will automatically reinstall the file for you without needing to run the Office setup.

You just got Wired!

(c) The Wire.

Much more help than the "fixmapi.exe" from Microsoft.  Works like a charm -- thanks man.

Thank you, thank you thank you...for the tip on solving the MAPI32.dll wrong version error after uninstalling Office 2007 .

I had my brains burnt for one week when I could not get into my Outlook at the office, despite following Microsoft's advice to keep on reinstalling outlook.

It fixed my problem IMMEDIATELY.

You saved my life, cyberspace speaking.

One I find myself using a lot after I found out about it is Ctrl backspace/delete.  It will delete backward/forward to the beginning/end of the word.  So if you have let's say  someObject.somelongwordMethod(), get the cursor in front of the M, hit ctrl backspace, and somelongword is gone.  Much faster than using the mouse to try to highlight what you want to delete.

One that bugs me is when people don't realize shift-tab will go backwards through a tab order.

A couple I like:

Alt + Tab: switch applications (code to IE, for example).  I use this all the time.  Then you don't have to scroll your mouse down to the bottom of the screen to switch applications.

In VS:
Ctrl + Space: pull up Intellisense
Shift + Alt + F10 (2005 only): insert a "using" statement when you haven't included something that is required or to create a method stub for a method you just typed that isn't defined.  I.e., you type "bool printed = PrintSomething(int numChars, String stringToPrint);" and you'll see a red mark underlining the last character in what you just typed, indicating that it didn't recognize that method, but is ready to create the stub for you if you press shift + alt + F10.  If you do press that, you'll get a little drop-down.  Press the "generate method stub" option and it will just plop down what is needed.  In this case, it knows that you're setting a boolean to the return value of this method that it's writing the method stub for, so it will know to declare it as "private boolean PrintSomething."  It also knows that you are sending it an integer and a String, in that order, so it will put that in the method declaration, as well.  I.e. "private boolean PrintSomething(int blah, String blah)."  It usually picks odd names for the parameters, though.  It will then put the squiggly brackets - { } - and put one line in the method... which is basically a line that throws an exception saying that the method is not defined.  Can be a decent time saver.  And you won't have to scroll up to put "using System.IO;" at the top if you realize you need to use the FileInfo object or something.

Thanks for posting this, much apprecaited

Dispared to Repaired.  You are the Man!  Deleted MSMAPI32.DLL and the thing fixed itself.  Thanks a million!

That was pure genius :)

Mike and The Wired... you are FREAKIN' AWESOME! I spent hours on this after uninstalling the 2007 beta and trying to reinstall my old Office 2003 to no avail until I deleted that file (it is now 4am.. time for sleep..).

Thank you! You're solution actually worked; Microsoft's was completely useless. I just deleted MAPI32.DLL and Office opened immediately.

I renamed the MSMAPI32.dll then ran FIXMAPI.EXE from the c:\windows\system32 folder and it fixed this error.

It worked as stated. Fixed Outlook 2003 after having Beta 2007 installed. I wish I could say thank you MIcrosoft...but I can't. Thank you Mike!

Thanks very much.  You just cured a major headache.

Can somebody help? My problem is that suddently, one morning, when I tried opening outlook, it shutted dowm immediately. The error report mentionned masmapi32.dll. No way I can keep it opem more thasn a few seconds before it shuts down. Should I delete this file s said abocvve nd reinstall?

PHEWWW!  MIKE I OWE YOU A BEER MAN!  CHEERS

Great article !
It work and solve the problem of Outlook 2007 and Outlook 2003 coexistance !
10X!

the visuals drawn canot have events attached can they? i mean... If you put a list on 3d object like this, you won't be able to select items; am I right?

You star!
Better than Microsoft's technical support. Fixed my issue too after installing Off.2007.Beta2

Works perfect :)

Thank you thank you thank you!!!!!!!! (hugs and kisses)

tytyty!!!

Mike, can't thank you enough.  Do you take paypal? :)

Thank you! I"ve spent a lot of time to find a proper solution. Where are idiots from Microsoft to help. Microsoft has a stupid old proposal to find.... and replace mapi32.dll in system dir, that dose not work in our situation reinstalling Office 2003 after Office 2007 beta.

THANKS A MILLION!!

Thank You Mike!

Thanks!  Fixed my problem....

thanks for the fix. It worked perfectly. Many thanks!

yES ! fINALLY....WHY DOES MICROSOFT GIVE US THE WRONG INFO !!!!!! ##@$#%^

<a href='http://www.yahoo.com'></a> http://www.ringtones-dir.com/download/">http://www.ringtones-dir.com/download/ <a href='http://www.ringtones-dir.com'>download ringtones</a>. <a href="http://www.ringtones-dir.com ">nokia ringtones</a>: Best free samsung ringtones, Cingular ringtones and more, Ringtones for free. [url]http://www.ringtones-dir.com/free/[/url] [link=http://www.ringtones-dir.com]ring tones[/link] From site .

http://www.ringtones-dir.com/get/ ringtones site free. Best free samsung ringtones, Cingular ringtones and more, Ringtones for free. From website .

funny ringtones

Sharp fellas, worked like a charm!!!!!

Thank u so much - yes all that you need to do is rename the file - but u don't need to reinstall it - just try opening it again and it will work!!!!

Great Job, Headache gone, well done mike

Great - worked a treat - thank you.

I did the following after uninstalling OL2007 I reinstalled OL2003. Then I went to Windows/System32 folder and renamed MAPI32.dll to MAPI_OLD.dll then in that same folder there is an executable called FIXMAPI.exe. I run the executable by double-clicking on it. Then I restarted WinXP Pro.

Fixed the problems.

Hope this helps...

Yama

Hmm, the first sample, where you ls, only seems to grab the first file and doesn't walk each file.  Any ideas?

THanks - worked perfectly

Brilliant

Thanks

when u open the mapi_old.dll it says something about how this helps run the operating system. It asks u  if you want to continue and if u do u open it with..... What do u open it with? And also what do you mean when u say that u restarted WinXP Pro.

That was a very poor design decision by ReSharper.  There's no way that they wouldn't have thought of that.  They're assuming that they're application is more important than intellisense... I doubt anyone would agree with them.

YOU ARE A GOD!!!

Thank You Sooooooooooooooo Much!

Fantastic. The trick worked for me too. Just had to rename the file, as it didn't allow me to delete it - really great.

THANKS THANKS THANKS
i had to uninstall 2007 beta - HORRIBLE hated it slow as molasses and
well nevermind

so i needed to reinstall 2003 - and get to my emails - i had been using thunderbird - but miss my outlook - so now i am set to go

thanks again!

Just use Outlook for syncing my Gmail contacts with my PDA, but was annoyed to get the same error.

Worked like a charm, thanks!

Mike - you saved my ass.  Thanks!

This may not be a keyboard shortcut, but it's helpful nonetheless, and apparently not that realized since most people here don't know about it.  If you want to open a file rather than relying on the editor's open dialog if you have the folder open in Explorer, just start dragging the icon for it, alt-tab to the editor, and drop it in the editor.  I normally keep Explorer open and navigate my files with it so it's usually open to whatever project I'm working on.  It's way faster to just drag and drop than deal with the open dialog.  Plus, I did this while some people were watching me solve some problem and they were like, "How'd you open that file so fast!"  Yes, you can double-click a file too in Explorer, but depending on your file associatons the file may not open in the program you want.

Thanks I wish I would have found this earlier on this week.

YOU ROCK

Sweet- four hours of my life wasted until I found this- nice one!

Mike,
Can't thank you enough. Have wasted hours on this problem!

What a star - thanks. Cured my problem after 3 hours wasted re-installing everything.

Wish it were this easy for me (I would have been done one day ago).  Like others, I have tried uninstalling/reinstalling Outlook 2003, renaming MSMAPI32.dll, run Fixmapi.exe, uninstalling Outlook 2003, then installing Outlook 2007 (after all the foregoing), then get error OLMAPI32.dll.  I believe the problem is somehow related to Microsoft Office Document Image Writer.  When I tried to do a restore I noted that "Printer Driver Microsoft Office Document Image Writer Installed" (MODIW) at a time about 7 minutes after the time my Outlook.ost and Personal.pst files were last updated.  Outlook stopped working shortly thereafter.  I have uninstalled MODIW several times but it keeps coming back.

None of the suggestions to run Installer Cleanup Utility, Custom Maintenance Wizard, Removal Wizard and other MS Office Resource Tools have had any effect.
It is obvious that getting completely rid of Outlook (either version) for a clean reinstallation is impossible.  Any suggestions to the contrary are welcome.

Thanks for the tip!   Outlook 2003 stopped working after I uninstalled Thunderbird 1.5.  Renamed the .dll file, restarted Outlook, and it fixed itself.  You guys saved me lots of time.

Thanks and thanks again.

I spent 4 days trying to fix this and every query led me to try and fix mapi32.dll which was obviously the wrong approach. Like you I found 2007 wanting hence my reason to uninstall.

What is it with MS that they get a simple thing like giving the wrong message wrong!

I fixed the problem by deleting all versions of mapi32.dll files except the following:
C:\i386/mapi32.dll   110KB 8/4/2004
C:\Windows\System32\mapi32.dll  110 KB 8/4/2004
C:\Program Files\Microsoft Office\Office12\OLMAPI32.DLL 2,916 KB 8/24/2006
C:\Program Files\Common Files\System\MSMAPI\1033\MSMAPI32.DLL 49 KB 8/24/2006
Note: these dlls are on the technical refresh to Office 2007

I can access Outlook now, but not reply or send messages. Did anyone else have this problem?

Hello living beings out there,

I had the exact same problem described above but thanks to my pal Mike here, in one day i solved it ! I'm so gratefull that i'd like to add something to Mike's tutorial that really can save precious time:

....
The actual dll that is causing the problem is MSMAPI32.dll, which is located at C:\Program Files\Common Files\System\MSMAPI\1033. Simply rename this file to something else (e.g. MSMAPI32_OLD.dll), ...
••• AND TRY TO OPEN OUTLOOK WITH UR CD IN THE DRIVE OR YOUR ISO MOUNTED !  This will avoid reinstallation and will just replace the dll  (ó.Ò,')  so no more of the following: •••
reinstall Office 2003, and...
••• But only: •••
Outlook 2003 should work perfectly after that.....

It works perfectly! Goodluck to you all & greetz from Brussels (capitol of Belgium)  ;-)

Cya,
R3M!X

Shame on the MS guys for giving out such a crap error message. Good tip, saved a lot of frustration. Thanks!

Many thanks to you, Mike, for this brilliant, but alas, so simple a solution.
So much frustration involved, and just confusing suggestions from Microsoft.

(Just curious: How did you find the solution?)

Best regards
TomV.

Thanks Man, You are rocking. The solution was awesome. i spent 6 hours on this. But simply by renaming the file MSMapi.dll solves the problem.



Thanks a lot

Here's a quick little PowerShell script you can use in conjunction with Out-Zip to zip up a folder on...

PingBack from http://www.powershellhq.com/2006/11/30/create-zipcompressed-folders-with-powershell/

PingBack from http://www.powershellhq.com/2006/11/30/zip-up-a-folder-and-email-it/

Mike,

Are you sure your zip-email script works?  I have added it to my profile as follows (where <???> represents my company server, hidden here for privacy/security reasons):

function test-it {
$sender = rwhiting@<mycompanyserver>.com
$recipient = rwhiting@<mycompanyserver>.com
$server = exchange2.<mycompanyserver>.com
$targetFolder = c:\MyFolder
$file = c:\MyZipFile.zip

if ( [System.IO.File]::Exists($file) ) {
 remove-item -force $file
}

gi $targetFolder | out-zip $file $_
$subject = "Sending a File " + [System.DateTime]::Now
$body = "I'm sending a file!"
$msg = new-object System.Net.Mail.MailMessage $sender, $recipient, $subject, $body
$attachment = new-object System.Net.Mail.Attachment $file
$msg.Attachments.Add($attachment)
$client = new-object System.Net.Mail.SmtpClient $server
$client.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials
$client.Send($msg)
}

function out-zip {
$path = $args[0]
$files = $input

if (-not $path.EndsWith('.zip')) {$path += '.zip'}

if (-not (test-path $path)) {
 set-content $path ("PK" + [char]5 + [char]6 + ("$([char]0)" * 18))
}

$zipfile = (new-object -com shell.application).NameSpace($path)
$files | foreach {$zipfile.CopyHere($_.fullname) }
}

When I execute "test-it" within PowerShell 1.0, I get a series of error messages:


"The term 'rwhiting@<myserver>.com' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again."

I get a similar message for "exchange2.<myserver>.com", "rwhiting@<myserver>.com", "MyFolder", and "c:\MyZipFile.zip".

And also (among others): "New-Object: Constructor not found. Cannot find an appropriate constructor for type System.Net.Mail.Attachment."

Am I doing something wrong, even though I basically cut-and-pasted the script?

Update on above question ...

When I add quotes around each of the literal string values:

    $sender =" rwhiting@<mycompanyserver>.com"
    $recipient =" rwhiting@<mycompanyserver>.com"
    $server =" exchange2.<mycompanyserver>.com"
    $targetFolder = "c:\MyFolder"
    $file =" c:\MyZipFile.zip"

I get fewer error messages, but still this one:

    New-Object: Exception calling ".ctor" with "1" argument(s): "Could not find file 'c:\MyZipFile.zip'."

even though the file DOES exist. Why can't PowerShell see it?

Further update ...

I had to change this line:

    $client.Credentials = new-object system.net.networkcredential("rwhiting","<mypassword>")

Now the script works fine when I enter it INTERACTIVELY, LINE-BY-LINE in PowerShell. But when I execute it AS A FUNCTION, it still does NOT work, but returns the same old error:

    New-Object: Exception calling ".ctor" with "1" argument(s): "Could not find file 'c:\MyZipFile.zip'."

Why does this script work when entered line-by-line interactively in PowerShell, but NOT when run as a function? What am I missing?

Thanks,

Solution ...

Okay, I figured it out. The line correction is:

    [System.Net.Mail.Attachment] $attachment = new-object System.Net.Mail.Attachment $file

It is necessary to cast the $attachment variable to type System.Net.Mail.Attachment, since new-object (in this instance) returns a REFERENCE to an object of that type, not an ACTUAL OBJECT of the type. But $msg.Attachments.Add($attachment) requires an actual object. Hence the need for the cast.

nice :)
;))

Very Helpful!!

Cache.Insert("Customer" + customer.CustomerID.ToString(), customerValue);

makes so much sense.

This looks like a great way to add special effects such as zooming, lighting, and tilting to a 2D game. However, as dreckgos points out, it would only work if the game doesn't require point-and-click type stuff on the game board (e.g, it uses the keyboard or relies on a different panel to host the interactive controls).

There is a workaround that I found, however, from the WPF team: http://blogs.msdn.com/wpf3d/archive/2006/12/12/interacting-with-2d-on-3d-in-wpf.aspx

The last few days I played around with the 3d capabilities of the Windows Presentation Foundation (WPF).

Here's a quick little PowerShell script you can use in conjunction with Out-Zip to zip up a folder on

PingBack from http://www.pwrshell.com/2008/03/04/powershell-script-zip-up-a-folder-and-email-it/

PingBack from http://www.pwrshell.com/2008/03/04/powershell-script-zip-up-a-folder-and-email-it-2/

PingBack from http://frankthefrank.info/entry.php?id=kwws%3d22eorjv1lqhwlxp1frp2eorjv2pkrgqlfn2dufklyh2533923%3b23%3a25%3c81dvs%7b

Pingback from  WPF 3D: Google maps on a sphere, or &#8216;The World&#8217; &laquo; Hungry for Knowledge