C / C++ / MFC

3-Jul-08 3:05

Thats reading the docs:
http://msdn.microsoft.com/en-us/library/77d16yhw(VS.80).aspx[^]

If you do more stuff with a Control you better create a instance member.

Greetings from Germany

com dll problem

rjkg3-Jul-08 2:16

rjkg

3-Jul-08 2:16

I am using two third party com dll . I am facing the problem that their clsids are same ,so i can
use only one dll. but my project requirement is to use both the dll . Is their any way to
change the clsid of the com dll . any binay tool etc. any another trick.

Rajesh

Nibu babu thomas3-Jul-08 2:28

Nibu babu thomas

3-Jul-08 2:28

rajeshgupta1253 wrote:
clsids are same

Is it the name that's the same or the GUIDs(it can't be)?

ATL COM DLLs come with namespaces if you have the tlb file associated with them, namespaces does help avoid such cases.

Then there is a rename attribute that can be used with a tlb file while using #import.

From MSDN:
The rename attribute is used to work around name collision problems. If this attribute is specified, the compiler replaces all occurrences of OldName in a type library with the user-supplied NewName in the resulting header files.

Nibu babu thomas
Microsoft MVP for VC++

Code must be written to be read, not by the compiler, but by another human being.

Programming Blog: http://nibuthomas.wordpress.com

rjkg3-Jul-08 2:38

rjkg

3-Jul-08 2:38

guids are same

Rajesh

Roger Stoltz3-Jul-08 2:39

Roger Stoltz

3-Jul-08 2:39

This is supposed to be a no-no....

If the two servers have the same class id, then it is the same server, by definition and by COM spec. It may be that the later server is an updated version, but it is still the same server.
If the supplier of the two servers claims that those are two different servers, they have broken some of the fundamental rules of COM and there are no guarantees for this to work when distributed even if you might get it to work on your machine.
The human readable ProgID may be updated with a new version from e.g. <Company>.<Server>.1 to <Company>.<Server>.2, then they also have to give the server a new class id.

If the supplier of the two servers confirms that this is the same server, then your project requirements are wrong or misinterpreted since this is not how the COM architecture works.

It may give a hint if you compare the ProgIDs.

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

KarstenK3-Jul-08 3:10

3-Jul-08 3:10

I guess the coders had a sample project and had written some code but not changed the CLSIDs. Mad | :mad:

Greetings from Germany

KarstenK3-Jul-08 3:09

Avoiding global in Callbacks

3-Jul-08 3:09

Different CLSID for different modules is a primary role for COM. The CLSID should be changed if there is no compatibility in the interface!!!! D'Oh! | :doh:

You better explain the creators of the dlls that the same CLSID are crappy.

I bet that they came from the same person who hasnt enough experience to deal with COM. Dead | X|

Greetings from Germany

flip3-Jul-08 2:01

flip

3-Jul-08 2:01

Hi What is the correct way to avoid globals in accessing callbacks.
E.g.

A signal handler for ctrl-C or similar.

I have seen the boost:function and boost::bind used for user defined callbacks but I am yet it to see this being used for a standard C system library with callback.

E.g.

void sig(){};

int main()
{
signal(SIGINT,sig);
}

If sig was a member of a class is it possible to use boost::bind or otherwise so that when a signal interrupt is generated it is possible
to access the members of the class without the use of globals?

Regards,

flip

Convert Visual Studio 2005 ATL project into Visual C++ 6.0 project

dolly3-Jul-08 1:52

dolly

3-Jul-08 1:52

Hello Friends,

I have an ATL project in Visual Studio 2005, but now I want it in Visual C++6.0.

I have used one utility available on Code Project only i.e.

prjconverter.exe

it converted .sln to .dsw BUT on building the project,

I am having many error, mainly

"C:\Program Files\Microsoft Visual Studio\VC98\ATL\INCLUDE\atlcom.h(2945) : error C2065: '_Module' : undeclared identifier"

Because even in converted project,

class Coeapi_sampleModule : public CAtlDllModuleT< Coeapi_sampleModule >
{
public :
DECLARE_LIBID(LIBID_oeapi_sampleLib)
DECLARE_REGISTRY_APPID_RESOURCEID(IDR_OEAPI_SAMPLE, "{2FB8F87B-D079-497D-8948-F2F060162392}")
};

Coeapi_sampleModule _AtlModule;

BUT

what I want (generated by compiler if we build in vc 6) is

CComModule _Module;

and i read that CComModule is obsolete now, but I have to use it anyway because I have to code & build the project in Visual C++ 6.0 only not in Visual Studio 2005.

Please Help.

Thanks well in Advance!

dolly,
N,IN

Re: Convert Visual Studio 2005 ATL project into Visual C++ 6.0 project

Gary R. Wheeler3-Jul-08 1:55

Gary R. Wheeler

3-Jul-08 1:55

