• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • C# .NET error msg in a XAML window will crash if window opened from PB

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

Resolved C# .NET error msg in a XAML window will crash if window opened from PB

  1. Advice
0
Votes
Undo
  1. Scott Gorke
    Scott Gorke
  2. PowerBuilder
  3. Wednesday, 5 May 2021 20:25 PM UTC

Second question re: same project!

Hi,

We're using PB 2019 R2 build 2353, with an app running in Windows 10 1909.

As expressed in a previous question, we have a PB app that makes a call to open a window built in C# .NET XAML. During data entry in the XAML window, it might try to pop a C# .NET error message if an entry is incorrect.

If the XAML window is run exclusively in a C# .NET app, the error message displays correctly..

If the XAML window is opened by a call from the PB app, the PB app crashes trying to pop the error message.

Any ideas on how to fix this? Can this be resolved by a fix in PB code, or is the solution strictly a C# one?

Powerbuilder .NET importer - complex data types
PB 2019 app opens a C# .NET XAML window, but it's ...
Accepted Answer
Scott Gorke
Scott Gorke Accepted Answer Pending Moderation
  1. Thursday, 23 September 2021 16:31 PM UTC
  2. PowerBuilder
  3. # Permalink

This has been fixed on the C# .NET side. Closing....

Comment
There are no comments made yet.
Responses (3)
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 5 May 2021 23:32 PM UTC
  2. PowerBuilder
  3. # 1

Maybe a solution could be for the .Net to return an error message to PB and show it in PB instead of WPF .net ?

Sorry if that's not possible.

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 5 May 2021 22:06 PM UTC
  2. PowerBuilder
  3. # 2

Same answer as the previous question.

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Thursday, 6 May 2021 00:01 AM UTC
Armeen, the DLL importer tool for non visual .net dlls is a great feature.

Another HUGE feature would be to be able to import VISUAL .Net stuff.

(just saying...)

:)
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 6 May 2021 01:48 AM UTC
Yes, that would be a great feature. Unfortunately, it's much more involved than .NET DLL Importer.
  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.