|
First note that the proxy-stub you built is creatable:
K ARUN KUMAR wrote: [HKEY_CLASSES_ROOT\CLSID\{A12EAEC2-2B64-470B-93AF-EFE0855DD3AC}\InProcServer32]
@="D:\\VC++\\Sample Applications\\BytComp\\DebugPS\\BytCompPS.dll" "ThreadingModel"="Both"
But your interface isn't using it:
K ARUN KUMAR wrote: [HKEY_CLASSES_ROOT\Interface\{A12EAEC2-2B64-470B-93AF-EFE0855DD3AC}\ProxyStubClsid32]
@="{00020424-0000-0000-C000-000000000046}"
{00020424-0000-0000-C000-000000000046} is the universal marshaller, not your proxy-stub ({A12EAEC2-2B64-470B-93AF-EFE0855DD3AC}).
Also I notice your interface is marked with [dual]. This means the interface has to be automation compatible and should only use a limited number of types (which doesn't include BYTE arrays).
Do you get warnings when you compile the IDL file? Did you ignore them?
Since you exported these keys you're free to tinker with them as they can easily be restored using the exported files.
Change this key:
[HKEY_CLASSES_ROOT\Interface\{A12EAEC2-2B64-470B-93AF-EFE0855DD3AC}\ProxyStubClsid32]
@="{00020424-0000-0000-C000-000000000046}"
So that it looks like this:
[HKEY_CLASSES_ROOT\Interface\{A12EAEC2-2B64-470B-93AF-EFE0855DD3AC}\ProxyStubClsid32]
@="{A12EAEC2-2B64-470B-93AF-EFE0855DD3AC}"
NOTE: Don't alter the exported files, make the changes in the registry. Alternatively copy the exported file, make the change in the copy, then double click the copy.
Steve
|
|
|
|
|
Hi Steve,
You are amazing. The change worked.
But when iam building the server,
it again modifying the registry
setting to default Marshaller GUID.
How to set my ProxtStub GUID as default?
|
|
|
|
|
The problem is your interface is marked as an automation interface but it uses types that are not automation compatible. As I said, I'm sure the MIDL compiler would have warned you about this, and you should always investigate compiler warnings. The are a number of ways to fix this:
- Don't use an automation compatible interface. Remove the
dual and all the [id] attributes, and derive from IUnknown instead of IDispatch. You will not need the IDispatchImp base class in you server implementation either. - Add another interface to the object (which isn't
dual and derives from IUnknown, as described above) to contain the non-automation compatible methods. - Manually make the changes I described after RegisterTypeLib[^] makes the "wrong" ones. This is a hack though: why use an automation-compatible interface that automation clients will not be able to call?
- Give my posts good marks
Steve
|
|
|
|
|
Thanks a lot buddy.
Sure..
Arun
|
|
|
|
|
Hi,
I've a windows class library and would like to create ActiveXControl for that. I regstered the dll using RegAsm.exe and created the below html in local IIS(wwwroot) and accessed. But its not showing the design.
Please let me know if I missed any steps in creation of ActiveXControl. Thanks in advance.
<html>
<body color=white>
<hr>
Please note that you MUST load this HTML document from your local IIS, or from a TRUSTED SITE <hr>
<font face=arial size=1>
<OBJECT id="myControl1" name="myControl1" classid="0AE91E82-5EE3-4d27-B7ED-CE2C0B059BB7" width="500" height="200">
</OBJECT>
</font> <hr>
</body> </html>
classid is the GUID of the class.
In one of the class, I declared the GUID as below.
[ Guid("0AE91E82-5EE3-4d27-B7ED-CE2C0B059BB7"),
InterfaceType(ComInterfaceType.InterfaceIsDual),
ComVisible(true)]
|
|
|
|
|
<object id="myControl1" classid="CLSID:0AE91E82-5EE3-4d27-B7ED-CE2C0B059BB7" <="" object="">
Also, if your activeX is not signed, ensure your browser's security level is set to low, and unsigned activeX controls are allowed to load.
|
|
|
|
|
I tried the above as per your message. Still the problem exists..
|
|
|
|
|
Hello,
Instead of IDispatch, If I have some COM component that exposes its methods through IUnknown, can we call its methods at runtime? Problem is Invoke memeber only available in case of IDispatch
Regards
Usman
|
|
|
|
|
Hello,
I am getting address of COM function by loading type library (TLB) and iterating over types using ITypeLib and ITypeInfo.
After calling AddressOfMember function of ITypeInfo I am facing following exception:
System.Runtime.InteropServices.COMException (0x800288BD): Wrong module kind for the operation. (Exception from HRESULT: 0x800288BD (TYPE_E_BADMODULEKIND)) at System.Runtime.InteropServices.ComTypes.ITypeInfo.AddressOfMember(Int32 memid, INVOKEKIND invKind, IntPtr& ppv).
Any idea how to get rid of this excpetion?
for (int curFunc = 0; curFunc <iTotalfunc ; iTotalFuncs;curFunc++)
{
try
{
IntPtr ppFuncDesc;
oTypeInfo.GetFuncDesc(curFunc, out ppFuncDesc);
funcDesc = new System.Runtime.InteropServices.ComTypes.FUNCDESC();
funcDesc = (System.Runtime.InteropServices.ComTypes.FUNCDESC)Marshal.PtrToStructure(ppFuncDesc,typeof(System.Runtime.InteropServices.ComTypes.FUNCDESC));
int cNames;
//if (funcDesc.)
oTypeInfo.GetNames(funcDesc.memid, m_strFuncNames, 1, out cNames);
switch (funcDesc.invkind)
{
case System.Runtime.InteropServices.ComTypes.INVOKEKIND.INVOKE_FUNC:
//Console.WriteLine(" (method)");
//_infoType = "Function";
//_property = false;
string strSignature = "";
if (funcDesc.cParams> 0)
{
IntPtr addrssOfMember;
oTypeInfo.AddressOfMember(funcDesc.memid, //Here where exception occured System.Runtime.InteropServices.ComTypes.INVOKEKIND.INVOKE_FUNC, out addrssOfMember);
}//end of if
}//end of switch
}//end of try
}//end of for
Regards
Usman
-- Modified Friday, May 14, 2010 3:06 AM
|
|
|
|
|
hi,
I need to do language localization using XML in VC++ (MFC).
I need to do mapping using XML file and i need to scan the XML file for the desired language, so that my output would be in my desired language.
I have no idea, how to go about it.
Please Support
|
|
|
|
|
|
Hello,
I need to write type libraries in C#.NET. Type library is of unmanaged COM servers. How..?
Regards
Usman
|
|
|
|
|
Type libraries can be accessed using the ITypeInfo and ITypeLib interfaces.
From C# you can do COM interop to use these interfaces.
Here is a good article on COM Interop[^].
|
|
|
|
|
#include "stdafx.h"
#include "windows.h"
Hi All,
In the below mentioned code. i want to use MSCOMM32.OCX file API to my C++ code.
i am facing an issue when i am getting HResult from the cocreateInstance.
Kindly let me know what should i do to access MSCOMM32.OCX API.
#include "atlbase.h"
#import "C:\\WINDOWS\\system32\\MSCOMM32.OCX" no_namespace raw_interfaces_only raw_native_types no_implementation named_guids
int main(int argc, _TCHAR* argv[])
{
GUID iid = {0xE6E17E90, 0xDF38, 0x11CF, 0x8E, 0x74,0x00,0xA0,0xC9,0x0F,0x26,0xF8};
GUID Clsid = {0x648A5603, 0x2C6E, 0x101B, 0x82, 0xB6, 0x0,0x0, 0x0, 0x0, 0x0, 0x14};
IMSComm **ppv = 0;
HRESULT hRet = 0;
hRet = CoInitialize(NULL);
hRet = CoCreateInstance (Clsid, NULL,CLSCTX_LOCAL_SERVER,iid,(void**)&ppv);
_bstr_t pbstrSettings("9600,N,8,1");
(*ppv)->put_PortOpen(1);
(*ppv)->put_Settings(pbstrSettings);
(*ppv)->AboutBox();
return 0;
}
|
|
|
|
|
The activeX is probably not registered.
Which OS are you using?
Open a command prompt with admin privileges, change to the system32 directory and type the command regsvr32 mscomm32.ocx.
|
|
|
|
|
pallaka wrote: hRet = CoCreateInstance (Clsid, NULL,CLSCTX_LOCAL_SERVER,iid,(void**)&ppv);
As a rule, OCX is an in-proc server.
With best wishes,
Vita
|
|
|
|
|
I have read that COM+ is not portable. It is tightly coupled.
Please provide me a pointer to understand this better.
I gather that, COM+ which is a runtime environment should be tightly coupled
with the operating system.
Why I am confused is because, ultimately COM+ is based on components and
components are binary and ready to use that can move across dlls and
across machines ... so where is tight coupling?
Regards,
Net Questions
|
|
|
|
|
|
Hi Mike,
COM+ runtime environment is supported only by microsoft.
With regards to the component that I create say using the ATL languange or C++, can it or not run on other platforms?
Regards,
Net Questions
|
|
|
|
|
Disclaimer:
I've been breaking into developing via the C# language for about 7 months now, so take it easy on me.
I am writing an add-in to a 3D CAD program called Autodesk Inventor. It has a COM API and they (Autodesk) provide a nice project template to start from which includes the proper references as well as some pre-baked code to get you started. I have been succesfully coding against it for a couple of months now and I have decided to try out the new C# 4.0 language features that just came out with VS 2010. I'm really liking the named and optional parameters, but I digress.
When debugging, I start up an Inventor.exe session which, in short, looks to the registry and finds my add-in and loads it. The problem I'm having is actually hitting a breakpoint in my code while debugging. I have gone through several different property settings on the referenced InventorInterop.dll as well as options on debugging (among other trial and error things), none of which seems to work. The only thing that works is when I go back to an earlier .NET framework (i.e. not 4.0).
I have tried this on other *sample* add-ins that come with the SDK and the same thing happens. The add-in loads and code gets executed, but the breakpoints don't get hit when targeting the .NET 4.0 framework.
Is this a problem with me, the COM interop, or something else altogether?
Thanks in advance.
-Brian Hall-
|
|
|
|
|
Hello Folks,
I'm working on a C++ project that requires me to unmount and remount volumes on a flash drive, and from what I can tell, the system services I need to access are implemented using COM.
http://msdn.microsoft.com/en-us/library/cc227526(v=PROT.10).aspx[^]
I believe that I am supposed to create an IVolumeClient object using CoCreateInstance, and then use that object to communicate with the Disk Management server.
My confusion comes when I try to find any kind of interface to IVolumeClient on my development machine. Where would I find a C++ header file for the IVolumeClient interface, and where would the proper CLSID and IID values for CoCreateInstance be found?
Thanks for your time,
Ron Aldrich
|
|
|
|
|
Good Question. I've searched the whole DDK, and I can' t find one. the Interface is however defined in full (including CLSID) in the open specification you refer to (look in Appendix A, 6.1 full dmintf idl)
May I however suggest another (supported) approach to this: (the open spec is for information only)
Starting with server 2003, you can use WMI to mount/unmount volumes : http://msdn.microsoft.com/en-us/library/aa392400(v=VS.85).aspx[^]
The thing that confuses me is that the documentation states: no client operating systems supported, but this may be an artefact of the age of the documentation (the documentation may not have been updated since this function was implemented, and this may only indicate that at the time of the implementation, there were no clients supporting this).
If all else fails, you can always use the mountvol.exe utility, have look at the answer in http://www.codeproject.com/Messages/3443352/Re-How-to-get-the-hidden-drives-in-windows.aspx[^] (I believe mountvol uses WMI, that's why I think it's supported in Vista and Windows 7.
If you have to go beyond server 2003, you could use FSCTL's to do your mounting, have a look at this article:
Inside Mountvol.exe[^] Although this primarily deals with registering the reparse points as a normal user. (this can't be done, for security reasons), however the drive letters (a: b: c: ...) are pre-existing, so they require no privileges to mount. Running you program as administator will help anyway (always needed for the registration of a reparse point).
A lot of this is educated guesswork (I haven't tried it) but this should set you on your way...
|
|
|
|
|
Thanks Michel,
That helps, but I'm still not sure I'm looking in the right area.
Here's my problem:
I'm changing the write protect state on a USB flash drive, using vendor unique SCSI commands. In order to do so safely, I'm looking at 3 (or four) steps.
1) Unmount the drive's volumes (Hopefully this will be adequate to insure that all caches are flushed).
2) Change the drive's write protect state (vendor unique SCSI command).
3) Remount the drive's volumes.
It's possible that I'll also need an additional step.
2b) Somehow, magically, convince the drive's device driver that it needs to reestablish its write protect state.
Now for the hard part:
All of this has to work on Windows XP, Windows NT and Windows 7. Support for Windows Server flavors is optional.
Ideally, this has to work on a user account, without administrator privileges.
I guess my first task is to determine whether or not this is even possible.
Thanks for your time,
Ron Aldrich
Software Architects, Inc.
|
|
|
|
|
WOW, who sold you this job? were you sober?
Taking it in order.
1) Unmounting the drive will flush the caches. Of course the SCSI standard allows surprise removal so, you never can tell.
2) Issuing SCSI commands. You should be able to issue any SCSI custom command through IOCTL passtrhru interface if the drive is not mounted. How this is affected by security and passwords, I'll be honest: I don't know. You may well require elevated priviliges to do this from user mode.
3) Remounting volumes: should be no problem if you have chosen a drive letter or a reparse point previously. If the drive (well the drives's GUID, really) has not been mounted before, you need elevated privileges to put in the HKLM section of the registry. Also take a look at the automount status (which I think you can see in mountvol, or diskpart. (not too sober myself)).
2B) reestablish write protect. Well I suppose there's a custom SCSI for that one too? Of course if your thingy i s already mounted, you may require elevation. Scratch that, if your drive is already mounted R/W, write protecting it afterwards will cause the file system driver (FAT32, NTFS) to have a nervous breakdown. You won't believe how these things can fill your event log with messages of doom.
Ron Aldrich wrote: All of this has to work on Windows XP, Windows NT and Windows 7
Which Windows NT? If you're talking about 3.1 or 3.51, I've worn out the CD's to put my ashtray on. (Actually I seem to remember they still came on floppys). Windows 2000 has left supported status when William Shatner had to hand over the keys of the USS Enterprise. Your best bet is XP service pack 3. It postdates server 2003 (when all the goodies were introduced) and should have all the nice OS interfaces, without having to write your own device drivers.
Without user privileges: actually I think this is feasible, providing that you have an install program that handles the messy bits like doing initial mounts, establishing HKLM keys.
Ron Aldrich wrote: I guess my first task is to determine whether or not this is even possible.
Funny you should say that. Today I gave some advice to a rookie, which was exactly in line with what you're saying now. Of course I'm not implying you're a rookie, but this might amuse you: http://www.codeproject.com/Answers/76089/this-is-a-network-analyzer-how-do-i-Dnslookup.aspx#answer3[^]
If you're really looking at targeting pre-XP SP3 releases then the Open Specification document to which you referred may be be your only chance. But remember that these open specifications are not cast in stone. These docs were only produced by M$ because they were forced do to so by the EU. Support will be patchy, at best.
Good luck
If you send me a private reply on this message, you'll get my email address by returning mail. (putting addresses on the internet is never a good idea. (Can I interest you in some Cialis or Viagra?)
PS, to clear some confusion: you don't mount a drive. A drive is a physical thing which contains partitions. A drive is either offline or online. When it's online it can be controlled by the device manager. Partitions can be mounted or dismounted on reparse points (drive letters, empty NTFS directories) when the drive is online...
|
|
|
|
|
Hi,
I am working on a plug-in for IE that can capture and manipulate requests, before sending them to server, just like Tampar IE.
Kindly provide some help in this regard.
A step-by step would be highly appreciated as I am a novice in this domain.
TIA
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
