COM Discussion Boards

IHTMLSelectElement onchange event

9-Apr-06 21:27

can anyone tell me how do I resolve this error? I get this error when I include FileName_i.c file in my managed C++ client. The complete error is:

cl : Command line error D8045 : cannot compile C file '..\Trial\Trial_i.c' with the /clr option

I also tried switching off the /clr option and used "No Common Language Runtime Support" option, but on that there comes a huge list of errors because I am writing managed code (i.e. Forms etc.), can anyone tell me how do I build my Client which includes the above filename.

Re: error D8045

khan++9-Apr-06 21:34

khan++

9-Apr-06 21:34

I think you cannot compile the XXXX_i.c file.
I am not sure about Managed C++, but in native code, it must not be compiled that way. It can be #included, or the pre-compiled header for it, turned off.

this is this.

abhishekks9-Apr-06 21:16

abhishekks

9-Apr-06 21:16

can spmebody pls advice me how to fire IHTMLSelectElement onchange event in mfc .. i tried IHTMLWindow2 execscript......... but this does not work since the javascript function uses this pointer

why can not get the variable value correctly

brygid9-Apr-06 20:27

brygid

9-Apr-06 20:27

hello,I wrote a property named get_Popvalue(long *nValue),
STDMETHODIMP CATC:get_Popvalue(long *nValue)
{
AFX_MANAGE_STATE(AfxGetStaticModuleState())
// TODO: Add your implementation code here
*pVal = m_dSendBytes;
TRACE1("m_dSendBytes:%d\n",m_dSendBytes);
//m_dSendBytes is not changed here??
return S_OK;
}
and m_dSendBytes is a public variable the defined in the class CATC.

m_dSendBytes will be changed in another function CATC:NotifyData()

void CATC:NotifyData(long nSize)
{
m_dSendBytes += nSize;
//m_dSendBytes can be changed here
}

but m_dSendBytes can not get correctly by com invoked.
Can you tell me why? Thanks

C# project as a Client to COM component

rahultaing9-Apr-06 15:28

Re: C# project as a Client to COM component

9-Apr-06 15:28

Can anyone tell me is it possible to make a C# project as a Client to a COM component. If yes, then how to do that. To be precise, I have made a Client in managed C++ which is using a COM component. In managed C++ Client I call CoInitialize(NULL); which works, but I don't think we can write CoInitialize(NULL); in a C# file.

Please Suggest!

Lim Bio Liong9-Apr-06 22:24

Lim Bio Liong

9-Apr-06 22:24

Hello rahultaing,

In your C# project, perform the following :

1. Make a reference to the Type Library File or to the Executable File (DLL or Exe) of your COM component.
1.1 Go to the "References" section of the "Solution Explorer".
1.2 Right click "References" and select "Add Reference".

2. The "Add Reference" dialog box should appear.
2.1 Select the "COM" tab.
2.2 Click on the "Browse..." button.
2.3 A typical file section dialog box should appear.
2.4 Navigate to your component's TLB or DLL or EXE file and select it.

3. An Interop Assembly will be created dynamically for your COM Component.
3.1 The Object Browser of your Visual C# IDE should now contain an entry for your COM component's Interop Assembly. Look out for this.
3.2 The types contained in the Interop Assembly are important for you to use in your source codes. They will usually be scoped by a namespace that has the form "XXXLib".
3.3 Among the types will be a name for your component's class.
3.4 In your C# code, declare this class as per normal using "new".
3.5 Use your class object normally, calling on its properties and methods.

4. What we have just done is something known as COM interop.
4.1 There is no need to call CoInitialize() nor CoUninitialize(). These are called on your behalf by the .NET framework.
4.2 There is also no need to AddRef() or Release() your COM components. The objects are garbaged collected.

Best Regards,
Bio.

How are COM objects instantiated?

Richard Andrew x649-Apr-06 12:45

Re: How are COM objects instantiated?

9-Apr-06 12:45

