Added TreeView component (#60)

Added TreeView component

Author: csharpfritz

CODE-OF-CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project leader at [[email protected]](mailto:[email protected]). All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,84 @@
+# Contributing to BlazorWebFormsComponents
+
+Thank you for taking the time to consider contributing to our project.  
+
+The following is a set of guidelines for contributing to the project.  These are mostly guidelines, not rules, and can be changed in the future.  Please submit your suggestions with a pull-request to this document.
+
+1. [Code of Conduct](#code-of-conduct)
+1. [What should I know before I get started?](#what-should-i-know-before-i-get-started?)
+    1. [Project Folder Structure](#project-folder-structure) 
+    1. [Design Decisions](#design-decisions)
+1. [How can I contribute?](#how-can-i-contribute?)
+    1. [Tell us your story](#tell-us-your-story)
+    1. [Write code for a component](#write-code-for-a-component)
+    1. [Write documentation](#write-documentation)
+
+
+## Code of Conduct
+
+We have adopted a code of conduct from the Contributor Covenant.  Contributors to this project are expected to adhere to this code.  Please report unwanted behavior to [[email protected]](mailto:[email protected])
+
+## What should I know before I get started?
+
+This project is currently a single library that will provide a shim, a buffer that will help you convert markup to run in Blazor. The project will grow in the future to support more automated conversion from ASP<span></span>.NET Web Forms to Blazor.
+
+### Project Folder Structure
+
+This project is designed to be built and run primarily with Visual Studio 2019. The folders are configured so that they will support editing and working in other editors and on non-Windows operating systems.  We encourage you to develop with these other environments, because we would like to be able to support developers who use those tools as well.  The folders are configured as follows:
+
+```
+/docs                                 -- User Documentation
+/samples                              -- Usage Samples 
+  BeforeWebForms
+  AfterBlazorClientSide               -- Shell project with WebAssembly config
+  AfterBlazorServerSide               -- Shared project with Server-Side config
+    /Pages/ControlSamples/COMPONENT_NAME/SCENARIO.razor
+/src                                  -- Library source and unit tests
+  BlazorWebFormsComponents
+  BlazorWebFormsComponents.Test
+    /COMPONENT_NAME/test.razor        -- Unit tests
+```
+
+
+
+We may add a top level `tests` folder if there are integration tests to show at some point.
+
+All official versions of the project are built and delivered with Azure DevOps Pipelines and linked in the main README.md and [releases tab in GitHub](https://github.com/FritzAndFriends/BlazorWebFormsComponents/releases).
+
+### Design Decisions
+
+Design for this project is ultimately decided by the project lead, [Jeff Fritz](https://github.com/csharpfritz).  The following project tenets are adhered to when making decisions:
+
+1. All attributes of the original controls should be supported. This helps emphasize the 'convert your markup' feature. 
+1. HTML markup generated by the components should replicate the markup generated by the original controls.  This helps to ensure the components behave as the Web Forms controls were expected to.
+1. Minimal .NET APIs should be supported, in order to present the API.  The following are the primary APIs available:
+    1. Component events: OnInit, OnLoad, OnPrerender, OnUnload
+    1. DataBind()
+1. The following APIs and Controls will NOT be supported:
+    1. **DataSources** - These are components that provide connectivity to a data source.  In Blazor, this code should be moved to a Repository pattern and classes.  You can still connect that Repository to the components and work with the data.
+    1. **ViewState** - There is no viewstate in Blazor.  ViewState is marked obsolete on components, and state of your interactions with the controls should be stored in private variables or Session.
+    1. **Postback** - There is no postback in Blazor, therefore we will not support this feature.
+
+## How can I contribute?
+
+We are always looking for help on this project.  There are many millions of applications built that target ASP<span></span>.NET Web Forms, and we need your help building and identifying scenarios that need to be supported.  There are several ways that you can help:
+
+### Tell us your story
+
+Tell us how you are currently using the web forms framework so that we can build to meet your needs.  This means one of several types of contributions:
+
+1. Send a pull request with a sample page that shows your scenario in the `samples/BeforeWebForms` project
+1. Send a pull request with your desired scenario as a unit test in `src/BlazorWebFormsComponents.Test`
+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
+
+### Write code for a component
+
+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.
+
+Any code that is written to support a component are required to be accompanied with unit tests at the time the pull request is submitted.  Pull requests without unit tests will be delayed and asked for unit tests to prove their functionality.  We use the [Razor Components Testing Library](https://www.nuget.org/packages/Razor.Components.Testing.Library/) to test our components.
+
+Code for components' features should also include some definition in the `/docs` folder so that our users can identify and understand which feature is supported.
+
+### Write documentation
+
+The documentation for the migration and consumption of these components will be significant in scope and need to cover many scenarios.  We are always looking for help to add content to the `/docs` section of the repository with proper links back through to the main `/README.md` 

Directory.Build.props

@@ -2,8 +2,8 @@
 <Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
   <ItemGroup>
     <PackageReference Include="Nerdbank.GitVersioning">
-      <Version>3.0.28</Version>
+      <Version>3.0.50</Version>
       <PrivateAssets>all</PrivateAssets>
     </PackageReference>
   </ItemGroup>
-</Project>
+</Project>

README.md

@@ -2,7 +2,7 @@
 
 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)  
+[![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)
 
 [![Nuget](https://img.shields.io/nuget/v/Fritz.BlazorWebFormsComponents?color=violet)](https://www.nuget.org/packages/Fritz.BlazorWebFormsComponents/)  [![Nuget (with prereleases)](https://img.shields.io/nuget/vpre/Fritz.BlazorWebFormsComponents)](https://www.nuget.org/packages/Fritz.BlazorWebFormsComponents/)
 
@@ -37,7 +37,7 @@ There are a significant number of controls in ASP.NET Web Forms, and we will foc
   - Navigation Controls
     - Menu
     - SiteMapPath
-    - TreeView
+    - [TreeView](docs/TreeView.md)
   - Login Controls
     - ChangePassword
     - Login