-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can you please make .NET BLAZOR integrating with c++ webassembly easier? #49959
Comments
Thanks for contacting us. This would be a feature for the runtime team to consider. Moving it there for them to evaluate the ask. |
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
This is largely covered by #44636 |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis issue has been moved from a ticket on Developer Community. let me easily start writing logic in c++, you can figure out the rest of the stuff. suggestion : use existing tool chains like llvm/emscripten to compile it to webassembly modules and start using it with intelisense from c# codes in visual studio. Original CommentsFeedback Bot on 3/11/2021, 00:45 AM:Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We'll provide an update once the issue has been triaged by the product team.
|
To elaborate, we can consider bringing the C/C++ environment closer to .NET Specifically the ability for consuming C/C++ code in blazor project easily by targeting C/C++ projects to blazor The C/C++ projects targeting blazor, through careful engineering, can ideally be consumed in blazor directly with intellisense.
let C/C++ be capable of dynamically running webassembly (string format / binary), let .NET be capable of too. Use the browser's webassembly to achieve it It's a feature that's important as blazor's oppertunity for becoming the all-interfacing all-purpose app engine for writing all-platform business applications I understand we can compile C/C++ to dll and use dll in .NET, but I am hoping to bring webassembly in the game, let C/C++ compile directly to webassembly, and .NET will help developers use C/C++ functions as if there is no barrier, then later on the two will see each other in webassembly and .NET use the native-compiled wasm modules to run the native code Eventually we can use webassembly even when there is no browser by bundling its runtime, for example we can replace MAUI with Blazor for our next generation application framework. Developers would be using blazor + native codes to build an unified UI experience, and if they require platform specific, they can use native codes to access them if the app is targeting those platform (multi-targeting is possible, we can do it a lot of ways, for people to use native features on IOS/Android/etc) If there is a path for Microsoft .NET to be the framework for building all UI-heavy applications, [Browser-UI] + [Any Programming Language] glued together by [.NET] utilizing [Webassembly] seems to be the one Stage is presented, Microsoft's name will be remembered. Imagine a tomorrow you wanted to display a dialog box for login, Kotlin community already built a library for drawing such a dialog box, you decide where to put it in blazor, meanwhile hashing the password using a library from ALGOL 60, in VisualStudio, where meets productivity |
Let native development integrate with blazor to build the application of our diverse community. |
This issue has been moved from a ticket on Developer Community.
let me easily start writing logic in c++, you can figure out the rest of the stuff. suggestion : use existing tool chains like llvm/emscripten to compile it to webassembly modules and start using it with intelisense from c# codes in visual studio.
Original Comments
Feedback Bot on 3/11/2021, 00:45 AM:
Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We'll provide an update once the issue has been triaged by the product team.
The text was updated successfully, but these errors were encountered: