my dll is custom credential provider .this dll provide a link in windows logon screen,this link will display win32 dialog with custom control.this is working for windows 7 32&64 bit and windows 8 32bit.but 64 bit windows 8 every thing is coming fine dialog only not displaying .
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?