Unable to find an entry point

[JonR]

I have written an application that calls 'My.Computer.FileSystem.SpecialDirectories.Current UserApplicationData'. My application is working fine, but one user has reported an issue that has me stumped. When this property is accessed, the following exception is thrown: "Unable to find an entry point named 'VerLanguageName' in DLL 'version.dll'". The stack trace says that the exception came from Microsoft.Win32.UnsafeNativeMethods.VerLanguageNam e(Int32 langID, StringBuilder lpBuffer, Int32 nSize)

I don't think the problem is with my code. I suspect that there is something wrong with a system-level component on her computer, particularly with the DLL that is mentioned. Is this DLL part of a specific windows component that could be reinstalled/repaired? Any idea how to proceed? Thanks for any advice you can offer.

Jon

[!NoItAll]

It seems you are making a call into 'version.dll' and either it is missing, or has been replaced by a different 'version.dll' on her system. This is often the case with such generically named dlls. I once worked for a company that created 'system.dll' and place it into the windows\system folder. This sucker got replaced so often by poorly implemented installers that it was ludicrous.
Anyway - you may have to deploy version.dll with your application - better yet - place it directly in the same folder as your application. Do NOT register it. This way even if there is a registered version of 'version.dll' in her (or anyones) windows\system folder your application will always default to using the dll in it's own folder FIRST. This does not work with OCX files by the way.

[JonR]

Thanks for the reply. I am not making a call directly into version.dll. I am calling the standard .NET property 'My.Computer.FileSystem.SpecialDirectories.Current UserApplicationData' which in turn calls a function in version.dll.

I realize this is probably a one-off, since I should ordinarily be able to expect that most computers will not have corrupt system-level DLLs. Is there anything that I can suggest to this user that might fix this problem? (ie: does this DLL exist as part of a standard microsoft component that can be uninstalled and reinstalled?). Is there somewhere that I can point this user to get the correct version of this DLL for her system? I am concerned about the legalities (and side-effects) of redistributing microsoft DLLs with my application, or using a dll that is not compatible with her current OS & service pack.

Regards,

Jon

[!NoItAll]

@JonR
My second guess is then that you are correct about a possible corruption. Also some *other* application may have overwritten an important DLL, or there is a permissions issue on her computer. Perhaps her IT dept has it "partially" locked down in some odd fashion - in which case my advice is to let this one go. The permutations of the cause of this error could be endless!