|
Sir,
S/W Engineer
Akebono Soft Technologies
aleem_abdul@akebonosoft.com.
|
|
|
|
|
Please don't cross post. We have asked you before.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Dear sir,
I have done the assembly registration and gac intallation in two steps, but I am getting error as
* Failure adding assembly to the cache: An attempt was made to load a program with an incorrect format. *.
Please tell me what could be the reason, and where I might have done mistake. The steps I did are as below.
No. 1 C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin>sn -p D:\Aleem\DSOControl1\DSOControl1.snk
D:\Aleem\DSOControl1\DSOControl1.dll
Microsoft (R) .NET Framework Strong Name Utility Version 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
Public key written to D:\Aleem\DSOControl1\DSOControl1.dll
No. 2. C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin>gacutil /i D:\Aleem\DSOControl1\DSOControl1.dll
Microsoft (R) .NET Global Assembly Cache Utility. Version 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
Failure adding assembly to the cache: An attempt was made to load a program with an incorrect format.
Regards,
S/W Engineer
Akebono Soft Technologies
aleem_abdul@akebonosoft.com.
|
|
|
|
|
Please don't cross post. We have asked you before.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
|
Thank you sohail, but if you have more please give me. I am not suire it will be 100% for it. Because, I am struck here, give me few more links for getting out of this, please.
Regards,
S/W Engineer
Akebono Soft Technologies
aleem_abdul@akebonosoft.com.
|
|
|
|
|
I don't want to sound rude here but
- I gave you search results from Google. Strong Name assemblies is part of .NET concepts. I am not too familiar with .NET so can't explain you. You will need to search (Google) and read the articles correctly, it will solve all your queries. I see your problem more about not knowing the details/concepts and it really is no glitch in your app, so please read the articles on "Strong Name". You need to help yourself by understanding how to do and not just get some solution which you can use directly.
- You seem to be cross posting across forums. This is not appreciated on CodeProject. Best would be to find appropriate forum and someone will answer you soon. Cross posting will only not earn you respect nor any answers here!
The MSDN forum link I mentioned shows how to generate Strong Name assemblies. Please ready it completely.
After you do the above things, still if you are stuck, post in correct forum and people will be glad to help you.
warm regards
S o h a i l K a d i w a l a
To Err Is Human; to Debug, Divine
modified 21-Apr-21 21:01pm.
|
|
|
|
|
Sorry Sohail for troubling all, but It seems could able to get it, because I have converted the activeX in to .Net assembly and installed in to GAC. The only thing left is I should be able use it in my application. Please pray for my success. Thank you.
Regards,
S/W Engineer
Akebono Soft Technologies
aleem_abdul@akebonosoft.com.
|
|
|
|
|
Please don't cross post. We have asked you before.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Please don't cross post. We have asked you before.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Hi,
I am trying to programmatically re-start a COM+ application using VBScript
and "COM+ Admin" automation library. In Win XP, its all taken care by COM+ itself
when you set the "Pooling & Recycling" properties. But in Windows 2000,
scripting seems to be the only way. An outline of the script:
<br />
Set catalog = CreateObject("COMAdmin.COMAdminCatalog.1")<br />
catalog.ShutdownApplication("My Appln")<br />
catalog.StartApplication("My Appln")<br />
The restart works fine but the active clients at the time of restart are
terminated abruptly. Is there anyway that I can do a graceful restart?
Or in other words, can i somehow get the number of active instances of each
component in a package, so that the script can wait till this count becomes zero,
before restarting ? I tried the other automation library "COM+ Services", but no clue.
Thanks in advance.
Regards,
Venkat.
|
|
|
|
|
I think you'll need to look at the COM+ Events & Statistics API to do this.
Alternatively you could just do the restart, then in your client application(s) check the returned HRESULT for (I think) RPC_S_SERVER_UNAVAILABLE, at which point the client could (re)CoCreateInstance the required object.
|
|
|
|
|
can anybody help me with the iso-8583 information?
thx
|
|
|
|
|
|
Hi
I wanna know that how can i create OLE Servers within my application.
I mean i wanna make my application insertable as OLE Server
Hope somebody answers me soon.
Bye
pitchu
|
|
|
|
|
Then study COM. There are a plethora of books about.
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.
|
|
|
|
|
Hi
I wanna know that what is the difference between the different technologies exposed by Microsoft, i mean
COM / ActiveX / OLE
Is it like this they are selling old wine in new bottles
Hope some body answers me soon
bye
pitchu
|
|
|
|
|
wasim ahmad bhat wrote: selling old wine in new bottles
Yes, mainly.
A nice introductory description is given in the following book (if I remember well):
[^]
The following sentences, quite poor, may give a glimpse:
COM (Component Object Model) is the model the other two tecnologies rely on. However, historically, OLE comes before COM (at least as name). ActiveX was, loosely speaking, a marketing move. It indicates the COM controls available for using on internet.
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.
|
|
|
|
|
|
I have a Automation class present in local Automation server. This class has following method
VARIANT_BOOL IsWorking();
which is part of a dispinterface.
I have a MFC Client which contains a wizard generated class that derives from COleDispatchServer. This class represents the above mentioned Automation Class. The wizard generated code for this method is as follows -
BOOL IsWorking()<br />
{<br />
BOOL result;<br />
InvokeHelper(0x2, DISPATCH_METHOD, VT_BOOL, (void*)&result, NULL);<br />
return result;<br />
}
now every call to IsWorking() method always returns 1 ( IsWorking() returns VARIANT_TRUE and VARIANT_FALSE correctly. I have verified this by debuggin server code ) . VARIANT_TRUE and VARIANT_FALSE are being transalted somewhere during the call being completed from servers side.
Any guess what I am missing here?
Second, I tried making the return type as void and instead return the boolean as an OUT param as VARIANT_BOOL*
In this case, i get invalid pointer address inside my server's
void IsWorking(VARIANT_BOOL* pRetVal) method
hence resulting in access violation.
What could be the problem in this case.
S o h a i l K a d i w a l a
To Err Is Human; to Debug, Divine
modified 21-Apr-21 21:01pm.
|
|
|
|
|
Do you explicitly use the VARIANT_BOOL type in the .IDL file as well?
Anyway, you should if you're not.
It could be a mixup between the use of boolean which is defined as an unsigned char and BOOL which is defined as a long for MIDL.
If you've checked the option to be MkTypLib-compatible you'll run into problems since for MkTypLib BOOL, boolean and VARIANT_BOOL are defined as short.
You need to delete the wizard generated files when you change the interface and run the wizard again.
--
Roger
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"No one remembers a coward!" - Jan Elfström 1998
"...but everyone remembers an idiot!" - my lawyer 2005 when heard of Jan's saying above
|
|
|
|
|
Thanks for your answer.
Roger Stoltz wrote: Do you explicitly use the VARIANT_BOOL type in the .IDL file as well?
Anyway, you should if you're not.
Yes, I am explicitly using VARIANT_BOOL and not any other boolean type since I read about VARIANT_BOOL usage. FYI, the app i am working on is an old app and has an ODL file and not IDL. MIDL config uses "/mktyplib203" - MKTypLib compatible option.
Roger Stoltz wrote: It could be a mixup between the use of boolean which is defined as an unsigned char and BOOL which is defined as a long for MIDL.
I doubt about the mixup because all method and interface and wrapper classes decalarations were generated using MFC wizard and has no modifications
Roger Stoltz wrote: You need to delete the wizard generated files when you change the interface and run the wizard again.
Yes, I deleted and re-generated everytime.
-- modified at 13:02 Tuesday 9th January, 2007
Further information - the return value "pvarResult" changes to (True, VT_BOOL) after this call (MFC source, File: oledisp2.cpp, Line# 373) -
SCODE sc = m_lpDispatch->Invoke(dwDispID, IID_NULL, 0, wFlags,<br />
&dispparams, pvarResult, &excepInfo, &nArgErr);
Though, now I have hard coded the return value in the function to return VARIANT_FALSE everytime!
S o h a i l K a d i w a l a
To Err Is Human; to Debug, Divine
modified 21-Apr-21 21:01pm.
|
|
|
|
|
Sohail Kadiwala wrote: I doubt about the mixup because all method and interface and wrapper classes decalarations were generated using MFC wizard and has no modifications
Don't be too sure about this one. At least one of the wizards puts boolean as type when a method is added and you select BOOL as type, even if the interface has the attribute [oleautomation]. The result is that it won't even make it through the MIDL compilation: an error is generated and you'll be asked to use VARIANT_BOOL instead of boolean in automation interfaces.
I would really like to see the declarations in the .odl, .h and the wizard generated header file for the client.
Sohail Kadiwala wrote: Further information - the return value "pvarResult" changes to (True, VT_BOOL) after this call (MFC source, File: oledisp2.cpp, Line# 373)
This rings a bell quite loudly... I've seen this problem before, but I cannot remember what the solution was.
I have a vague memory that it was really about the mixup of boolean types and marshalling.
Can you describe the relationship between your server and client a little bit further? EXE-server? Threads? The need for marshalling?
The name IsWorking suggests that it could be multithreaded...
--
Roger
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"No one remembers a coward!" - Jan Elfström 1998
"...but everyone remembers an idiot!" - my lawyer 2005 when heard of Jan's saying above
|
|
|
|
|
Roger Stoltz wrote: I would really like to see the declarations in the .odl, .h and the wizard generated header file for the client.
SERVER code is below -
dispinterface ISomeInterface<br />
{<br />
properties:<br />
methods:<br />
[id(1), helpstring("")] void Start(BSTR str);<br />
[id(2), helpstring("")] VARIANT_BOOL IsWorking();<br />
};
Start actually starts an asynchronous activity on the server. I use IsWorking method to determine whether the activity is over or not. In my client, when a request is recieved for another "start", I need to check whether the Server is already working, if yes, then I need to wait in my client. Server notifies the Client about activity completion through COM event source/sink mechanism. So in short, IsWorking determine whether the client should wait or not before issuing any requests
In Server's SomeInterface.H file, following is the declaration
void Start(LPCTSTR str);<br />
VARIANT_BOOL IsWorking();
Client code generated by Wizard -
void Start(LPCTSTR str)
{
static BYTE parms[] = VTS_BSTR ;
InvokeHelper(0x1, DISPATCH_METHOD, VT_EMPTY, NULL, parms, str);
}
BOOL IsWorking()
{
BOOL result;
InvokeHelper(0x2, DISPATCH_METHOD, VT_BOOL, (void*)&result, NULL);
return result;
}
Roger Stoltz wrote: This rings a bell quite loudly... I've seen this problem before, but I cannot remember what the solution was.
I have a vague memory that it was really about the mixup of boolean types and marshalling.
While Googling for hours, I got this thread which is similar but the Class and file in talk though similar, is different. Check following thread -
http://groups.google.com/group/microsoft.public.vc.mfc/browse_thread/thread/fa6cffd879ac26da/1564231c27c4667a?lnk=st&q=V_BOOL(&rnum=10#1564231c27c4667a[^]
Roger Stoltz wrote: Can you describe the relationship between your server and client a little bit further? EXE-server? Threads? The need for marshalling?
The name IsWorking suggests that it could be multithreaded...
The EXE server is created in MFC and it has exposed SomeInterface class which is CoCreatable. The Client could be any client, I have -
1. ActiveX component which is client to my server. And this control is placed inside C# application. ActiveX component is written in MFC
2. I have created a Simple MFC EXE with FormView, which directly calls the methods of the EXE server. This is did just to ensure there is not threading or marshalling issue because of Managed C# code. But the problem occurs in both the Managed client with ActiveX control or Unmanaged client
The coclass has no threads. The Exe server is multithreaded but the coclass Start method simply delegates the call there.
My clients are single threaded.
Regarding marshalling, I believe standard marshalling should take care of this because i am using the OleAutomation compatible type.
Everything works fine for Start method and I succesfully get the "BSTR" from my clients hence I see no issue about marshalling.
To me it seems like a bug some problem as discussed on the thread I have mentioned above. I think the problem is somewhere in IDispatch::Invoke code. I should avoid calling it a bug till I am sure about this 
As of now, I have converted the return type to LONG and everything is working fine. I can proceed further on the original code. I have created a sample application which I can use to diagnose this issue with you side-by-side.
S o h a i l K a d i w a l a
To Err Is Human; to Debug, Divine
modified 21-Apr-21 21:01pm.
|
|
|
|
|
Regarding your declarations, I cannot find anything wrong: it looks as expected.
N.B. I'm not quite convinced yet. I think the problem described in the forum discussion you found could be a consequence of this mixup. The reason why I'm not sure is because it's an .odl file and you want to be compatible with MKTypLib and I'm not 100% on top of what happens then.
So, the server is an out-of-process server.
This means that every call has to be marshalled.
Sohail Kadiwala wrote: The coclass has no threads. The Exe server is multithreaded but the coclass Start method simply delegates the call there.
I don't exactly know what you mean by these statements, but I guess you mean that you do not initialize more than one apartment in the server and that is in the application thread of the server. I hope this also means that you do not call any interface functions from anywhere else than from that thread, even if you're talking about an event sink.
Tell me if this is not the case.
Sohail Kadiwala wrote: Regarding marshalling, I believe standard marshalling should take care of this because i am using the OleAutomation compatible type.
Well, if you haven't built and registered anything else explicitly, the universal marshaller will be used for automation interfaces. This is also known as type library marshalling. Standard marshalling requires you to build a second DLL with the proxy/stub.
I assume you're using typelib marshalling, which is exactly why I was talking about a mixup between boolean types since the generated typelib will be used for marshalling. I think you can figure out the rest if I present the problem as "you may declare a return type as 16-bit wide in your code but 32-bit wide in the typelib".
Sohail Kadiwala wrote: Everything works fine for Start method and I succesfully get the "BSTR" from my clients hence I see no issue about marshalling.
This is not proof of anything other than the call to Start seems to work. The call to IsWorking may still be erroneous even though it looks OK as mentioned above.
I would like to follow up on the forum discussion you found. I think there might be something there to try out.
If you change the type back to VARIANT_BOOL and put a breakpoint after the call is made in oledisp2.cpp, line #373. Try forcing the server to return VARIANT_FALSE and VARIANT_TRUE every second time you call it. Take a look at the lower 16 bits of the return value. It should change between 0x0000 and 0xffff. The upper 16 bits could contain garbage which would make the return value evaluate to true even if VARIANT_FALSE is returned.
What happens? What type is returned (VT_BOOL) and what is the value of it?
Let's first find out what is returned and how it's wrong and then we can try and find the correct solution for it.
--
Rog
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"No one remembers a coward!" - Jan Elfström 1998
"...but everyone remembers an idiot!" - my lawyer 2005 when heard of Jan's saying above
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
