Posts: 1
Joined: Fri Sep 21, 2018 5:47 am


Postby dlebansais » Fri Nov 02, 2018 11:52 am

Dear CSHTML5 dev team.

I've been working with your product (free trial) for some time and I'm quite happy with it. The ability to write web app using the same logic as Windows app is very nice. I have two sites written with a mix of HTML and PHP, and I did my best to port them to CSHTML5 . Here is my feedback.

1. Compilation time is pretty slow, but that's not really a problem. It's just quite noticeable when compared to PHP scripts for which all you need to do is to upload them.

2. My sites aren't particularly big, yet each easily take over 20 Mb of scripts, and they take some time to download. Also, I believe browsers put limits on the amount of script data they will run from a site and it's pretty stringent (100 Mb?). I feel like I could hit this barrier in the future. But I haven't really tested, it's just a feeling.

3. The doc from this site is scattered, and not very reliable. For example, it will state that CultureInfo.InvariantCulture is supported, and indeed you can use it, for example with CultureInfo.InvariantCulture.EnglishName, but when comes the time to compile you'll get the "not yet supported" error. I'm not too sure why the error is delayed, instead of just not including the feature in the class, but now when I try something new I always assume it's in fact not implemented, and I try to compile a small test sample. It takes time, it's annoying. It's my feedback.

4. Trying the various Inlines such as <Bold>, <LineBreak>, <Hyperlink> I have several issues with them:
4.1. For the life of me, I couldn't manage to bind them to data. I can bind a TextBlock with, for example, <TextBlock Text="{Binding MyText}"/> but I can't do the same with Hyperlink and that's a big limitation for me. Perhaps I'm overlooking something.
4.2. There is always a space after the Hyperlink tag. If you take your example 4, "here is a link." actually looks like this: "here is a link .". That's ... weird.
4.3. I haven't been able to put a style on the Hyperlink foreground, so it always has blue text. I wasn't able to use VisualStateManager either, so can't give my links a custom look.

5. I have several pages, and it's quite slow to switch from one page to the other. Perhaps I'm not using the correct way to do it? Each page inherit from Windows.UI.Xaml.Controls.Page, and I switch with "Window.Current.Content = NewPage;"

6. I've noticed that Google Chrome (for example) saves my site in a cache after the first download. That's fine, until I make a change. In that case, the change will be visible only after the cache is explicitly cleared. It's problematic! I hope there is a way to work around this, I haven't really looked yet.

This was with 1.2 beta 6. I see beta 7 is out now, keep the good work.

JS-Support @Userware
Site Admin
Posts: 1142
Joined: Tue Apr 08, 2014 3:42 pm

Re: Feedback

Postby JS-Support @Userware » Wed Nov 07, 2018 4:50 am


Thank you very much for your feedback!

This is very useful.

Here are some comments on each of the points.

1. Compilation time will improve as we release a WebAssembly-based version, likely in 2019.

2. This will improve with the Bridge-based version that is expected in the coming months, which produces less verbose JavaScript and also allows to "minify" it. Furthermore, we plan to split the main script "CSharpXamlForHtml5.js" into several pieces so that only the features that are actually used by your application are downloaded.

3. Thanks. We just removed "InvariantCulture" from the list of supported methods in the documentation. Please let me know if you find other specific items that we should update. As for the fact that the compiler shows more errors than the design-time, this should be fixed with the Bridge-based version that is expected in the coming months: the design-time intellisense/autocomplete will only show the supported classes and methods.

4.1. The <Hyperlink> tag currently does not allow to bind data indeed. As a workaround, please use the "HyperlinkButton" control.

4.2 Thanks. That's strange indeed, we will investigate. In the meantime, please use a negative margin or the "HyperlinkButton" control.

4.3 The inability to set a style for the hyperlink foreground is indeed a bug. As for the VisualStateManager, this is not possible because <Hyperlink> does not inherit from Control. However, you can use the "HyperlinkButton" control instead. We have just published the default style and ControlTemplate for the HyperlinkButton control, so that you can customize it. You can find it at:

5. You are doing it right. Performance is one of our current main areas of focus and we have been working on it for some time. Please expect performance improvements in the coming months.

6. This will be fixed with the Bridge-based version, expected in the coming months. In the meantime, please append "?YYYYMMDD" to the URL of index.html in order to force a refresh. For example, the link to our Showcase application is in the following format, precisely to ensure that if we update it, we also update the text that we append:

keep the good work.

Thank you very much!

Return to “General Discussion and Other”

Who is online

Users browsing this forum: No registered users and 1 guest