Pls Update Vazor to .NET9

[rrvenki]

Asp.NETCore Razor does not support VB. So OpenSilver resorted to .NET4.8 for the xxxx.Web project so VB could be supported. So the XAML part of the solution targets .NETSTANDARD 2.0. So i used Vazor targeting .NET 9 and created the xxxx.Web project. So i could upgrade the XAML project of the solution to target .net9.

On compilation i get error that there is no Asp.NET Runtime identifier for browser-wasm. This probably is because the Vazor is built for .NET 6. Upgrading it to .NET 9 requires related wasm.

Please upgrade Vazor to support .NET 9. I could help if required.

Thanks Venkatesh

[VBAndCs]

Hi Raja. This is a small open-source project, so you can download it and update it as you need. I have no time for this right now. Thanks.

---

From: Raja Venkatesh @.> Sent: Wednesday, May 7, 2025 4:45 PM To: VBAndCs/Vazor @.> Cc: Subscribed @.***> Subject: [VBAndCs/Vazor] Pls Update Vazor to .NET9 (Issue #25)

[https://avatars.githubusercontent.com/u/4756516?s=20&v=4]rrvenki created an issue (VBAndCs/Vazor#25)https://github.com/VBAndCs/Vazor/issues/25

Asp.NETCore does not support VB. So OpenSilver resorted to .NET4.8 for the xxxx.Web project so VB could be supported. So the XAML part of the solution targets .NETSTANDARD 2.0. So i used Vazor targeting .NET 9 and created the xxxx.Web project. So i could upgrade the XAML project of the solution to target .net9.

On compilation i get error that there is no Asp.NET Runtime identifier for browser-wasm. This probably is because the Vazor is built for .NET 6. Upgrading it to .NET 9 requires related wasm.

Please upgrade Vazor to support .NET 9. I could help if required.

Thanks Venkatesh

— Reply to this email directly, view it on GitHubhttps://github.com/VBAndCs/Vazor/issues/25, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALQ5MVU2CXPVQOMJU5Q5X4D25I2BZAVCNFSM6AAAAAB4UMDE46VHI2DSMVQWIX3LMV43ASLTON2WKOZTGA2DMNJXHEZDOMQ. You are receiving this because you are subscribed to this thread.

[https://s-install.avcdn.net/ipm/preview/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif]https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Virus-free.www.avast.comhttps://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail

[InteXX]

@rrvenki

My current Vazor project (under development) runs fine on .NET9; I tested it just now.

You may wish to try a sample .NET8 Vazor project that I published a while back, here:

https://github.com/CommunityVB/VazorTopShelf

Simply update the project's TFM to .NET9 and run.

[InteXX]

@rrvenki

Also: wasm is a Blazor construct, which is completely foreign to Vazor. Vazor addresses the problem of the ASP.NET's team's decision to exclude VB.NET support from Razor pages technology.

Vazor simply replaces a Razor page's HTML output with a VB.NET XML Literal hierarchy. I doesn't purport to do anything related to wasm.