referencesource
BlazorWebFormsComponents
Our great sponsors
referencesource | BlazorWebFormsComponents | |
---|---|---|
88 | 4 | |
3,087 | 428 | |
0.6% | 1.9% | |
0.0 | 0.0 | |
about 2 months ago | 8 months ago | |
C# | HTML | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
referencesource
-
Why your F# evangelism isn't working
Just like every language is able to be slow/non-performant -- but OO in this case would be Python in a web context; it doesn't invalidate that a good amount of OO codebases in the wild devolve into incomprehensible black boxes, where no one has any idea what anything does or how to make meaningful changes that fulfill the intent of (compare that to iterative programming, where you can atleast read it)
A list: I give you a vector. Plain and simple. Not this insanity: https://referencesource.microsoft.com/#mscorlib/system/colle... You do not need OO to create a vector (or even an array -- god forbid!)
As for trees: roll your own. They're simple enough, yet tightly-coupled with context that no generic implementation exists that is flexible enough. You do not need OO to create a tree. C has been working with trees long before the current Frankensteination of OO was even a twinkle in Gosling's eye.[0]
Data structures do not need inheritance -- they might need delegation (message passing that requires you to actually think about your system).
Data structures do not need encapsulation -- they most likely need namespaces. Realistically, most classes will be used as namespaces.
Data structures do not need polymorphism -- just implement the methods you need, and name them appropriately (no 5+ word phrases, please. Please!)
What modern OO does is lower the barrier to productivity in the present, and then pays for it in the future. It's no different than writing your "planet scale" backend system in JS.
[0] If you want to know why we have Java: some guys that didn't have the time to think about low-level (memory management specifically) things for their embedded applications, got sick of trying to learn C++, decided to make their own language. That's it. There was no grand plan or thoughtful design -- it's just a mismash of personal preference.
List is an IList/IReadOnlyList; these interfaces do nothing that couldn't be done right inside the file itself.
https://referencesource.microsoft.com/#mscorlib/system/colle...
https://referencesource.microsoft.com/#mscorlib/system/colle...
Instead we have to go diving through the IList, which implements ICollection, which implements IEnumerable, which implements IEnumerable (again). Just because each interface is composed of another interface, doesn't mean you aren't using inheritance. You are effectively creating a custom inheritance tree through willy-nilly composition.
It is gratuitous to make this chain so deep, when the underlying code is just a handful of lines.
https://referencesource.microsoft.com/#mscorlib/system/colle...
https://referencesource.microsoft.com/#mscorlib/system/colle...
https://referencesource.microsoft.com/#mscorlib/system/colle...
----------------------------------------------------------------------------------------------------------------
The doc-strings are unnecessary. It's self-evident what most of the code does if you read it.
// Returns an enumerator for this list with the given
-
Multi-Key Dictionary in C#
.net itself has arbitrary interfaces, ex https://github.com/microsoft/referencesource/blob/master/mscorlib/system/action.cs
-
Bring WCF apps to the latest .NET with CoreWCF and Upgrade Assistant
Not enough people care. And you can compile the APIs yourself from the .NET Framework reference source if you really want it. System.Messaging was added to the .NET Framework reference source in this PR.
- Ask HN: Examples of Top C# Code?
-
What do you think is more readable when using LINQ: Query Expressions or Method Expressions?
Now go review the code at https://github.com/microsoft/referencesource/blob/master/System.Xml.Linq/System/Xml/Linq and find where those parts are in LINQ to XML.
-
How to Validate an Email Address in C#
Let’s look at another example. The following is a regex used by Microsoft in their EmailAddressAttribute class:
-
We doing this?
If I trained an AI to make a Java VM by getting it to learn from Microsoft's Reference Source licensed .NET framework. Would I be allowed to make a profit or distribute my Java VM?
-
Why do Task.Wait and Task.Result even exist?
And the actual implementation: https://github.com/microsoft/referencesource/blob/master/mscorlib/system/threading/Tasks/ThreadPoolTaskScheduler.cs
BlazorWebFormsComponents
- Migrating from webforms ti Blazor step by step
-
The .NET Team's Favorite Razor Features
I like Razor Component Libraries. Just write a .razor file and it's a component that can be referenced. I used these a lot in my BlazorWebFormsComponents project, which helps with migrating ASP.NET Web Forms project to Blazor.
-
C# 9 top-level programs and target-typed expressions
You can give it a shot with this project. https://github.com/FritzAndFriends/BlazorWebFormsComponents
It emulates WebForms component with Blazor. Although I would just start from scratch.
-
Why did microsoft dropped support for webforms but still supports windows forms?
And to add to that it's not like they haven't had any upgrade path either. They even have docs on Migrating Webforms to Blazor and even created an ebook for it along with webforms components wrappers. To make your migration experience not as bad as it would have been.
What are some alternatives?
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
export-data-to-excel-in-blazor - This repository contains examples of exporting data from a data table to Excel in Blazor applications using Syncfusion Excel (XlsIO) library.
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
github1s - One second to read GitHub code with VS Code.
CoreCLR - CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.
CoreWCF - Main repository for the Core WCF project
csharplang - The official repo for the design of the C# programming language
ILSpy - .NET Decompiler with support for PDB generation, ReadyToRun, Metadata (&more) - cross-platform!
Moq - Repo for managing Moq 4.x [Moved to: https://github.com/moq/moq]
dotnet - .NET Community Toolkit is a collection of helpers and APIs that work for all .NET developers and are agnostic of any specific UI platform. The toolkit is maintained and published by Microsoft, and part of the .NET Foundation.
MSBuild - The Microsoft Build Engine (MSBuild) is the build platform for .NET and Visual Studio.
dnSpy