.NET WebForms Application DLL Problem

Jesse__Wolfe_(ApolloUser4_(Delete)_2153026)

Hi All..I am experiencing a very wierd (to me) error with my WebForms Application (Visual Studio .NET).I got a small application working, ensured it compiled, then began developing wiht a few LAPI calls (just a few basics). I added a reference to LAPI_NETp.dll. Strangely, it added LAPI_SSIp.dll to my projects /bin directory. OK, makes sense, NETp may rely on SSIp. But when I run the application, I get an error stating basically:Parser Error Message: File or assembly name LAPI_SSPIp, or one of its dependencies, was not found.When I delete the LAPI_SSIp.dll from the /bin directory and refresh my web page... the application works! Recompile it, however, and LAPI_SSIp get put back into /bin and the app is broken again.I'm guessing maybe LAPI_SSIp depends on some other libraries that aren't getting copied to the /bin directory?Does anyone know what the dependency might be?Jesse WolfeThe Apollo GroupJesse.Wolfe@apollogrp.edu

Find more posts tagged with

Comments

Jesse__Wolfe_(ApolloUser4_(Delete)_2153026)

I think I would still like an explanation from OT as to why the LAPI_SSIp.dll lib is imported to the /bin space automatically in a non-functional manner.However, the workaround I found was to remove the entry in the machine.config file that causes the run-time linker to load all the libraries found in /bin.Then, add entries in the web.config file for the project for any DLL's that are in /bin. This required a little modification of the default entry; just review the machine.config for details.Not so good for a developer with many projects and other contexts besides Livelink/LAPI development, but it works well for myself; I'm just doing LAPI and the loss of the * directive doesn't bother me.Jesse

Steve_Piatt_(spiatt_(Delete)_891610)

Because of reuse of unmanaged code (primarily for NTLM authentication--even if you are not using it) in the LAPI_BASE.dll by the LAPI .NET LAPI_SSPIp.dll assembly, it is necessary to include the LAPI directory in the system path. It will be insufficient to simply place all of the LAPI binaries in the ASP.NET web applications bin directory. The ASP.NET interpreter will not look there for unmanaged code. I had an open issue with Microsoft on this topic. It was closed since this was the design for ASP.NET with regards to all unmanaged code that is called from managed code.

Jesse__Wolfe_(ApolloUser4_(Delete)_2153026)

Thanks, Steve, for responding so quickly. I would have never figured that one out. :)Perhaps the SDK installer script could prompt the user to optionally add the SDK/bin path to the system path for them? Would have saved a lot of headaches. Regards,Jesse

Ann_Minton

The LAPI 9.1.0 SP3 Release Notes (12/17/02) state: "LAPI_NETp.dll is dependent upon LAPI_SSPIp.dll. LAPI_SSPIp.dll is dependent upon LAPI_BASE.dll and LLKERNEL.dll. In some LAPI .NET deployment scenarios, such as deploying a LAPI ASP.NET application, LAPI_BASE.dll and LLKERNEL.dll must be located by the system via the PATH environment variable."This statement is true for both .NET 1.0 and .NET 1.1. However, we have since discovered that for .NET 1.1, you must place the Microsoft file MSVCR70.DLL in the system path as well. We recommend placing the file in the \winnt\system32 directory. I have attached the required file to this message.For future releases of LAPI we will ask the user during installation if they would like the installer to put the LAPI bin directory into their system PATH. We will also redistribute MSVCR70.DLL and install it into the system32 directory (if needed), just as we do with the MSVCP60.DLL and MSVCRT.DLL files.

GlobalRegistry

Any one else run into this error?For ASP apps, I can delete the LAPI_SSPIp dll that get imported into the bin directory or set its property value Local Copy = False in visual studio....But for the console app, when I use a username/password over port 2099, everything works fine. But if I use NTLM Directory Services authentication over port 80 with the config parameter for LLSession, I keep getting the LAPI_SSPIp or one of it's dependencies errors when I try to use it with a LAPI_Documents object.I've got all the system paths set up but I think I may be missing something. I also have the msvcr70.dll in system32 and all the others mentioned.Anyone have/had this issue?

Krishnankutty_Nair

I am new to lapi webservices .I was trying out the lapi webservices sample.Here's my setup.I have a llserver running on my localhost,IIS5(also apache),WinXP I have MS VSS Microsoft Visual Studio .NET 2003 The first time I started following the documentation and doing what was told for IIS. I created the IIS virtual directory and tried the DocMan.asmx and I got a Document served you know (open,download).So I tried writing a simple web service thru VSS and got an error saying that I did not have asp.net vesrion1.1 on my machine.I downloaded that and voila my simple web service started working.Stll my livelink docman.asmx refused to load saying some assemblies(?) could not load and whatsoever.I have the errors as an attachment.The msvcr70.dll thing was already present in my computer.I also installed VJ# .NET for the 1.1 the other one would not install on mine for good measure.Many early poster here have indicated similar thingsabout LAPI_SSPIp.DLL and since the errors were more or less centered around them I deleted the LAPI_SSPIp.DLL and voila I am seeing light at the end of the tunnel..Now to see if really these things work...Wonderful this discussion board.Hopefully I may need that dll only if I am tunneling and I don't think I need it right now.