Public version 2.12.2.0

This forum is meant for questions and discussions about the X# language and tools
Post Reply
Juraj
Posts: 161
Joined: Mon Jan 09, 2017 7:00 am

Public version 2.12.2.0

Post by Juraj »

In VS2022 I crete new project in Core dialect, WPF application.
Build:
:========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========

When pres Start debigging or Start Without debugging applicatiun can not run.
work path ...BinDebugg contains .exe, .pbd, .exe.config files. In this path exe start OK

Juraj
Attachments
TestStart03.jpg
TestStart03.jpg (72.24 KiB) Viewed 356 times
TestStart01.jpg
TestStart01.jpg (37.97 KiB) Viewed 356 times
TestStart02.jpg
TestStart02.jpg (28.67 KiB) Viewed 356 times
User avatar
robert
Posts: 4279
Joined: Fri Aug 21, 2015 10:57 am
Location: Netherlands

Public version 2.12.2.0

Post by robert »

Juraj,
I am not sure what happens here, but I see the same problem with the subscribers version.
Maybe it is something in the template?
What does work is starting the app from the explorer and then attaching the debugger to it (with Debgug-Attach to Process).
I'll look into this asap.

Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
Juraj
Posts: 161
Joined: Mon Jan 09, 2017 7:00 am

Public version 2.12.2.0

Post by Juraj »

When this app open in VS2019 work OK.
User avatar
robert
Posts: 4279
Joined: Fri Aug 21, 2015 10:57 am
Location: Netherlands

Public version 2.12.2.0

Post by robert »

Juraj,
it also works with VS 2022 version 17.0.
So apparently Ms has changed something between VS 17.0 and VS 17.2.
I tried the 17.2.3 download that was released on May 31, but that does not solve the problem.

We'll try to fix this in our code, but past experience has shown that this can sometimes be VERY tricky and it costs a lot of time to diagnose the problem.


Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
Juraj
Posts: 161
Joined: Mon Jan 09, 2017 7:00 am

Public version 2.12.2.0

Post by Juraj »

Hi Robert,
I don't know if it will help, but the bug is only in WPF, WinForms and VO MDI OR VO SDI can be run

Juraj
Post Reply