compiling a simple ShellExecute with C

[=?Utf-8?B?aGtNaWNybw==?=]

Having problems compiling the following code in C USING CL.EXE
// shell.c LANGUAGE = .NET 2003
#include <iostream.h>
#include <windows.h>

int main()
{
SHELLEXECUTE(NULL, "open", "notepad.exe", NULL, NULL, SW_SHOWNORMAL);
RETURN 0;
}

Results:

C:\ CL /EHs shell.c
....... Incremental Linker Version 6.00.8447
......
shell.obj : error LNK2001: unresolved external symbol __imp__ShellExecuteA@24
shell.exe : fatal error LNK1120: 1 unresolved externals
C:\>

I suppose the problem has to do with Unicode. but am not sure. Any help
appreciated.

Thanks,

Hank

[Mattias Sjögren]

SHELLEXECUTE(NULL, "open", "notepad.exe", NULL, NULL, SW_SHOWNORMAL);

The function is called ShellExecute, not SHELLEXECUTE.

>C:\ CL /EHs shell.c
...... Incremental Linker Version 6.00.8447
.....
shell.obj : error LNK2001: unresolved external symbol __imp__ShellExecuteA@24
shell.exe : fatal error LNK1120: 1 unresolved externals

Try adding

/link shell32.lib

Mattias

--
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

[David Wilkinson]

hkMicro wrote:

Having problems compiling the following code in C USING CL.EXE
// shell.c LANGUAGE = .NET 2003
#include <iostream.h>
#include <windows.h>

int main()
{
SHELLEXECUTE(NULL, "open", "notepad.exe", NULL, NULL, SW_SHOWNORMAL);
RETURN 0;
}

Results:

C:\ CL /EHs shell.c
...... Incremental Linker Version 6.00.8447
.....
shell.obj : error LNK2001: unresolved external symbol __imp__ShellExecuteA@24
shell.exe : fatal error LNK1120: 1 unresolved externals
C:\>

I suppose the problem has to do with Unicode. but am not sure. Any help
appreciated.

Hank:

Note that iostream (which you are not actually using) is C, not C++. And
<iostream.his an obsolete header (use <iostream>).

You are not really in the right group; use microsoft.public.vc.language
for questions that do not have to do with.NET.

--
David Wilkinson
Visual C++ MVP

[David Wilkinson]

David Wilkinson wrote:

Hank:

Note that iostream (which you are not actually using) is C, not C++. And
<iostream.his an obsolete header (use <iostream>).

You are not really in the right group; use microsoft.public.vc.language
for questions that do not have to do with.NET.

Of course I meant: iostream is C++, not C.

--
David Wilkinson
Visual C++ MVP

[Jeffrey Tan[MSFT]]

Hi Hank,

Yes, this is because <Windows.hincludes a lot of important(or must have)
windows header files, such as <windef.h>, <winbase.hetc... These files
define must of the windows structures types, such as DWORD, BOOL etc..

So we'd better always include <windows.hif you are programming Windows
SDK applications. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Jeffrey Tan[MSFT]]

Hi Hank,

Have you reviewed all the replies to you? If you still need any help or
have any concern, please feel free to feedback, thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support