Shortcuts to C:\

[gOtAgObyUnOw]

I am wondering if it is possible to create a shortcut to C:\ through a Visual C++ program??, the operating system is XP professional, and the computers are networked, which prevents shortcuts by right clicking. (if u didnt already know that). any ideas, through programs or other things let me know please, any help will be greatly appreciated.

[CornedBee]

There's a description of the .lnk format somewhere on the MS homepage.

[Jop]

The quickest & easiest way to create a shortcut is by using the ShellExecute API:

#include <windows.h>

int main(){

	ShellExecute(NULL, "open", "C:\\", NULL, NULL, SW_NORMAL);
	return 0;
}

Enjoy

[PT Exorcist]

i tryed this from VC++7 and it didnt work:

// shell.cpp : Defines the entry point for the console application.
//

#include "stdafx"
#include "iostream"
#include <windows>

int _tmain(int argc, _TCHAR* argv[])
{
	ShellExecute(NULL, "open", "C:\\", NULL, NULL, SW_NORMAL);
	return 0;
}

whats the problem here?

[Jop]

// shell.cpp : Defines the entry point for the console application.
//

#include "stdafx.h"
#include <iostream>
#include <windows.h>

int _tmain(int argc, _TCHAR* argv[])
{
	ShellExecute(NULL, "open", "C:\\", NULL, NULL, SW_NORMAL);
	return 0;
}

Check the blue parts

[PT Exorcist]

#include "stdafx.h"
#include <iostream>
#include <windows.h>

i cant get it! what is the difference?

#include "*.h"
#include "*"
#include <*.h>
#include <*>

where * is the name of the header..what is the difference between them? when do i know which to implement?

[PT Exorcist]

emm...did u edit ur post? i could swear u said bold and not blue and that the things were in bold..lol

[PT Exorcist]

still got an error:

error C2065: 'ShellExecute' : undeclared identifier

[sunburnt]

#include "*.h"
#include "*"
#include <*.h>
#include <*>

#include <windows.h>
The angular brackets are used for header files that are located in the compiler's include directory. Quotes are used for header files that are located in your project directory or elsewhere.
#include "../inc/myclass.h"

.h header files are depreciated; now the standards committee has decided that instead there should be no .h extension, and that the content of the header file should be located inside a namespace (often std).
use .h if you must, or locate the appropriately new header file.
#include <iostream.h> ==> #include <iostream>
#include <stdlib.h> ==> #include <cstdlib>

[PT Exorcist]

hmm ah ok very tks

[Jop]

Originally posted by PT Exorcist

i cant get it! what is the difference?
( ... )
where * is the name of the header..what is the difference between them? when do i know which to implement?

Ok, you use the < and > when the (header)file resides in the include path (this is something that's defined by your linker, there are directories in which the linker looks for the header files by default). So most of the headers that came with your compiler will be available by using < and >.

When you use " ", you're telling your linker that you're looking for a header file in the same dir as your cpp file (maybe you can do stuff like "MyDir/myFile.h" but I've never tried it - Now I see from the reply above that this is possible)

Stuff in the Standard Template Library doesn't use the .h postfix, but since the Windows API isn't compatible with other systems, it's not in the Standard Template Library, so that's why there's a .h postfix.
Iostream doesn't have a .h postfix since it's in the Standard Template Library.

I hope I explained things well

And yes, I edited my post, I saw that the bold parts weren't that obvious

Edit: Hmm writing this stuff took me little too long, sunburnt was faster

[PT Exorcist]

ah ok tks to you too lol

[Jop]

Do you still get errors by the way? I think it should work just fine with the code I posted? in a console app that is

[PT Exorcist]

hmm err no..it still giving error..but it is not big trouble..u see..i am not the guy who started the topic..it was just curiosity lol

[Jop]

Well now you made me curious why it doesn't work

Just open a new Solution, a new empty console app project. Make a new Cpp file and paste the code below.

#include <windows.h>

int main(){

	ShellExecute(NULL, "open", "C:\\", NULL, NULL, SW_NORMAL);
	return 0;
}

If everything is correct (include paths etc) it should work.

[CornedBee]

And if it works you can extend it for UNICODE:

#include <windows.h>
#include <tchar.h>

int _tmain(int argc, _TCHAR **argv)
{
	ShellExecute(NULL, _T("open"), _T("C:\\"), NULL, NULL, SW_NORMAL);
	return 0;
}

Or to avoid the console window popping up, make it a win32 app subsystem windows and use
int _tWinMain(HINSTANCE, HINSTANCE, LPTSTR, int)

instead.

[PT Exorcist]

hmm ok ty after school ill try it out

[PT Exorcist]

Originally posted by Jop
Well now you made me curious why it doesn't work

Just open a new Solution, a new empty console app project. Make a new Cpp file and paste the code below.

#include <windows.h>

int main(){

	ShellExecute(NULL, "open", "C:\\", NULL, NULL, SW_NORMAL);
	return 0;
}

If everything is correct (include paths etc) it should work.

that worked