ATL / WTL / STL

Re: Dialog DoModal fails in win2000

1-Oct-08 7:46

Have you initialized common controls with InitCommonControls[^] or InitCommonControlsEx[^]? That can often have that effect.

gaara242-Oct-08 0:08

gaara24

2-Oct-08 0:08

No I haven't. This might be the solution. Is there any example of how it's used that i can look at?

Thanks,

Alex

Re: Dialog DoModal fails in win2000

Stuart Dootson2-Oct-08 7:16

2-Oct-08 7:16

This page[^] looks like it tells you all about it.

Task Scheduler

brucewayn1-Oct-08 0:11

brucewayn

1-Oct-08 0:11

i am working on an application where i want to schedule a task setting the time, date and day. All i know is that it is possible using thread... but how??? i just want to have an idea for approaching such application.

Re: Task Scheduler

Stuart Dootson1-Oct-08 7:36

Questions re. ATL service (EXE) plus ATL simple object

1-Oct-08 7:36

You could use the Windows Task Scheduler[^]. See this CP article[^] for a helpful article.

markiemooster30-Sep-08 3:22

markiemooster

30-Sep-08 3:22

I've written a Windows service with the help of the VS2008 ATL project wizard. I've added a ATL simple object which I hope will allow external processes to interact with my service via its interface.

1. I assume I can use the _AtlModule global variable to achieve this. Is it safe to call _AtlModule methods from the ATL simple object, e.g. _AtlModule.MyMethod(x)?

