Problem is this || IID_ICredentialProviderSetUserArray when i call IID_ICredentialProviderSetUserArray interface through Quareyinterface dll is crashing without implementing ICredentialProviderSetUserArray interface dll is working is fine .
CSampleCredential **_rgpCredentials; // Pointers to the credentials which will be enumerated by this
ICredentialProvider *_pWrappedProvider; // Our wrapped provider.
DWORD _dwCredentialCount; // The number of credentials provided by our wrapped provider.
DWORD _dwWrappedDescriptorCount; // The number of fields on each tile of our wrapped provider's
ok but that is not problem when i called ICredentialProviderSetUserArray ==riid probblem is occurring
if (IID_IUnknown == riid ||
IID_ICredentialProvider == riid ||
Are you certain that the old object is not getting out of scope when you create new. When you create multiple objects, chances are that you are not maintaining reference counts correctly so there is a small chance that object is actually removed or marked for removal when client attempts to access ...
But for e.g. HrIsProtected() I need to provide an implementation of ILockBytes. Has anybody experience how to correctly implement ILockBytes in managed code? I am a bit at a loss as to what is expected here.
For unmanaged code I found a sample that uses CreateILockBytesOnHGlobal(). This returns an unmanaged instance of ILockBytes. Is there any chance of using this unmanaged instance from managed code (probably not...) or marshalling it into a managed structure? Or is there a similar method for C#? In that case I wouldn't have to implement ILockBytes, which would save me a lot of time.
Of course, I could implement this part in unmanaged code, but I'd prefer a solution in managed code, if possible...
Does any one knows how to compile COM for VB6, my application contain one .Fig file as interface and .m file containing code and
one Excel file for data.
My problem is how to compile all together in dll which i can call
I recently upgraded my project from .net 3.5 to 4.0. My Word Interop Assembly was working on client machines just fine in .net 3.5. After upgrading to .net 4.0 I changed the Embedded Interop Types property to false. Now some clients are looking for Interop.Microsoft.Office.Core when previously they weren't. My question is how come the clients are looking for this assembly with .net 4.0 when they weren't in .net 3.5?
I have created a class in c# to replace a vb6 class used in an asp web page. Note I said asp and not asp.NET. I am running this in IIS 7.5 on a 64 bit Windows 7 machine.
I compiled the program and all its support dlls as x86 and believe I got all the correct tags and check boxes for COM. I can create and use the class in VB6 but it still bombs in vbscript with can't create object. I found some articles on going to do tweaks in the registry to get it to work on 64 bit but alas no avail.
The web application will run with the old VB6 object just fine. The configuration is an application with a separate pool set to pipeline mode classic, no managed code, enable 32 bit applications = true;
Initially I was getting a can not create object when trying to use the new c# object but I copied the dll and its support dlls to the sysWOW64 directory and it changed it's tune to
MaxRecall.Shared error '80004003'
Object reference not set to an instance of an object.
/mr/mrq.asp, line 193
the structure of the project is thus
the object I am creating with createobject is dependent on a single assembly, MaxRecall.CORE, which is dependent on two assemblies, MaxRecall.CLIENTS and MaxRecall.Shared. None of the support assemblies are com exposed so this error is not a COM error at all I think.
MaxRecall.Shared is totally static with zero objects to create. It only had two static doubles that were class scoped that were not instantiated but I set them to 0 in their declarations. To my thinking there are no objects in MaxRecall.Shared to gain an instance to so the error is odd.
Sigh. Any and all insights are desperately welcomed. I cross posted this in the ASP.net section.
Last Visit: 31-Dec-99 18:00 Last Update: 3-Oct-22 1:25