xsharp.eu • Public 2.5b
Page 1 of 1

Public 2.5b

Posted: Tue Sep 01, 2020 6:52 pm
by Juraj
Hi All


today I wanted to test the public version 2.5b xSharp. I installed it in the VS2019 community. After trying to create a new WPF application I got this error (attachment). The same is true in VS 2017.

Juraj

Public 2.5b

Posted: Tue Sep 01, 2020 8:08 pm
by Chris
Hi Juraj,

Just to make sure if it is a X# or general problem, please try creating a c# WPF project, does this one work ok?

Public 2.5b

Posted: Wed Sep 02, 2020 6:01 am
by Juraj
Hi Chris,

in c# work xaml designer OK. After reinstall old version X# (2RC1Fox) work xaml designer ok.

Juraj

Public 2.5b

Posted: Wed Sep 02, 2020 7:18 am
by robert
Juraj,
What happens if you right click on the filename, choose "Open With" and then "XAML Designer".
Can you open the window that way ?

Robert

Public 2.5b

Posted: Wed Sep 02, 2020 7:39 am
by Chris
Robert,

I can confirm the problem, in both VS2017 and VS2019, with the 2.5 public build. And indeed, with Open With, the WPF form does open correctly!

Public 2.5b

Posted: Wed Sep 02, 2020 9:38 pm
by ic2
Hello Juraj, Robert, Chris,

I posted this August 10 and a while later I also solved it with Open with

https://www.xsharp.eu/forum/public-prod ... xaml#15519

I think it's a VS issue. I remember I've seen it before, I think with C#. Almost everything which can go wrong with VS will go wrong at some point in time.

Dick

Public 2.5b

Posted: Thu Sep 03, 2020 2:00 pm
by robert
Dick,

this is NOT a VS issue but something in our code.

Robert

Public 2.5b

Posted: Thu Sep 03, 2020 2:46 pm
by ic2
Hello Robert,
robert wrote:Dick,
this is NOT a VS issue but something in our code.
Could be but I am sure I've had this issue before and I usually ask or report it in this forum (or in the NG X#, before Vulcan). I could only find a Vulcan bug (logged it as bug #1070) where the VS editor crashed when on trying to edit WPF (2011) and no postings from me concerning that message.

So I am almost certain I saw it in C#. If you search on this message there a pages full about this error.

If you can prevent it in X#: that's great of course. But it may be not entirely an X# issue I'd say.

Dick