1. Aron Cox
  2. PowerBuilder
  3. Sunday, 3 March 2019 16:14 PM UTC

I am calling a .NET component given to me by our .NET Team from PowerBuilder 2017 R2. They tell me I need an .exe.config file for it to work. If I build my application into an executable, and add an .exe.config file, it does indeed work.

However, what do I do if I am running the application from the PowerBuilder IDE? I tried adding a PBVM170.exe.config but it didn't seem to work? Is that the right thing to do and I just need to try harder, or is there something I am missing?

Thank you for any help :)

 

Marco Meoni Accepted Answer Pending Moderation
  1. Sunday, 3 March 2019 21:01 PM UTC
  2. PowerBuilder
  3. # 1

Hi Aron,

I think what you want to achieve is so called side-by-side assembly.

In that case you need a .exe.manifest named as your compiled application, or PBVM170.exe.manifest if you are running from PB IDE. In that manifest you can describe the side-by-side .NET assembly that your app should bind to at run time.

Best,

.m

Comment
  1. Aron Cox
  2. Friday, 15 March 2019 10:36 AM UTC
Thanks Marco, that is something I have also wanted to do in the past, and is sorta related to my question, but it's not a manifest file I am looking at but a config file.
  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 4 March 2019 00:44 AM UTC
  2. PowerBuilder
  3. # 2

The IDE isn't called PBVM170.exe, it is PB170.exe.

Try naming it pb170.exe.config and put it in the same folder as pb170.exe.

Comment
  1. Aron Cox
  2. Friday, 15 March 2019 10:35 AM UTC
Sorry, yes my mistake when typing this message, duh. I have it as PBVM170.EXE.config but it seems like it still isn't working. I will do some more experimenting once everyone involved has stopped being sick with this super-cold that seems to have been going round the UK for ages!
  1. Helpful
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 4 March 2019 08:55 AM UTC
  2. PowerBuilder
  3. # 3

thanks Roland,
that's was obviously a copy/paste typo from initial message :-)

However, in one of my previous projects, I used .exe.manifest following MS specs for side-by-sed assembly (not .exe.config, maybe it is the same). Here it is with its bunch of loaded assembly, hope it helps.

When an exe file is started the side-by-side logic in Windows looks for a file named [programname].exe.manifest. The manifest should contain names for assembly/dll files that are side-by-side and should be found based on file location instead of looking in the registry. The default location for a assembly/dll file is the same directory as the exe-file.




































Best,

.m

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.