Hi,

Is one of the Windows services in charge of instantiating COM objects, or is it more integrated into the OS than that?

When an out-of-process server is started, does the system start it with a call to CreateProcess?

Thank you,
Rich

Michael Dunn9-Apr-06 18:39

Michael Dunn

9-Apr-06 18:39

The COM subsystem in the OS is responsible for loading/running COM servers as necessary. The server itself hands out an IClassFactory interface, and that IClassFactory implementation actually creates COM objects.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

error: LNK2001

rahultaing9-Apr-06 10:49

9-Apr-06 10:49

Can anyone tell me the possible cause of this linker error? I am making a Communicator Component, in the Communicator.h file I write #include "Sockets.h", the Sockets.h file is in the correct folder and contains a class SocketSystem, So now when I declare an object of SocketSystem in my Communicator.h file which is a component that I am trying to make, the above linker error occurs.

Please help!!!

Note: My Sockets.h is a normal C++ header file which contains different Classes and is not included in the project but is present in the same folder.

Richard Andrew x649-Apr-06 12:39

9-Apr-06 12:39

Did you make sure to include the necessary .LIB files in your project's "Additional Dependencies" property?

Richard Andrew x649-Apr-06 13:15

9-Apr-06 13:15

LNK2001 error means that your code is referencing functions that the linker
cannot find.

You have to tell it where to find those functions.

Most likely, the functions appear in some DLL that is not part of your
program.

What are the names of the functions that it can't find?

Post some of the exact error messages it is giving you.

Rich

rahultaing9-Apr-06 13:21

9-Apr-06 13:21

Communicator.obj : error LNK2001: unresolved external symbol "public: __thiscall SocketSystem::SocketSystem(void)" (??0SocketSystem@@QAE@XZ)

Communicator.obj : error LNK2001: unresolved external symbol "public: __thiscall SocketSystem::~SocketSystem(void)" (??1SocketSystem@@QAE@XZ)

Debug\Trial.dll : fatal error LNK1120: 2 unresolved externals

These are the error messages which I get when I declare an object of SocketSystem Class which is present in my "Sockets.h"

Richard Andrew x649-Apr-06 13:27

9-Apr-06 13:27

OK, I understand that the SocketSystem class is declared in "Sockets.h", but where is the class defined? Where are the actual functions located?

Do you have the source for the SocketSystem class, or do you only have the compiled version?

rahultaing9-Apr-06 13:34

9-Apr-06 13:34

The "Sockets.h" file only contains the declaration of the functions, and the functions are implemented in "Sockets.cpp".

The Sockets.cpp file is also present in the same folder as Sockets.h

Richard Andrew x649-Apr-06 13:36

9-Apr-06 13:36

Well, that must be the problem. You just need to add the Sockets.cpp file to your project.

Richard Andrew x649-Apr-06 13:33

9-Apr-06 13:33

Let me ask an easier question:

Do you have a file called "Sockets.cpp" ?

If you have a file by that name, add it to your project, then rebuild, and see if it works.

rahultaing9-Apr-06 13:37

9-Apr-06 13:37

Is it mandatory to add the files in the project? I mean I have the files in the same project folder but I have not added those files in my project itself. I tried doing that earlier, but it gave me around 17 linker errors on that, so I removed those files from my project.

Richard Andrew x649-Apr-06 13:43

9-Apr-06 13:43

The files which contain the actual implementations of the functions must be part of your project, otherwise how else does the compiler generate code for those functions?

If including the Sockets.cpp file caused more linker errors, then that means that there must be OTHER .cpp files that must ALSO be included.

rahultaing9-Apr-06 13:47

9-Apr-06 13:47

Yes I knew about it and so I even tried adding all those 4 modules that I used to use in my previous C++ project. Now when I add all those files as well, the compiler again gives me a linker error, I will list those errors in 5 minutes from now. Please see if that makes any sense to you.

rahultaing9-Apr-06 13:51