WPF Designer

[TooTallTommyT]

I was hoping that the general forum would come up with some answers, but nothing so far, so...

I've upgrade to the latest versions and I still get (even a brand new project) an "Invalid Markup" on my designer window. If hover over either of the two controls in the xaml page, textblock or textbox, I get a hover message: "Textblock is not supported in a Windows Presentation Foundation (WPF) project."

Any idea when this might finally get fixed. It's hard to design a screen if I can't see what I'm doing.

Thanks

[JS-Support @Userware]

Hi,

I believe that in v2.0 Preview 0.4 the XAML Preview is working only in some specific case (that is, if version 1.x is installed AND you are using VS 2015 or 2017). We are working to fix the XAML Preview in version 2.x.

However, you should not be getting errors in the XAML Text Editor. Could you please post a screenshot showing the design-time errors?

Thanks

[TooTallTommyT]

This screen shot is just after creating a brand new project in VS2017, and compiling.

Xaml Editor Errors.PNG (192.1 KiB) Viewed 2401 times

[Username]

I'm having that error too when I just create a new empty project without touch in 1 line of code... I'm using VS2019

[JS-Support @Userware]

Thanks. We are looking into this. We'll keep you updated asap.

[Username]

News?

[JS-Support @Userware]

It's due to the fact that v2.0 Preview 0.5 does not come with the XAML Editor yet (this is listed in the "known issues" section of the release notes of v2.0 Preview 0.5).

As a temporary workaround, you can install the version 1.x of CSHTML5, which installs the appropriate XAML Editor into your Visual Studio (only on VS 2012, 2013, 2015, or 2017 - please note that VS 2019 is not yet supported with v1.x). It will fix the issue while waiting for the XAML Editor to be directly integrated into v2.0.

Thanks.

[TooTallTommyT]

Actually, I had this problem with versions 1.xx in VS2015 and VS2017 as well. This is one of the reasons why I never tried to do anything serious with this framework. I have a project I'm eager to try, and with the features that are coming out with ver 2.xxx, the framework should give me enough to do what I want, but I waited to see if this issue would be fixed...which it hasn't. I can do work arounds, but it's frustrating and quite interrupts the flow.

[JS-Support @Userware]

Thanks. We'll keep you updated asap.

[rthomas]

Hi,

As a workaround you can create a real XAML project and reference (Add exsting -> as Link) the CSHTML5 files in it.

Remi

[TooTallTommyT]

Have you actually done this, rthomas? I don't see how this works. I know how to add files by link, but I do not see how to "reference" those links once I have added them. Even if I could, how do then test it in the browser, since this isn't an actual CSHTML5 app? Do you have a sample project I could look at?

What say you JS-Support, is this a viable solution? Can you chime in and give me some insight?

[JS-Support @Userware]

Hi,

It is definitely possible to share .xaml files between CSHTML5 projects (of type "Migration Edition") and WPF projects, but it is not convenient because the namespaces need to be the same.

Support for the XAML preview in v2.x should be available before the end of August.

Thank you very much.