Click here to Skip to main content
Click here to Skip to main content

How to create and resolve a shortcut

By , 6 Oct 2003
 

Introduction

Shortcut is a file with an extension .lnk. Each of these files contain a special COM object that points to another file. Usually, when you try to open a .lnk file, the system opens a file which this shortcut points to.

Let's do the following experiment. Create a text file (file with an extension .txt) somewhere. Then create a shortcut pointing to this file (send me a private e-mail if you do not know how to create a shortcut manually). Then try to open the shortcut with Microsoft Word, using File->Open command and select just created shortcut. MS Word will do it correctly: it will open the text file that is pointed by this shortcut. Now do the same with Notepad. Instead of the text file content, you will see garbage. It means that Notepad has no idea how to deal with shortcuts.

So we came to a conclusion: in Windows a program should have a built-in support for shortcuts in order to handle them correctly.

In this article I will show how to do it. I will present 2 functions: how to create and resolve the shortcut. The code is well commented (in my opinion) and self-explanatory.

Code

/**********************************************************************
* Function......: CreateShortcut
* Parameters....: lpszFileName - string that specifies a valid file name
*          lpszDesc - string that specifies a description for a 
                             shortcut
*          lpszShortcutPath - string that specifies a path and 
                                     file name of a shortcut
* Returns.......: S_OK on success, error code on failure
* Description...: Creates a Shell link object (shortcut)
**********************************************************************/
HRESULT CreateShortcut(/*in*/ LPCTSTR lpszFileName, 
                    /*in*/ LPCTSTR lpszDesc, 
                    /*in*/ LPCTSTR lpszShortcutPath)
{
    HRESULT hRes = E_FAIL;
    DWORD dwRet = 0;
    CComPtr<IShellLink> ipShellLink;
        // buffer that receives the null-terminated string 
        // for the drive and path
    TCHAR szPath[MAX_PATH];    
        // buffer that receives the address of the final 
        //file name component in the path
    LPTSTR lpszFilePart;    
    WCHAR wszTemp[MAX_PATH];
        
    // Retrieve the full path and file name of a specified file
    dwRet = GetFullPathName(lpszFileName, 
                       sizeof(szPath) / sizeof(TCHAR), 
                       szPath, &lpszFilePart);
    if (!dwRet)                                        
        return hRes;

    // Get a pointer to the IShellLink interface
    hRes = CoCreateInstance(CLSID_ShellLink,
                            NULL, 
                            CLSCTX_INPROC_SERVER,
                            IID_IShellLink,
                            (void**)&ipShellLink);

    if (SUCCEEDED(hRes))
    {
        // Get a pointer to the IPersistFile interface
        CComQIPtr<IPersistFile> ipPersistFile(ipShellLink);

        // Set the path to the shortcut target and add the description
        hRes = ipShellLink->SetPath(szPath);
        if (FAILED(hRes))
            return hRes;

        hRes = ipShellLink->SetDescription(lpszDesc);
        if (FAILED(hRes))
            return hRes;

        // IPersistFile is using LPCOLESTR, so make sure 
                // that the string is Unicode
#if !defined _UNICODE
        MultiByteToWideChar(CP_ACP, 0, 
                       lpszShortcutPath, -1, wszTemp, MAX_PATH);
#else
        wcsncpy(wszTemp, lpszShortcutPath, MAX_PATH);
#endif

        // Write the shortcut to disk
        hRes = ipPersistFile->Save(wszTemp, TRUE);
    }

    return hRes;
}

