• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • DotNetAssembly.LoadWithDotNetFramework - load dll from GAC

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved DotNetAssembly.LoadWithDotNetFramework - load dll from GAC

  1. How-to
0
Votes
Undo
  1. Jeff Martin
    Jeff Martin
  2. PowerBuilder
  3. Thursday, 9 April 2020 14:32 PM UTC

It appears assemblies are loaded by specifying the path to the dll. Is there anyway to load an assembly located in the GAC (Global Assembly Cache) without specifying the path? The path to our GAC files changes slightly with every build when the version increments (ie: folder "v4.0_4.98.20.77__5a2301cbe58bb678" vs folder "v4.0_4.99.20.90__5a2301cbe58bb678").

 

 

PDF Printer recommended for Appeon Powerbuilder 20...
Runtime for PBR3
Responses (2)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 9 April 2020 14:43 PM UTC
  2. PowerBuilder
  3. # 1

Have you tried this new .NET interop feature of PowerBuilder 2019 R2?https://docs.appeon.com/appeon_online_help/pb2019r2/whats_new/ch01s03.html

It might solve your problem.

Comment
Load more comments
Jeff Martin
  1. Jeff Martin
  2. Thursday, 4 March 2021 16:09 PM UTC
Looking for any follow up to referencing DLLs in the GAC via the .NET interop feature introduced in PB 2019.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 4 March 2021 16:13 PM UTC
Hi Jeff, Mark had explained you can do this but you just need to use relative path. That didn't work for you?
  1. Helpful
Jeff Martin
  1. Jeff Martin
  2. Friday, 5 March 2021 13:28 PM UTC
We have it working, but it is a hacky approach for sure.
  1. Helpful
There are no comments made yet.
Mark Lee @Appeon
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Friday, 10 April 2020 09:28 AM UTC
  2. PowerBuilder
  3. # 2

Hi Jeff,

I suggest you use a relative path in the .NET DLL Importer module. 

Your need to copy the DLL needed to be imported to the relative path (the same as the App exe folder) first.

And then you can modify the source .NET DLL path after importing the dll.

So in this case, you can ignore the absolute path issue.

However, I will record it as a new enhancement / requirement request and will transfer it to our product team for consideration.

Regards,

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.