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

Resolved Debug with Visual Studio and PowerBuilder for C# components

  1. Issue
1
Votes
Undo
  1. Stèphan Eizinga
    Stèphan Eizinga
  2. PowerBuilder
  3. Tuesday, 10 March 2020 11:20 AM UTC

When we want debug our ActiveX components written in C# (Visual Studio) and PowerBuilder the application starts and stops.

We have enabled 'Enable native code debugging' and 'Use Managed Compatibility Mode'.

When we use PowerBuilder 12 is starts PowerBuilder and we can debug in Visual Studio for our components.

What is changed in PowerBuilder 2019 and how can we fix this?

  1. .NET Std Framework
  2. C#
  3. Debugging
  4. Visual Studio
Fixed DATA in a DW how to Describe and Modify ?
Excel VBA from PB script
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 10 March 2020 16:19 PM UTC
  2. PowerBuilder
  3. # 1

Attach Process example ...

Comment
There are no comments made yet.
Stèphan Eizinga
Stèphan Eizinga Accepted Answer Pending Moderation
  1. Tuesday, 10 March 2020 15:32 PM UTC
  2. PowerBuilder
  3. # 2

Hello Chris,

When i use an bat file, i get the follow error message:

 

How can i find ticket #3635? is it public?

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 10 March 2020 16:19 PM UTC
Hi Stèphan - try using the "Attach Process" feature of VS. I'll post a screen shot in a minute for you to look at.

https://docs.microsoft.com/en-us/visualstudio/debugger/attach-to-running-processes-with-the-visual-studio-debugger?view=vs-2019

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 10 March 2020 15:20 PM UTC
  2. PowerBuilder
  3. # 3

Hi Stèphan;

  This looks like a issue similar to what has been reported in Ticket #3635. The ability to debug PB from the VS IDE is no longer working and this issue has now been transferred to Engineering for further analysis.

   In Ticket #3635 though, a workaround suggestion was to use a BAT file to start the IDE (PB190.exe) instead of mapping directly to the IDE's EXE. That seems to work for the Appeon Testers. Hopefully, that might be an OK workaround for you as well for the time being.

Regards ... Chris

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.