/*********************************************************************
* Function......: ResolveShortcut
* Parameters....: lpszShortcutPath - string that specifies a path 
                                     and file name of a shortcut
*          lpszFilePath - string that will contain a file name
* Returns.......: S_OK on success, error code on failure
* Description...: Resolves a Shell link object (shortcut)
*********************************************************************/
HRESULT ResolveShortcut(/*in*/ LPCTSTR lpszShortcutPath,
                        /*out*/ LPTSTR lpszFilePath)
{
    HRESULT hRes = E_FAIL;
    CComPtr<IShellLink> ipShellLink;
        // buffer that receives the null-terminated string 
        // for the drive and path
    TCHAR szPath[MAX_PATH];     
        // buffer that receives the null-terminated 
        // string for the description
    TCHAR szDesc[MAX_PATH]; 
        // structure that receives the information about the shortcut
    WIN32_FIND_DATA wfd;    
    WCHAR wszTemp[MAX_PATH];

    lpszFilePath[0] = '\0';

    // Get a pointer to the IShellLink interface
    hRes = CoCreateInstance(CLSID_ShellLink,
                            NULL, 
                            CLSCTX_INPROC_SERVER,
                            IID_IShellLink,
                            (void**)&ipShellLink); 

    if (SUCCEEDED(hRes)) 
    { 
        // Get a pointer to the IPersistFile interface
        CComQIPtr<IPersistFile> ipPersistFile(ipShellLink);

        // IPersistFile is using LPCOLESTR, 
                // so make sure that the string is Unicode
#if !defined _UNICODE
        MultiByteToWideChar(CP_ACP, 0, lpszShortcutPath,
                                       -1, wszTemp, MAX_PATH);
#else
        wcsncpy(wszTemp, lpszShortcutPath, MAX_PATH);
#endif

        // Open the shortcut file and initialize it from its contents
        hRes = ipPersistFile->Load(wszTemp, STGM_READ); 
        if (SUCCEEDED(hRes)) 
        {
            // Try to find the target of a shortcut, 
                        // even if it has been moved or renamed
            hRes = ipShellLink->Resolve(NULL, SLR_UPDATE); 
            if (SUCCEEDED(hRes)) 
            {
                // Get the path to the shortcut target
                hRes = ipShellLink->GetPath(szPath, 
                                     MAX_PATH, &wfd, SLGP_RAWPATH); 
                if (FAILED(hRes))
                    return hRes;

                // Get the description of the target
                hRes = ipShellLink->GetDescription(szDesc,
                                             MAX_PATH); 
                if (FAILED(hRes))
                    return hRes;

                lstrcpyn(lpszFilePath, szPath, MAX_PATH); 
            } 
        } 
    } 

    return hRes;
}

Using the code

The following code will show how you may use these functions.

void HowToCreateShortcut()
{
    LPCTSTR lpszFileName = _T("C:\\Work\\Window.exe");
    LPCTSTR lpszShortcutDesc = _T("Anything can go here");
    LPCTSTR lpszShortcutPath = 
_T("C:\\Documents and Settings\\Administrator\\Desktop\\Sample Shortcut.lnk");

    CreateShortcut(lpszFileName, lpszShortcutDesc, lpszShortcutPath);
}

void HowToResolveShortcut()
{
    LPCTSTR lpszShortcutPath = 
_T("C:\\Documents and Settings\\Administrator\\Desktop\\Sample Shortcut.lnk");
    TCHAR szFilePath[MAX_PATH];

    ResolveShortcut(lpszShortcutPath, szFilePath);
}

That's it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Igor Vigdorchik
Web Developer
United States United States
No Biography provided

Sign Up to vote   Poor Excellent
Add a reason or comment to your vote: x
Votes of 3 or less require a comment

Comments and Discussions

 
You must Sign In to use this message board.
Search this forum  
    Spacing  Noise  Layout  Per page   
