|
Hello,
I'm wondering if anyone could have a hint that could put up the light on me.
I've created a COM Service (COM Server & Service) and all works superbly. I access the objects on the COM service using IIS. I used to be able to debug my process as a Local Server instead of a Service by using the "-debug" command line option and that allowed me to see my coding mistakes. But i've come to a point where it works only as a Service and not as a Server.
If i use VBA from MS-Excel, i can access my object but not from IIS JScript where i used to be able to before.
Hmmmmm .. maybe if i completely unregister my proxy/stub DLL .. guess i'll try that tonite 
|
|
|
|
|
I access the objects on the COM service using IIS
hope u fixd it already.. i dont understand anything, what u mean by accessing it from IIS-JSscript..
rgds..mil10.
|
|
|
|
|
What i mean is that in IIS, if i have a server side script from which i try to instantiate my base object like:
var obj = Server.CreateObject("my.progid");
this will fail if i start my object as a server but works if it is a service. Very weird actually. Haven't had a chance to work on it yet, but i'll keep you posted.
|
|
|
|
|
Ok..ok DB, let me know how u come over that... Actually i havnt tried NT services using com exe.
But a reasonable doubt is, if the com server is running as an nt service under local system account, how can u create objects of classes in that server. because our client programs are under the users account right?, and the Nt Service is under Local system account.
rgds..mil10
|
|
|
|
|
Heheh .. the answer is simple
<br />
::CoInitializeSecurity(NULL, -1, NULL, NULL, RPC_C_AUTHN_LEVEL_NONE,<br />
RPC_C_IMP_LEVEL_IMPERSONATE, NULL, EOAC_NONE, NULL);<br />
This is in my Service_Main code just after CoInitialize(NULL)
Havent been successfull at making it work as a Local Server even after doing a full rebuild of:
1) COM Server (which is also my COM Service)
2) COM Stub/Proxy
3) IIS Filter
It used to work fine and suddenly stopped working. But its probably a little something i bugged when i toyed my registering procedure to register my LocalService key under AppID.
My COM Service is in pretty good shape now. I've learnt a great deal about COM and how to handle it. Eventually i might need to bring it forward as a DCOM application but its not a requirement yet
I appreciate all the help i've been getting from you and any others that did help me find answers, even if it wasnt done directly, like when i browsed the great articles of CodeProject. I try to repay by helping others when i can.
|
|
|
|
|
Hi db ... Congrats... keep it up and learn more...
I can understand ur raising confidence in COM programming day bi day.. keep it up... best wishes ... mil10.
|
|
|
|
|
Morning all!
I'm having a bit of a problem with the IDL file generated by VS. I'm using VS7.1 to create a COM object, but I need to edit into the IDL a importlib("") statement. This is needed as I am using another interface from another COM library.
My problem is that everytime I edit the IDL file, then build the project, the IDL file gets recreated, erasing any changes I've made!
I know I'm missing something obvious here. Any help?
I Dream of Absolute Zero
|
|
|
|
|
Ok, I've managed to locate the [importlib("")] attribute that places the corresponding entry in the IDL file. But I'm still getting unresolved type declarations from the MIDL compiler.
What are the other steps necessary to declare external COM type libraries?
Using VS7.1 C++ environment, if that makes a difference.
I Dream of Absolute Zero
|
|
|
|
|
Hi Rich!
Have you found how to do that? Keep me posted if you do!
Beers on the agenda?
Speak soon,
Jerry (the bad)
|
|
|
|
|
Hey! Welcome back!
Sorry, I still haven't found a definite solution. MSDN is great at some things, but crap at real world COM tutorials/documentation.
I decided to compromise and use an IUnknown** parameter instead (which I then QueryInterfaced for the required interface).
Beers are always on my agenda. Maybe towards the end of the month (next week onwards) we can catch up. 
I Dream of Absolute Zero
|
|
|
|
|
hello
at first i´ve to excuse my bad english, i´m from germany
i have a problem with programming com-atl-components.
i want to programm a .dll file for vb in c++. this dll should work with strings. so i look around the www and i found this:
http://www.codeproject.com/string/comstring.asp
i know, it´s the easiest way, but after a week of searching, trying and not working, it is enough 
so, my problem is: how can i use this, built in in a dll?
you know, when i make a point behind a CString object in c++ there comes a list with all the methods in the class...this is what my boss wants in vb, but i think, at first it have to work in c++.
so, please help me
enrico
|
|
|
|
|
Not sure what you want to do but let us try
a) Create an empty ATL or Com object called StringForMyBoss
b) Add to this object a property called value of type BSTR
c) Add to this object all the member functions designed in that class so you can use them from VB
Seems a bit overkill knowing that most of these functions exist in VB... but good luck!
Good luck,
Jerry
|
|
|
|
|
mmmhhh, slowly i think, i´m stupid..
i´ve try it and something works...well, in c++. i´m not ble to progamming vb and so, its the job of the boss.
you call it overkill? mmhh, boss said, in vb the stringoperations (esp. append) are too slow, c++ is more than faster...so enrico, you´re the trainee...create a dll that works for me...
i´ve never heard about this...and after more than 50 hours of searching you and another (from germany) helped me...in c++ it works, but in vb...well, it´s the boss´game 
|
|
|
|
|
ok, i have a test dll...just returning a integer. in c++ it works, but what i have to do in vb?
these are 2 methods of the dll:
[cpp]
STDMETHODIMP CTesteMal::getInteger(int* i)
{
*i=666; //working
return S_OK;
}
STDMETHODIMP CTesteMal::getIntergerDieZweite()
{
int i=666; //working
return i;
return S_OK;
}
[/cpp]
in vb i´ve tried this:
[vb]
Private Sub TRY_Click()
Dim Zahl As TESTMITINTLib.TesteMal
Zahl.getInteger () 'here is an error
End Sub
[/vb]
it doesn´t work whats my failure?
|
|
|
|
|
Dear freund,
This VB Code
Dim Zahl As TESTMITINTLib.TesteMal
roughly means in C++:
ITesteMal * Zahl;
So you need to construct your object, like this
<br />
Dim Zahl As New TESTMITINTLib.TesteMal<br />
Dim x As Integer<br />
Zahl.GetInteger x<br />
Hope this does the trick!
J
|
|
|
|
|
thanks for your help but sorry, not working
the error messege is (hope, i translate it right):
error while compiling
argumenttype ByRef incompatible
//Edit: sorry, wrong error message....
the right is:
runtimeerror '438'
object does not support this property or method
i think, it would be better to give up :/
wish you a nice weekend...and i don´t want to sit in front of a pc before monday...
|
|
|
|
|
If you give up now, you will never make it!
VB Integers are actually C++ short
So you need to declare a VB long
Dim x as Long
Your week-end will be better after this...
BTW, thanks to you, I am humming Mozart's Requiem!
|
|
|
|
|
you´re really fast
i know, that i´m not allowed to give up, but...too long time for this theme :/ and here is nobody who can help me...no c++ programmer just me
and....the error comes again...perhaps it´s in my dll...mmmhh...but now, i´ll go home
if you´re interest in helping a newbee here is my icq-number
305531731
enrico
|
|
|
|
|
LacrimaMosa wrote:
you´re really fast
Yes that's what all my girlfriends said... not something I would have wanted to go public on the www... but never mind!
Not that much time to spare, if you have simple questions, I can try to help although VB + COM are not my area of expertise!
Good luck!
|
|
|
|
|
jerry .. naughty boy..... u shud have invited enrico to soapbox or Lounge to discuss these like stunning topics......  
|
|
|
|
|
Ok, i´ve tested this and it works
Private Declare Function ReturnValue Lib "vbdll.dll" (ByVal lValue As Long) As Long
Private Declare Function ChangeValue Lib "vbdll.dll" (ByVal pValue As Long) As Long
Private Sub Command1_Click()
Dim lSendVal As Long
Dim lGetVal As Long
lSendVal = 100
lGetVal = 0
lGetVal = ReturnValue(lSendVal)
lSendVal = ChangeValue(lSendVal)
End Sub
-------------------------------------------------------
dll:
//nimmt einen wert und gibt ihn zurück
long __stdcall ReturnValue ( long lValue )
{
return lValue;
}
//erhöht den übergebenen wert um 100
void __stdcall ChangeValue ( long pValue )
{
(pValue) +=100;
}
-----------
now the problem are strings...i know, there ist a type mismatch between strings in c++ and strings in vb. but i don´t know the solution for this...something with BSTR. but in the way i´ve make my dll (look up) BSTR don´t work. somebody have a hint?
btw: @jerry: poor girlfriend-for her your surely too fast...so, bring her to me, you know how slow i am
|
|
|
|
|
I'm trying to create a program exposing it's interface to any third party software. No language limitations or assumption on the third party software can be made.The program is supposed to run as a service on a constant basis.
The program interface must reveal a way of reconfiguring/getting statistics from the program.
I'm wondering if anyone has an experience in the field of creating a program interface that will have following features:
1. Interprocess communication (Third party software will request/send information from/to my software)
2. Preferably will support remote usage. By a remote client.
One of the possible solutions is using a shared memory + event objects, but this is old and ugly approach.
Any suggestions with explanations,(COM?,COM+, DCOM?) will be highly appreciated.
|
|
|
|
|
You're looking at using DCOM.
Here's why (I might be partially wrong here):
COM: The start of COM, targets In-Process (DLL) application (Controls, etc).
COM+: Phase 2, targets out of process (Exe, Service, etc), mostly expands on OLE but makes its stronger.
DCOM: Targets remote server processes, which usually are services anyways.
DCOM is trickier to setup since you need to carefully define security and server to server security isnt easy unless you master it.
Note that its possible for a DCOM server to also act as out of process server if the caller is on the same system.
With DCOM, you need to create a COM Server that support remote calls, this add some constraints to you code but is easily controlled from the compilation of the IDL file. Then, you need to create a proxy/stub in process DLL that will run on the client system process. This stub will simply forward calls to the server using some communication protocol that you can define in "Component Services" administration applet, and then will get the replies back. If for some reason, you need callbacks, then the proxy part will catch server's calls to you process and forward them, therefore making it possible to get feedback from the DCOM server. btw, callbacks have a different name which i cant remember .. lol.
I would highly recommend that you start with a COM/COM+ application. Then, once you master the intricate details of COM, especially out of process specifics, you can mature to remote.
You can test COM/COM+ using VBA (Word, Excel, etc) or using IIS with vbscript or jscript. Note that creating an enumerator for jscript is much much more complex than it is for vbscript. I find VBA to be the simplest way to start seeing progress on your work. But IIS is easier to create sample user interface to test stuff, HTML helping here. Althought in your case, you probably just need VBA as the client.
|
|
|
|
|
I'm trying to create a program exposing it's interface to any third party software. No language limitations or assumption on the third party software can be made.The program is supposed to run as a service on a constant basis.
Any suggestions with explanations,(COM?,COM+, DCOM?) will be highly appreciated. .
Hi
COM, COM+ does not serve ur purpose of exposing an interface to a platform independent thirdparty remote client.
DCOM will do (still it is not platform independent), but it is the 20th centuary technology. Personally i won't prefer u 2 go 4 DOCM.
The 21st centuary solution for ur requirment is Webservices - the nextgen of DOCM.
If u r familiar with .NET this is just a one day work to create an XML web service in .NET. Any client app ( Sun OS, Mac OS, Linux or what ever ) can access ur service.
If .NET platform development is a concern, u can go for SOAP Webservices using SOAP toolkit. Then VB6/VC6 is enough, For this:
1) Install Microsoft SOAP Toolkit latest version on the server.
2) Just create a VB/ATL com dll with ur exposed interface, but the output of the method shud be SOAP format compatible XML text.
3) Generate the WSDL from the COM from using SOAP toolkit.
4) Expose the WSDL url as a webservice to the clients.
If u want more advanced, maintainable, scalable, distributed architecture go for SOA, Service Oriented Architecture. this is the most advanced of web services. I just mentioned for ur knowledge, no need to go for this. If u r a fresher to these techs it will take time to study SOA.
Simple Webservice is more than enough.
rgds..mil10
|
|
|
|
|
Is there a way to create a method in COM (developped in Visual C++) so I could use the operator = in VB?
In other words, once I have created my object in C++ I want to be able to write this in VB:
<br />
Dim Object1 As New MyObjectType<br />
Dim Object2 As New MyObjectType<br />
Object2 = Object1<br />
Is this possible?
Thanks in advance
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
