\nFor some reason,\n\nsome people go to enormous lengths to locate the Internet Explorer\nbinary<\/A> so they can launch it with some options.\n<\/P>\n \nThe way to do this is not to do it.\n<\/P>\n \nIf you just pass “IEXPLORE.EXE” to\n\nthe ShellExecute function<\/A>\n[link fixed 9:41am],\nit will go find Internet Explorer and run it.\n<\/P>\n \nThe ShellExecute function gets its hands dirty so you don’t have to.\n<\/P>\n \n(Note: If you just want to launch the\nURL generically, you should use\n \nso that the web page opens in the user’s preferred web browser.\nForcing Internet Explorer should be avoided under normal circumstances;\nwe are forcing it here because the action is presumably being taken\nresponse to an explicit request to open the web page specifically\nin Internet Explorer.)\n<\/P>\n \nIf you want to get your hands dirty, you can of course do it yourself.\nIt involves\n\nreading the specification from the other side<\/a>, this time\n\nthe specification on how to register your program’s name\nand path<\/A> (“Registering Application Path Information”).\n<\/P>\n \nThe document describes how a program should enter its properties\ninto the registry so that the shell can launch it. To read it\nbackwards, then, interpret this as a list of properties you (the launcher)\nneed to read from<\/STRONG> the registry.\n<\/P>\n \nIn this case, the way\nto run Internet Explorer (or any other program)\nthe same way ShellExecute does\nis to look in\nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths\\IEXPLORE.EXE (substituting\nthe name of the program if it’s not Internet Explorer you’re after).\nThe default value is the full path to the program and the\nthe “Path” value specifies a custom path that you should prepend\nto the environment before launching the target program.\n<\/P>\n\nShellExecute(NULL, “open”, “iexplore.exe”,\n “http:\/\/www.microsoft.com”, NULL,\n SW_SHOWNORMAL);\n<\/PRE>\n
\nShellExecute(NULL, “open”, “http:\/\/www.microsoft.com”,\n NULL, NULL, SW_SHOWNORMAL);\n<\/PRE>\n