You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+23-23Lines changed: 23 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
A collection of Blazor components that emulate the web forms components of the same name
4
4
5
-
[](https://dev.azure.com/FritzAndFriends/BlazorWebFormsComponents/_build/latest?definitionId=14)[](https://gitter.im/BlazorWebFormsComponents/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
5
+
[](https://dev.azure.com/FritzAndFriends/BlazorWebFormsComponents/_build/latest?definitionId=14)[](https://gitter.im/BlazorWebFormsComponents/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
@@ -12,7 +12,7 @@ We believe that Web Forms applications that have been well maintained and provid
12
12
13
13
This is not for everyone, not everyone needs to migrate their application. They can continue being supported as Web Forms for a very long time (2029 EOL at the time of this writing) and the applications that are considered for migration to Blazor may be better suited with a complete re-write. For those applications that need to be migrated, this library should help make that process simpler by providing components with the same names, markup, and functionality as previously available.
14
14
15
-
[Get started with your migration, steps ahead, and strategy documentation](docs/Migration/readme.md) for various controls and tools used are available. Live versions of these components are availalbe on the [Live Samples website](https://blazorwebformscomponents.azurewebsites.net)
15
+
[Documentation is available online](https://fritzandfriends.github.io/BlazorWebFormsComponents/). [Get started with your migration, steps ahead, and strategy documentation](docs/Migration/readme.md) for various controls and tools used are available. Live versions of these components are availalbe on the [Live Samples website](https://blazorwebformscomponents.azurewebsites.net)
16
16
17
17
Portions of the [original .NET Framework](https://github.com/microsoft/referencesource) are contributed to this project under their MIT license.
18
18
@@ -21,35 +21,35 @@ Portions of the [original .NET Framework](https://github.com/microsoft/reference
21
21
There are a significant number of controls in ASP.NET Web Forms, and we will focus on creating components in the following order:
@@ -64,8 +64,8 @@ We will NOT be converting any DataSource objects, Wizard components, skins or th
64
64
65
65
There are a handful of features that augment the ASP<span></span>.NET development experience that are made available as part of this project in order to support migration efforts. Importantly, these features are NOT implemented the same way that they are in Web Forms, but rather have the same API and behave in a proper Blazor fashion. These features include:
0 commit comments