GeneralRe: cant include atlbase.hmemberIgor Vigdorchik2-Feb-06 5:45 
On my pc it's in C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\atlmfc\include (I have VS2003).
Make sure this path (where it's on your pc) is listed in the project options.
GeneralDelete the UNC path informationmemberasimeqi12-Apr-05 8:42 

I am creating a shortcut on my machine and distributing it to several other machines.
The shortcut points to an executable on the local machine (Say C:\IE\IEinstall.exe).
Unfortunately the shortcut contains the UNC path to my machine. This creates problems when that path can be resolved from another machine but the logged on user on that machine does not have permissions for my machine (it may fail in other cases but this is definitely a case when it fails).
 
I would like to remove the UNC path information from my shortcut. There is a KB article about this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;150215
But I cannot find the tool mentioned in there in the resource kit.
Does anybody know where can I find that tool?
Or does anybody know the binary format of the shortcut so that I can remove the UNC by hand?

GeneralArgumentsmemberVadimeti14-Nov-04 4:07 
How can I create a shortcut for programm that called with
an argument : "c:\myfile.exe -arg"
Thank you .
GeneralRe: ArgumentsmemberIgor Vigdorchik14-Nov-04 7:46 
Use IShellLink::SetArguments(LPCTSTR pszArgs) method.
GeneralGetPath may "succeed" without returning a pathmember--.-4-Nov-04 9:59 
From MSDN documentation on GetPath:

Returns NOERROR if the operation is successful and a valid path is retrieved. If the operation is successful, but no path is retrieved, it returns S_FALSE and pszFile will be empty.

Therefore, I believe the "if" below GetPath should be
 
    if (hRes != NOERROR)
 
instead of
 
    if (FAILED(hRes))
GeneralRe: GetPath may &quot;succeed&quot; without returning a pathmemberIgor Vigdorchik4-Nov-04 10:49 
There is no difference between these 2 statements.
GeneralRe: GetPath may &quot;succeed&quot; without returning a pathmember--.-4-Nov-04 11:32 
I find the following definitions in winerror.h:
 
#define NOERROR 0
#define SUCCEDED(status) ((HRESULT)(Status) >= 0)
#define FAILED(status) ((HRESULT)(Status)<0)
 
Hence there is a difference-- a return of zero is not considered a FAILure, but it does not provide useful data for my purpose.
GeneralRe: GetPath may &quot;succeed&quot; without returning a pathmemberIgor Vigdorchik4-Nov-04 11:43 
--.- wrote:
it does not provide useful data for my purpose
 
But I am not looking for an useful data, all I want to know if I get a valid path.
And if I don't then I bail out, if I do then I continue. This is a purpose of SUCCEDED and FAILED macros.
GeneralRe: GetPath may "succeed" without returning a pathmemberAbraxas2325-Dec-11 15:32 
To set the record straight S_FALSE is a 'success' code and hence will not be caught by the FAILED macro. The call to IShellLink::GetPath may 'succeed' and yet not return a valid path.
QuestionRelease?sussAnonymous13-Sep-04 23:09 
From my limited understanding of COM, I thought that you should call
pShellLink->Release();
in a couple of places to say that you had finished with the interface.
However, when I try this it causes compiler errors ???

AnswerRe: Release?memberIgor Vigdorchik19-Sep-04 5:18 
CComPtr is a smart pointer class, it does automatic reference counting through calls to AddRef and Release. So you never call Release().
GeneralproblemmemberMister Transistor30-Jun-04 1:48 
Sorry to be dim but although your code is well-commented, I don't understand the principle of what it is doing. I tried to use this in a VC++6 app under ME -I added the headers
#include <stdafx.h>
#include <atlbase.h>
#include <ShlObj.h>
and it compiled and linked first time. However, it does not resolve a shortcut. Debug shows that the call
      hRes = CoCreateInstance(CLSID_ShellLink,
                                          NULL,
                                          CLSCTX_INPROC_SERVER,
                                          IID_IShellLink,
                                          (void**)&ipShellLink);
fails with hRes being returned 0x800401f0
 
Andrew

GeneralRe: problemmemberIgor Vigdorchik30-Jun-04 3:21 
This error means 'CoInitialize has not been called'.
You need to call CoInitialize() to initialize COM somewhere before you call this function (better to do it in main()).
 
Igor.
GeneralRe: problemmemberMister Transistor2-Jul-04 0:57 
Igor,
thanks - I tried to find that error message but failed. Since I am using VC6 I added the call CoInitialize(NULL) to InitInstance (there is no 'main' in a Windows program).
 
My app now works, although there is a minor feature - the lnk path that I pass uses forward slash to separate directories but ResolveShortcut returns backslash separated ones.
 
Also, Microsoft state that new applications should use CoInitializeEx, however I cannot get this to compile, using the header they specify...
see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/com/htm/cmf_a2c_36qt.asp
 
cheers
Andrew
GeneralRe: problemmemberIgor Vigdorchik2-Jul-04 4:32 
Mister Transistor wrote:
I tried to find that error message but failed
 
Use Error Lookup utility from VC6 Tools menu.
 
Mister Transistor wrote:
there is no 'main' in a Windows program
 
Sorry, but there is always a main() (sometimes hidden) in the Windows program Smile | :) .
 
