Started writing the migration steps and notes

Author: csharpfritz

README.md

@@ -1,9 +1,19 @@
 # BlazorWebFormsComponents
+
 A collection of Blazor components that emulate the web forms components of the same name
 
 [![Build status](https://dev.azure.com/FritzAndFriends/BlazorWebFormsComponents/_apis/build/status/BlazorWebFormsComponents-.NET%20Standard-CI)](https://dev.azure.com/FritzAndFriends/BlazorWebFormsComponents/_build/latest?definitionId=14)
 
-## Controls proposed to be migrated
+## Approach + Considerations
+
+We believe that Web Forms applications that have been well maintained and provide value should have a path forward to the new user-interface frameworks with minimal changes.  This is not an application converted nor is it a patch that can be applied to your project that magically makes it work with ASP<span></span>.NET Core.  This repository contains a library and series of strategies that will allow you to re-use much of your markup, much of your business code and help shorten your application re-write process.
+
+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 (2030 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.
+
+[Strategies for your migration and steps ahead](docs/Migration/README.md) are available as part of this repository.
+
+## Blazor Components for Controls
+
 There are a significant number of controls in ASP.NET Web Forms, and we will focus on creating components in the following order:
 
   - Data Controls

docs/Migration/README.md

@@ -0,0 +1,47 @@
+# Migration Strategies
+
+Migration from ASP<span></span>.NET Web Forms to Blazor is not simple and this repository attempts to make it easier for developers to reuse as much of their Web Forms application as possible.  The two technologies are 'concept compatible', but run on different implementations of the .NET runtime (.NET Framework vs. .NET Core / .NET 5+)
+
+We, the maintainers of this project, believe that with a little ingenuity the markup from a Web Forms application can be copied over with minimal changes and function similarly to its original purpose.  We believe that well formatted and maintained code in Web Forms should be easily migrated.  Applications that are a significant mix of C# and markup will have a more difficult time going through this process.
+
+## Known Required Changes
+
+There are several changes that are going to need to be made to the markup in your ASPX and ASCX files in order to get them working.  Some of these are obvious changes, and some are considerations necessary for the razor templating and Blazor rendering engine.
+
+### Visual Basic converted to C#
+
+Blazor uses razor templates which only support the C# language.  All Visual Basic in the markup will need to be converted to C#.
+
+### Bee-sting notation <% %> needs to be converted to @() notation
+
+ASP<span></span>.NET famously wrapped all .NET code in <% %>.  Starting with ASP<span></span>.NET MVC and razor templates, all C# code is wrapped in @() syntax.
+
+### _Imports files needed
+
+In order to match some of the syntax previously available in Web Forms markup, a series of `using static` statements are necessary to allow the appropriate shims to work with your markup.  You can find our sample of the `_Imports.razor` file here:  **INSERT LINK**
+
+### User Controls (ASCX files) need to be converted to components
+
+Components are the building blocks for Blazor, just as controls were in Web Forms.  If you have user controls in your application, you will need to convert those to components.  See the UserControl strategy below for more details.
+
+### MasterPages are no more
+
+The concept of a MasterPage does not exist in Blazor.  Instead, your ASPX pages will be loaded inside of a host page.  You can compose a razor component that hosts other *converted ASPX pages* but your pages cannot dictate their parent container.  See the MasterPage strategy below for more details.
+
+### Page Directive Changes
+
+### No Namespaces, No Tag-Prefixes 
+
+Namespaces and tag-prefixes are gone.  You can do a Find and Replace on asp: and remove those from your markup.
+
+## Strategies
+
+- A simple initial site migration
+- Intertwined code
+- Model-Binding
+- .NET Standard to the rescue!
+- Other considerations
+  - MasterPage
+    - Rearchitecting Web Application Layout
+  - UserControls
+    - The simple conversion