yes because the dialog box app compiles and runs by itself without any errors? so its defined there and working [edit] ok its compiling now, all I did was repalce the #include ...filedlg.h with #include ....filedlg.cpp, and am not getting the erorr anymore. will see if its running properly once I create a test file using that dll. thanks for the help for now _AnsHUMAN_. if you have anything to add regarding this, please do so that I may know what you had in mind [/edit] modified on Thursday, July 16, 2009 7:41 AM

Funny that you should mention it. I did have a backup of a native code which simply signed data, and worked as I wanted/expected it to, it would generate the signed hash as expected. But after I ran this (managed) project a few times (in a separate VS 2008), I went over to test my native application, which surprisingly now, also started giving me this same error. I assume it's a bug of having porting my project from VS 2005 to VS2008.

No, the class I referred to is not managed code. It is a crappy thing, but it's life -^ Carlo Pallini

Until you call fOpenDlg.DoModal(), your code is pointless. That aside... sadman89 wrote: CString fName = NULL; Why are you assigning NULL to a non-pointer? Not sure how this even compiles. sadman89 wrote: name = *fName; This makes no sense. sadman89 wrote: name = (fName+""); Nor does this. "Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

ok i tried that (and _bstr_t(..)) still the verification is displaying a 0 :confused:   i guess the cast(?) is fundamentally correct, but its still not giving me the expected output. I also looked at the excellent http://www.codeproject.com/KB/string/cppstringguide2.aspx for some new ideas but no luck :( darn this COM and the lack of help from Microsoft modified on Monday, June 22, 2009 4:01 AM

yeah i got the data to sign now, but im stuck with verifying the data, i googled it and couldn't find a satisfactory solution for it. seems to have something to do with capicom being made for java and all so the way its handling or data is different than c++ (ascii vs unicode) so im stuck there now lol. thanks for the concern though

yes I'm using mfc, atleast learning about it as I go along with this

will do. thanks :)