Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
Assemblies for .NET
Nagalakshmi_Ganesan_(nganesan_(Delete)_3029627)
We have reported a problem in using .NET assemblies with ASP Pages.Here is the problem addressed by our client.Any help/tips/suggestions are most welcome!.Thanks in advance!.Problem : Strong named assemblies for LAPI We need to build a .Net assembly & use this .Net assembly in our ASP pages.This .Net assembly utilizes LAPI functionality. For utilizing LAPI functionality in .Net, we need to make reference to LAPI_Netp.dll & LAPI_SSp.dll in our .Net project [as specified by OpenText]. For using our .Net assembly in ASP pages, the assembly has to be registered in GAC (Global assembly cache). For registering in GAC, the assembly to be registered & all the referenced assemblies need to be strongly named. When we build our .Net assembly as strong namedassembly, Visual Studio .Net is throwing the flg. error:"Unable to emit assembly: Referenced assembly LAPI_Netp.dll does not have a strong name". The problem here is that, in building a strong namedassembly all the referenced assemblies must be strongly named.But the assemblies provided by OpenText[LAPI_Netp.dll & LAPI_SSp.dll] are weakly named. Hence we require strong named assemblies for .Net,for building our .Net components. Attached zip file [LAPILibNet.zip] contains asolution, with a C# .Net class library project [that uses LAPI] [SimpleProject] & a C# WinForm application [SimpleProjectTest] for testing the class library. When we uncomment the following line inAssemblyInfo.cs of the class library project [SimpleProject], we're unable to build our library. "//[assembly: AssemblyKeyFile("..\\..\\..\\LapiLibNet.snk")]". Kindly provide the assemblies [LAPI_Netp.dll &LAPI_SSp.dll] as strong named assemblies, so that we're able to build our class library successfully.
Find more posts tagged with
Comments
Ann_Minton
In you post you state:"For using our .Net assembly in ASP pages, the assembly has to be registered in GAC (Global assembly cache)."I am unsure why your .NET assembly must be registered in the GAC. We have other customers using .NET assemblies in ASP pages and those assemblies are not in the GAC.Could you please explain why your assembly must be registered in the GAC?Regards.