Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > LoadLibrary() failure
 

LoadLibrary() failure

I'm using the excellent NHunspell spell checking API in a click-once C# Win Forms application. (Word automation is a broken mess.) NHunspell is a wrapper around the Hunspell spellchecking library used by Open Office. It first determines whether to load a 32-bit or 64-bit library based on the machine. It assumes that all the files are in the AppDomain.CurrentDomain.BaseDirectory (and they are being properly installed to the same location.) For one user (and that user only) the LoadLibrary() API fails when it attempts to load the proper library file. It works for me and several others but always fails for that one machine. Does anyone know of other instances of LoadLibrary() failing from one of the crazily named click-once installation directories? Could the path be too complex? Any ideas appreciated except telling me to abandon click-once!
CCPoston  Wednesday, August 12, 2009 2:51 PM

Hi CCPoston,

As far as I know, the path can cause the error if it contains some special characters. For example, if the path contains a period(.), the call of LoadLibrary would fail. You can get the details from: http://support.microsoft.com/kb/324468.

Could you please provide more information about the differences between the machines on which the program can be installed successfully and the machines on which the installation would fail? This can help us to restrict the error to a small area.

Best regards,
Aland Li


Please mark the replies as answers if they help and unmark if they don't. This can be beneficial to other community members reading the thread.
Aland Li  Friday, August 14, 2009 7:32 AM

Hi,

We are changing the issue type to “General Discussion�because you have not followed up with the necessary information. If you have more time to look at the issue and provide more information, please feel free to change the issue type back to “Question�by opening the Options list at the top of the post window, and changing the type. If the issue is resolved, we will appreciate it if you can share the solution so that the answer can be found and used by other community members having similar questions.

Aland Li


Please mark the replies as answers if they help and unmark if they don't. This can be beneficial to other community members reading the thread.
Aland Li  Wednesday, August 19, 2009 12:12 PM

You can use google to search for other answers

Custom Search

More Threads

• Intermittent Clickonce fails with Unknown Publisher using valid Authenticode certificate signing
• Deployment Visual Studio 2005
• .NET 3.5 SP1 Prerequisite understood but not enforced (kind of).. why?
• Problem with delopying my application
• how can I best deliver the HUGE .NET 2.0 download to customers without causing them to quit!!??!?
• Why would msi need vcredist if merge modules are included in a setup project?
• ClickOnce in a CITRIX environment
• Does windows service application support click once feature of .net 2.0
• Modifying TargetDIR via Command Line Property
• support other languages