Implements Component code generation and tooling support end to end
udditionally adds some default `@addTagHelper` directives to make
programming in Blazor a little nicer.
Components are discovered as Tag Helpers using Razor's extensibility
during the build/IDE process. This drives the code generation during
build and lights up a bunch of editor features.
Add
This is a working (all tests passing) implementation of the two-phase
compilation system we will need for component discovery.
This builds on top of work we've doing in Razor, including the Razor
SDK, MSBuild tasks, and CLI/server.
This currently *does* discovery components during the build process, but
it doesn't use that data for anything yet.
It works like this:
1. Generate class declarations (structure only, no method bodies)
2. Compile a 'temp' assembly using the .cs files and output of 1.
3. Do component discovery using the 'temp' assembly
4. Generate class definitions (including method bodies)
5. Compile the 'real' assembly using the .cs files and output of 4.
Adds a little more use of Razor extensibility.
Razor is a plugin model, so we can't be the 'first mover' for initiating
compilation in the build tools and IDE.
Reorganizes tests and fills out more reusable test infrastructure for
Razor-driven testing.
Adds tests for declaration-only configuration.
* Remove unnecessary <OutputType>Exe</OutputType> from templates
* Rename BlazorHosted.* projects to BlazorHosted.CSharp.(Client|Server)
* Add empty BlazorHosted.CSharp.Shared, referenced from the two other BlazorHosted.CSharp.* projects
* Have BlazorHosted.CSharp.Client fetch data from BlazorHosted.CSharp.Server
* Update templates to Blazor 0.0.5-preview1-10037
* Make date handling consistent across the templates
* Enable response compression in "hosted" template
* Enable response compression in dev server
* Simplify template app code using new namespace arrangement
* Fix project name in hosted template
Steve Sanderson
Ryan Nowak
Florian Dohrendorf
forest93
Daniel Roth
alexgav