All geek questions in one place

Calling a .Net COM assembly from a Powerbuilder application (without registering)

We have a Powerbuilder 10 application that uses .Net COM builds. We are trying to embed the manifest in the PB application (to call COM assemblies without registering). Sections for dependencies on .Net COM nodes have been added to the combined manifest file. We are trying to use different tools to enter a new manifest with different results - using GenMan32 for injection truncates the application from 6 MB to 45 KB. - Using ResourceTuner, the file size looks fine, but trying to run the application gives "Fatal Disk Error".

Any suggestions on invoking .Net ComEnabled assembly from PB without registering?

+3
source share
2 answers

This is more a redirect than an answer. One thing you need to know about is that PowerBuilder creates executable files that do not meet the standards for Windows executables. In essence, they are a bootstrap procedure for loading a PowerBuilder virtual machine, as well as a set of class definitions (objects). The cases that you raised are not the first ones that I heard about when utilities designed to modify executable files do not work with PowerBuilder executables.

, , , . , COM-, ConnectToNewObject() , , , .

,

.

+1

Source: https://habr.com/ru/post/1738714/

More articles:


All Articles