• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Jenkins Build - Illegal data type: dotnetobject Errors encountered during import/compile

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

Resolved Jenkins Build - Illegal data type: dotnetobject Errors encountered during import/compile

  1. Issue
0
Votes
Undo
  1. Jeff Nesler
    Jeff Nesler
  2. PowerBuilder
  3. Friday, 16 July 2021 04:06 AM UTC

Using Powerbuilder 2019 R2 and looking for some help with building an application that uses imported .Net Dll's.  We have installed the standalone compiler on a Jenkins server and have been successfully building applications there for the past few months.  I added some code that uses an imported .Net DLL and now one of the builds is failing with the following error:

Illegal data type: dotnetobject Errors encountered during import/compile

It builds fine on my local machine, so I'm assuming we need to push some other runtime files out to our Jenkins server, but I'm not sure what all needs to be deployed.  Is there a .pbd I could reference in my library list for the application that would contain the dotnetobject, or do I have to push additional runtime dll's out or possibly reinstall the standalone compiler?

Thanks for any advice,

Jeff N.

  1. .NET Assembly
  2. PowerBuilder Compiler
menuitem.create custom code is deleted
64 bit Number Support in the DataWindow
Responses (2)
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Friday, 16 July 2021 04:29 AM UTC
  2. PowerBuilder
  3. # 1

Hi, Jeff - 

Look at the PB Help topic "runtime files" in PB 2019 R2. The second table ("Additional runtime file") contains the information you are looking for, I believe. See the entry where the "Required For" column says ".NET class support".

Here's a URL to the same information online:

https://docs.appeon.com/pb2019r2/application_techniques/ch36s04.html

Regards,
John

Comment
Jeff Nesler
  1. Jeff Nesler
  2. Friday, 16 July 2021 15:48 PM UTC
Thanks John, I looked at the runtime help but I must have missed that section. it looks like these three files are the ones you're talking about:



PBDotNet190.dll, PBDotNetFrameworkInvoker190.dll, PBDotNetCoreInvoker190.dll



I'll try to deploy those additional files to our Jenkins server and see if that does the trick.
  1. Helpful
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Friday, 16 July 2021 09:27 AM UTC
  2. PowerBuilder
  3. # 2

Hi Jeff,

I didn’t reproduce the issue you described locally. Did you run into this when using pbc190.exe?
I suggest you upgrade to PB 2019 R3 Build 2703 and see if the issue is still there.
And if any problem, please open a ticket in the Support System (https://www.appeon.com/standardsupport/newbug) and provide a reproducible small case there, then Appeon will have Support staff assigned to follow up and handle the issue.

Regards,
Ken

Comment
Jeff Nesler
  1. Jeff Nesler
  2. Friday, 16 July 2021 15:53 PM UTC
Thanks for checking Ken. It works fine for me on my local machine as well, just not on our Jenkins build server where we installed the standalone compiler. That's why I thought we had left something out of our deployment to the Jenkins server. I'm going to try John's advice below and push out those additional runtimes to our Jenkins server.
  1. Helpful
Ken Guo @Appeon
  1. Ken Guo @Appeon
  2. Monday, 19 July 2021 09:08 AM UTC
Hi Jeff,



Thanks for your feedback! I suggest you can also try upgrading to PB 2019 R3, because in 2019 R3, PowerBuilder Runtime is separated from PowerBuilder IDE so you can install PowerBuilder Runtime separately on the Jenkins Server.



Regards,

Ken

  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 19 July 2021 16:55 PM UTC
https://docs.appeon.com/pb2019r3/whats_new/Separating_Runtime_from_IDE.html
  1. Helpful
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.