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: CONTRIBUTING.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,10 @@ Tell us how you are currently using the web forms framework so that we can build
71
71
1. Send a pull request with your desired scenario as a unit test in `src/BlazorWebFormsComponents.Test`
72
72
1.[Report an issue](https://github.com/FritzAndFriends/BlazorWebFormsComponents/Issues) with the details of a bug that you have found. Be sure to tag it as a `Bug` so that we can triage and track it
73
73
74
+
### Write some Web Forms sample code
75
+
76
+
Demonstrate how an existing control is being used in the `BeforeWebForms` project. The content of this sample project will be compiled and uploaded to the https://beforewebforms.azurewebsites.net location.
77
+
74
78
### Write code for a component
75
79
76
80
All code for a component should have an assigned issue that matches it. This way we can prevent contributors from working on the same feature at the same time.
[Live Samples running on Azure](https://blazorwebformscomponents.azurewebsites.net)
10
+
9
11
## Approach + Considerations
10
12
11
13
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.
The ListView component is meant to emulate the asp:ListView control in markup and is defined in the [System.Web.UI.WebControls.ListView class](https://docs.microsoft.com/en-us/dotnet/api/system.web.ui.webcontrols.listview?view=netframework-4.8)
2
4
5
+
[Usage Notes](#usage-notes) | [Web Forms Syntax](#web-forms-declarative-syntax) | [Blazor Syntax](#blazor-syntax)
6
+
7
+
## Features supported in Blazor
8
+
- Alternating Item Templates
9
+
- Alternating Item Styles
10
+
- Empty Data Template
11
+
- Empty Item Template
12
+
- Grouping
13
+
- Item Templates
14
+
- Item Styles
15
+
- Model Binding
16
+
- OnSelect Method
17
+
- LayoutTemplate
18
+
- DataBinder within the ItemTemplate and AlternatingItemTemplate
19
+
20
+
##### [Back to top](#listview)
21
+
22
+
## Usage Notes
23
+
24
+
- LayoutTemplate requires a `Context` attribute that defines the placeholder for the items
.NET Standard is the definition of a contract, a series of APIs, that all .NET frameworks must implement to be considered a .NET framework. .NET Framework, .NET Core, Xamarin, and Mono all implement various .NET Standard versions (or specifications) and this now becomes a vehicle for you to build your class libraries to be re-usable across various version of .NET.
2
2
3
-
>> Needs links to the .NET Standard specifications and repository on GitHub
3
+
[.NET Standard specifications](https://github.com/dotnet/standard) are managed in the open with definitions fore APIs and frameworks that .NET can be used with.
4
4
5
5
Class libraries can be built and target different version specifications of .NET Standard. You can target _ANY_ version of .NET Standard and gain compatibility across .NET Framework and .NET Core, but we recommend you target at least _.NET Standard 2.0_
6
6
7
-
>> Add image showing compatibility table of .NET Standard
7
+
8
8
9
9
## Implications
10
10
@@ -15,18 +15,14 @@ For your existing Web Forms applications, unless you are executing unsafe code o
15
15
1. Your business logic code is now isolated from your presentation code, and should be more testable. Write some unit tests to verify that your business logic is behaving properly.
16
16
1. If you'd like to write a mobile application to work with your web application, you can re-use your .NET Standard project with the Xamarin frameworks.
17
17
18
-
## Sample 1: Update an existing class library
18
+
## API Portability
19
19
20
-
The first sample demonstrates updating a simple class library to .NET Standard. In this model, we're assuming that you already have your business logic code properly separated from your user-interface and managed inside a class-library project that targets .NET Framework 4.5.
20
+
Portability is not guaranteed when you migrate business logic to .NET Standard. APIs have been changed or even removed in some cases. You should test your libraries and application for portability and take direction for possible migration paths using the official [.NET Portability Analyzer](https://docs.microsoft.com/en-us/dotnet/standard/analyzers/portability-analyzer).
21
21
22
-
###Sample
22
+
## Sample 1: Update an existing class library
23
23
24
-
This is a simple migration sample, demonstrating migrating a class-library from .NET Framework 4.5 to .NET Standard 2.0
24
+
The first sample demonstrates updating a simple class library to .NET Standard. In this model, we're assuming that you already have your business logic code properly separated from your user-interface and managed inside a class-library project that targets .NET Framework 4.5. You can find it in [samples/netstandard-1](../samples/netstandard-1/README.md) folder.
25
25
26
26
## Sample 2: Refactoring Business Logic
27
27
28
-
The second sample shows how to take an existing ASP<span></span>.NET application and refactor our some business logic as a .NET Standard project.
29
-
30
-
### Sample
31
-
32
-
This sample shows how to refactor some business logic from our Web Forms application into a .NET Standard library that can eventually be re-used in the .NET Core / ASP<span></span>.NET Core / Server-side Blazor application.
28
+
The second sample shows how to take an existing ASP<span></span>.NET application and refactor our some business logic as a .NET Standard project. You can find the source and directions for this sample in the samples/netstandard-2 (coming soon) folder.
0 commit comments