I don't get the RedemptionLoader work with Visual Basic .Net (Visual Studio 2019) at all.
I'm trying to avoid registering Redemption.dll (Redemption64.dll) on users machines. I tried to following instructions from https://www.dimastr.com/redemption/security.htm#redemptionloader to switch my application to the unregistered version with the RedemptionLoader. But I just can't get the version with the RedemptionLoader to work at all.
I'm using Visual Studio 2019, Visual Basic. I added RedemptionLoader.vb to the project. Among the references is reference to the Interop.Redemption.
In the project folder are
- Interop.Redemption.dll
- Redemption.dll
- Redemption64.dll The two Redemption DLLs have been deregistered.
In the program I try the following: Dim RDOSession As Redemption.session RDOSession = RedemptionLoader.new_RDOSession()
But already: Dim RDOSession As Redemption.session -> it does not work (Redemption is underlined).
This would be possible: Dim RDOSession As Redemption.RedemptionLoader -> but it is of no use for me.
I'm desperate and very thankful when I get the basics up and running.
Regards
Albert
CodePudding user response:
You need to add the included interop dll to your project references in VS.
CodePudding user response:
You must keep the interop library referenced in the project to be able to use the type definitions in your code base. The redemption loader is not related to the interop library, just make sure that unmanaged assemblies are put to the output folder, so the loader could locate them. That is all.
Sometimes it makes sense to create a brand new project and try to implement a new feature there to make sure everything works correctly. So, I'd recommend doing that to exclude any external factors from the view. I've implemented that scenario many times in VB.NET projects without a problem.