Share
Report
1,112Dear All,
The DLL Registration related issue is still not resolved. BTW I have come across a new issue related to the same problem.
The actual scenario is:.
I'm able to access two different Database through RTC Client and as well as through Developer Client from a single Client Computer.
The databases are 1. MGR & 2. OPT.
A custom dll is registered into the Client computer & I've declared the dll as an automation in Page (ID 43) in the MGR Database. The automation is working fine without any issue.
Now I've export the Page 43 from the MGR database & import the same into the OPT database. The Page 43 could not find the class name in the OPT Database, hence a compilation error is occurred.
Then using the Developer Environment Client I've declared the automation variable with the proper class name (manually) in the OPT database & now it's working good.
Why does one database can able to locate the class while other cannot "from the same computer" ?
Is there any issue related to my Registration Process ?
The Other Client PCs are still not able to locate the Automation Class name & it's not a compulsory that every Client PC should have Developer Environment installed.
Registration Process:
1. Accessing the Command Prompt through Administrative rights.
2. DLL is created in .NET framework version 3.5 & RegAsm.EXE is used to register the dll from the .Net framework v2.0.50727 folder
3. DLL is dropped into system32 folder
4. /codebase option is used during registration
5. Gacutil.EXE is not used
What are reasons ?
Kindly reply.
*This post is locked for comments
All responses (
Answers (