The simplest approach would be to create an ATL project in VC6 with the same name, and then use the wizards to add the same objects and methods. This will fill in the boilerplate code for you properly (which is probably causing most of your compiler errors).

Once you get this constructed, copy/paste the method implementations from your VS2005 project into the VC6 version.

Software Zen: delete this;
Fold With Us![^]

Wrapping a C++ LIB into a DLL

indogerman3-Jul-08 1:50

indogerman

3-Jul-08 1:50

Hi Guys,

I am trying to wrap a LIB file (content unknown, but header file is available) into a DLL, so as to be able to use it in a C# App.

I have created a C++ DLL (MFC-Shared) with the following code:

/********************* Header File **********************/

#pragma once

#ifndef __AFXWIN_H__	#error "include 'stdafx.h' before including this file for PCH"
#endif
#ifndef _DEFINED_myProg_H_  
#define _DEFINED_myProg_H_  
                                                                 
  #if _MSC_VER > 1000  
    #pragma once                                           
  #endif 
                                                                 
  #ifdef __cplusplus  
  extern "C" {                                     
  #endif 
                                                                 
  #ifdef __cplusplus    
  }                                                 
  #endif 
#endif 
#include "resource.h"		// main symbols
#include "origlib.h"		//Original Lib File


//Declaration of the function (without using classes)
bool GetList(CString *List1, CString *List2, CString *List3, int &iCount);


/******************************************************/


/********************* DLL - CPP File ***********************/


#include "stdafx.h"
#include "origlib.h"		//Original Lib File
#include "myprog.h"

#ifdef _DEBUG
#define new DEBUG_NEW
#endif

extern "C" __declspec(dllexport) bool GetList(CString *List1, CString *List2, CString *List3, int &iCount);

bool GetList(CString *List1, CString *List2, CString *List3, int &iCount);
{
		// Do work. Fill the lists with data, which has to given back from the function.
    return bVal;
}

/****************************************************************/

This DLL compiles ok.
So, i tried to test it in a MFC Test Application:

/********************* Testing - CPP File ***********************/

void CDLLTestDlg::OnBnClickedSearchbutton()
{
    CString *Arr1, *Arr2, *Arr3;
    int iDev = 0;
    GetList(Arr1, Arr2, Arr3, iDev);
}

However, here I get a linker error:
LNK2001: unresolved external symbol "bool __cdecl GetList (class ATL::CStringT<wchar_t,> blah...blah...,int &)" (?GetList@@YA_NPAV?$CStringT@_WV?$StrTraitMFC_DLL@_WV?$ChTraitsCRT@_W@ATL@@@@@ATL@@00AAH@Z)

Could anyone please help me, where I am going wrong??

Thank u soooo much Smile | :)

Re: Wrapping a C++ LIB into a DLL

Gary R. Wheeler3-Jul-08 1:58

Gary R. Wheeler

3-Jul-08 1:58

You need to add extern "C" to the function prototype bool GetList(...) in your header file. The compiler is treating that as a C++ declaration, which means a C++ decorated name is being output to the linker. The extern "C" qualifier tells the compiler and linker to treat the function as having "C"-style linkage.

Software Zen: delete this;
Fold With Us![^]

Re: Wrapping a C++ LIB into a DLL

KarstenK3-Jul-08 3:14

3-Jul-08 3:14

The linker says what you do wrong: interfacing ATL-Objects. Blush | :O

You need to have a plain interface with 'const WCHAR*' so there are no objects involved.

Greetings from Germany

BorderLess AboutBox.

Le@rner3-Jul-08 1:36

Le@rner

3-Jul-08 1:36

Hi all,

I want to show Borderless About box on initially when i run my application.

I want this About box doesn't have any border,Close button or OK button.

I want it is automatically close after sometime (like 20 t0 30 sec) and then application run .

Please tell me how can do this.

Thanks in advance.

IN A DAY, WHEN YOU DON'T COME ACROSS ANY PROBLEMS - YOU CAN BE SURE THAT YOU ARE TRAVELLING IN A WRONG PATH

CPallini3-Jul-08 1:41

CPallini

3-Jul-08 1:41

Your requirements define a Splash Window [^].
Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Rajesh R Subramanian3-Jul-08 1:42

Rajesh R Subramanian

3-Jul-08 1:42

"_$h@nky_" wrote:
I want to show Borderless About box on initially when i run my application.

I want this About box doesn't have any border,Close button or OK button.

I want it is automatically close after sometime (like 20 t0 30 sec) and then application run

In and around Mumbai, we call this a splash screen. Search CP for articles on splash screen.

Nobody can give you wiser advice than yourself. - Cicero
.·´¯`·->Rajesh<-·´¯`·.
Visual C++ MVP

CPallini3-Jul-08 2:08

CPallini

3-Jul-08 2:08

Surprisingly enough, also in Roma splash screen is a popular name for the above.
Big Grin | :-D