2. I plan to write some ASP server side script and use Server.CreateObject("xxxx.yyyyy") to access the service using the ATL simple object I created. (a) Will this be possible? (b) Are there any special permissions that will need to be set in IIS or anywhere else (I'm using Windows Server 2003)?

3. Does the service need to be running for such a call to succeed or will it be started?

Sorry for all the questions but I've never written a Windows service like this before.

Thanks in advance.

Re: Questions re. ATL service (EXE) plus ATL simple object

led mike30-Sep-08 5:13

led mike

30-Sep-08 5:13

markiemooster wrote:
Sorry for all the questions but I've never written a Windows service like this before.

Then I strongly urge you to find, read and understand materials that explain what services are. You do not seem to be on the correct track with services at this time.

Introduction to Windows Services[^]

led mike

Re: Questions re. ATL service (EXE) plus ATL simple object

markiemooster30-Sep-08 6:50

markiemooster

30-Sep-08 6:50

Thanks Mike. But I've written about half a dozen or so services in my time. Perhaps you weren't aware that you can create an ATL COM service using the VS2008 project wizard?

You choose the ATL Project template. In the Applications Settings dialog box, select the "Service" radio button. Now add an ATL class in the usual manner: "Add", "Class", "ATL Simple Object".

All that aside, could someone please shed some light on my queries.

Thanks.

Re: Questions re. ATL service (EXE) plus ATL simple object

Roger Stoltz6-Oct-08 4:51

Roger Stoltz

6-Oct-08 4:51

markiemooster wrote:
1. I assume I can use the _AtlModule global variable to achieve this. Is it safe to call _AtlModule methods from the ATL simple object, e.g. _AtlModule.MyMethod(x)?

2. I plan to write some ASP server side script and use Server.CreateObject("xxxx.yyyyy") to access the service using the ATL simple object I created. (a) Will this be possible? (b) Are there any special permissions that will need to be set in IIS or anywhere else (I'm using Windows Server 2003)?

3. Does the service need to be running for such a call to succeed or will it be started?

1. Depends on what you mean by "safe"...
Your service may be accessed from different applications which means that you have to make it thread safe.

2(a). I suppose that you are limited to automation compatible interfaces when using scripting languages, but that's fine.

2(b). I don't think so, but that may depend more on what you're trying to do from your service than the fact that you're exposing COM objects from it. You also have to call ::CoInitializeSecurity() in your wizard generated class derived from CAtlServiceModuleT. At least

CoInitializeSecurity( NULL, -1, NULL, NULL, RPC_C_AUTHN_LEVEL_NONE, 
                      RPC_C_IMP_LEVEL_IMPERSONATE, NULL, EOAC_NONE, NULL );

3. No, the service doesn't have to be started, but it must be installed as a service. The service is started when the client tries to create an instance of an object that the service exposes.

"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown

include file for a COM client (consumer)

George_George25-Sep-08 23:59

25-Sep-08 23:59

Hello everyone,

When writing an ATL COM server, MIDL compiler will automatically generated file _i.c and _i.h from IDL definition.

My question is whether my below usage for the two files are correct when writing a COM client (consumer)?

1. I put _i.h file into the "Header files" of the client project, and using it to make the build for client project;
2. I put the _i.c into the "Source files" of the client project, and using it to make the build for client project.

thanks in advance,
George

Stuart Dootson27-Sep-08 4:35

27-Sep-08 4:35

I don't think you need the .c file for COM, just the .h file. If you look at this page[^], it says that the C stub file is only needed when IDL is used to define RPC interfaces.

IIRC, the C stub contains code to serialize parameters for RPC calls into an interchangeable form.

George_George27-Sep-08 18:56

27-Sep-08 18:56

Hi Stuart,

If I do not include the .c file, there will be link error. Any ideas?

1>d:\visual studio 2008\projects\testatl2\teststruct1\main.cpp(14) : error C2275: 'TestStrcut1' : illegal use of this type as an expression
1>        d:\visual studio 2008\projects\testatl2\teststruct1\testatl2_i.h(58) : see declaration of 'TestStrcut1'
1>d:\visual studio 2008\projects\testatl2\teststruct1\main.cpp(17) : error C2275: 'ITestStrcut1' : illegal use of this type as an expression
1>        d:\visual studio 2008\projects\testatl2\teststruct1\testatl2_i.h(99) : see declaration of 'ITestStrcut1'


#include "TestATL2_i.h"

int main()
{
	HRESULT     hr;
	ITestStrcut1* pITS;

	CoInitialize (NULL);

	MyValue data; 

	data.x = 5;

	hr = CoCreateInstance ( TestStrcut1,         // CLSID of coclass
							NULL,                    // not used - aggregation
							CLSCTX_INPROC_SERVER,    // type of server
							ITestStrcut1,          // IID of interface
							(void**) &pITS );        // Pointer to our interface pointer

    if ( SUCCEEDED ( hr ) )
    {
        // Tell the COM object that we're done with it.
		hr = pITS->SetMyStruct (&data);
        pITS->Release();
    }
    else
    {
    // Couldn't create the COM object.  hr holds the error code.
	}

	CoUninitialize();

	return 0;
}

regards,
George

Stuart Dootson28-Sep-08 3:44

28-Sep-08 3:44

It's been a while since I've done ATL, but it's coming back now Smile | :)

I was wrong about the .c file not being needed - that's a *different* .c file!

The .c file defines the CLSID and IID for the ATL object and interfaces. You can compile the .c file and incorporate the .obj file into a .lib file - that's what Microsoft do in the Windows SDK (look for uuid.lib) - or just #include the .c file into your client. I usually use the second approach, so if I have generated interface files called a_i.c and a_i.h, I'd use something like the code below in the .cpp file containing my main or WinMain:

#include "a_i.h"
#define INITGUID
#include "a_i.c"

The #define INITGUID causes the code in the .c file to define variables that contain the IID and CLSID.

HTH!!!

George_George28-Sep-08 3:53

28-Sep-08 3:53

Thanks Stuart,

I am confused about your two solutions.

1. The first solution is to include _i.c file into the COM consumer project, I agree and understand. Is it what you mean?

2. The second solution is to use uuid.lib?? Could this lib file contains all customer defined CLSID/IID, since this lib file is shipped before you write any customized code? I doubt it will have the same effect as solution 1.

regards,
George

Stuart Dootson28-Sep-08 6:40

28-Sep-08 6:40

George_George wrote:
1. The first solution is to include _i.c file into the COM consumer project, I agree and understand. Is it what you mean?

Yes

George_George wrote:
2. The second solution is to use uuid.lib?? Could this lib file contains all customer defined CLSID/IID, since this lib file is shipped before you write any customized code? I doubt it will have the same effect as solution 1.

No - I used uuid.lib as an example of how CLSID and IIDs can be packaged - in fact, how Microsoft package up CLSIDs and IIDs for COM objects defined within Windows.

I meant that you could compile your _i.c file and put the .obj file into a .lib file, then get consumers to link against the .lib file you've produced. This way of doing things could be easier if you have several COM components to distribute.

George_George30-Sep-08 1:13

30-Sep-08 1:13

Thanks Stuart,

Good idea -- "compile your _i.c file and put the .obj file into a .lib file"! You mean a static lib file, and not import lib file, correct?

regards,
George

Stuart Dootson30-Sep-08 10:10

30-Sep-08 10:10

George_George wrote:
You mean a static lib file, and not import lib file, correct?

Yep, that's right. Create a static library project in VS and add the _i.c file as a source.

George_George30-Sep-08 22:33