Forums - CSHTML5

Black-Byte wrote:could you please post the Changlog from this to 2.0.0-alpha45-063 ?

Sure. We are going to release Preview 0.6 very soon with the full changelog.

Thanks.

Is there any way you can share the change or help me implement your fix myself, so I can make my own release before you release 1.2.4? Sorry for the delay. Sure. Here is how to patch: Please open the file "JSIL.Browser.js" and replace the following line: if (typeof (localStorage) !== &quo...

Hi, Instead of clicking "Browse..." to select the projects to migrate, please try doing the following: 1. Open your original Silverlight solution (with Visual Studio 2012, 2013 or 2015) 2. Launch the Silverlight Migration Wizard from there. You should see the projects in the list without h...

Hi,

We have fixed the RadioButton issue. Please expect the fix to be available in the very next build.

Thanks
Regards

Very interesting indeed. Thanks a lot for the link.

Hi,

This issue has been fixed in CSHTML5 version 2.0.0-alpha43-061, which is now available on NuGet.

The version 1.2.4 will be released asap, but we still have a few regressions to fix, because we are attempting to maintain both v1.x and 2.x with the same codebase.

Thanks.
Regards

Hi,

The fix is now available on NuGet (please update your CSHTML5 NuGet reference to version "2.0.0-alpha43-061")

Thanks.
Regards

fangeles wrote:I have upgraded the bridge version to latest nuget package 2.0.0-alpha43-061, and the wcf web service problem is fixed.

Thanks a lot for the update. I'm glad that the issue was fixed.

Thanks for sending the project to replicate the issue related to the radio buttons. It is on our backlog and one of our developers will work on it asap. I will keep you updated. Thanks a lot.

Hi,

We have just fixed the issue where some applications files were very big (especially the ".meta" files) when compiling with v2.0 Preview 0.5. Please expect the fix to be available in the coming days.

Thanks.

Hi,

We have fixes this issue. Please expect the fix to be included in the very next NuGet update.

Thanks.

Hi,

This issue is supposed to be solved in the latest NuGet package version 2.0.0-alpha42-057. Please feel free to keep is updated if you still encounter any issues.

Thanks

Hi, As we are attempting to maintain both the v1.x and v2.x branches in parallel (so that they have the same features with a different underlying technology), we have some delay to update v1.x because the recent changes in the v2.x branch have broken our internal builds of v1.x. We are working to fi...

Hi,

We have fixed the try/catch handling when using the async methods of the WebClient.

Please expect the fix to be available in the next NuGet package update.

Thanks
Regards

Thanks. Could you please try setting the columns in the constructor if the page rather than the Loaded event ? Also, can you please try the small showcase app that you get under Visual Stidio when you click File -> New Project -> CSHTML5 Showcase It contains a sample DataGrid with custom columns. Re...

Thanks.
Oh I see. That's a known bug in the current version 2.x Preview where the "meta" files are huge due to the fact that resources get copied into them. We are going to fix this issue asap.
Thanks. Regards.

Thanks for your message. We are going to look into the Open Dialog extension asap. As far as the size of generated JS files is concerned, could you please post a screenshot of your "bin/Debug/Output" directory showing the file sizes? Did you try with the "index.min.html" which on...

Thanks. We have reproduced this issue and we are looking into it. Please expect a fix in a few days.

Regards

The best way to contribute would be first to transition to v2.0 and then directly improve the CSHTML5 source code by cloning it from GitHub and following the instructions at: https://github.com/cshtml5/CSHTML5 You said that you were not able to get your project bug-free in 2.0 due to many issues wit...

Hi,

Thanks for your message.

The code for Guid parsing is totally different in CSHTML5 v2.x and should work properly.

We are adding what you reported to our backlog and see if we fix it in v1.x or if we skip it because it works in v2.x and you have a workaround for v1.x.