Mister Transistor wrote:
Microsoft state that new applications should use CoInitializeEx
 
CoInitialize() will do.
 
Igor.

GeneralThankssussbasudevc7-Apr-04 3:55 
Thanks for the article
Unless it's because I haven't searched enough, I haven't found a command line shortcut creation tool for XP. This should do it.
If it works could I put the executable on my website?
 
Basu
 
b a s u d e v a t g n s b i o t e c h d o t c o m
 
bman
GeneralRe: ThanksmemberIgor Vigdorchik10-Apr-04 2:36 
Sure.
GeneralMissing Directorymemberbruno leclerc23-Mar-04 23:32 
Hi,
When I want to create a shortcut in a missing directory,
the shortcut is not created, but no error is returned ?
Why ?
Thanks
GeneralRe: Missing Directorymemberronyy724-Mar-04 14:37 
It may have been created under an unexpected path. It happened to me when my original path > MAX_PATH it got truncated and was created somewhere else.
GeneralRe: Missing DirectorymemberIgor Vigdorchik24-Mar-04 15:50 
I just tested it, a shortcut was created but it's target property was pointing to an non-existing folder (or file). It's an expected behaviour, since IShellLink has no way of knowing if a target exists or not.
But when it tries to resolve it then if it can not find a target it'll display a prompting dialog. To suppress the dialog box, you need to set the SLR_NO_UI flag.
 
Igor.
Generalfile name &gt; MAX_PATHmemberronyy717-Mar-04 13:09 
Is there a way to create a shortcut for file name > than MAX_PATH using the UNC convention? i.e. \\?\UNC\....
QuestionWhat to includemember--.-10-Feb-04 15:38 
If you didn't start with a ready-made project for a Windows executable you'll want these includes:
 
#include <Windows.h>
#include <atlbase.h>
#include <ShlObj.h>

AnswerRe: What to includesussRivael11-May-04 0:00 
You might also need to include this in your source code before any OLE operations:
hRes = CoInitialize(NULL);
 

 
mik
Generalget info from MSOffice shortcutmemberSergey K3-Feb-04 5:42 
How to obtain a correct path to an executed file for lnk-file of MSOffice 2002 (for example Microsoft Word.lnk in main menu or on Desktop).
I try it to make using IShellLink::GetPath.
I get a path like C:\WINDOWS\Installer\{91110419-6000-11D3-8CFE-0050048383C9}\wordicon.exe.
If to see this file in a binary mode, the file contains this information and the shortcut works correctly.

GeneralRe: get info from MSOffice shortcutmemberIgor Vigdorchik3-Feb-04 13:43 
Did you use ResolveShortcut() function from the article?

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Permalink | Advertise | Privacy | Mobile
Web04 | 2.6.130617.1 | Last Updated 7 Oct 2003
Article Copyright 2003 by Igor Vigdorchik
Everything else Copyright © CodeProject, 1999-2013
Terms of Use
Layout: fixed | fluid