Title: Blazor layouts
UID: client-side/blazor/layouts
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/layouts

• Defining layouts
• Using layouts

@rstropek will take this one. Thank you @rstropek! 🚀

Texas two-step ...

• Choose a replacement sample
• Finish the sample app
• List parts (sub-topics) and create outlines+goals for each part
• Write the sub-topics
• Publish live version of the sample

Title: Dependency injection in Blazor
UID: client-side/blazor/dependency-injection
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/dependency-injection

• Configuring services
• Resolving services
• Built-in services

@rstropek will take this one. Thank you @rstropek! 🚀

https://blazor.net/docs/host-and-deploy/index.html#app-base-path

Add a trailing slash to <base> href in examples.

Thanks @RemiBou for reporting in https://github.com/aspnet/Blazor/issues/668.

Because this isn't a tutorial, let's try to avoid screenshots if possible and just provide a list of steps with links out to other topics if/when it makes sense ... especially to our aspnet/Docs topics:

• https://docs.microsoft.com/aspnet/core/host-and-deploy/azure-apps/
• https://docs.microsoft.com/aspnet/core/host-and-deploy/azure-apps/troubleshoot (but this only applies to the server-side ASP.NET Core bits)

We should move the routing content out of the components doc into a separate routing topic.

• Router component
• @page
• NavLink component

See https://github.com/aspnet/Blazor/issues/413#issuecomment-379435380.

This is essentially blocked until it can be determined if a completely flat directory structure for published assets will be instituted. Without a flat directory structure, a Blazor deployment can't sit in the $root container of Azure Storage (/ path delimiters aren't allowed in the $root container).

Hi,

it was founded a kind of typo in the Child content section of the Components page:

ChildComponent.cshtml:

<div class="panel panel-success">
  <div class="panel-heading">@Title</div>
  <div class="panel-body">@PanelContent</div>
</div>

@functions {
    public string Title { get; set; }
    public RenderFragment **PanelContent** { get; set; }
}

I got a fault when trying to execute this example. After a discussion in an issue report https://github.com/aspnet/Blazor/issues/686 it was founded the PanelConent field's name is incorrect. It is suggested to rename this to ChildContent. Unfortunatelly, there are still some errors with this name using. As a result I'm not sure how this example should be improved.

If you like please add this site to community page's samples section.
Thank you.
http://lupusablazordemos.azurewebsites.net/

Remove all references to ILayoutComponent. This interface will no longer exist in Blazor 0.3.0. Replace all layouts’ @implements ILayoutComponent with @inherits BlazorLayoutComponent and remove the @functions { .. } block that declares the Body property (since that’s now inherited from the base class).

Title: ASP.NET Core Blazor
UID: client-side/blazor/index
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/

• TOC
• Define & describe
• Link out .NET site Get started content
• aspnet/Docs issues
• Filing bugs/suggestions in Blazor repo
• Link Blazor repo release notes

Using chrome:

Regarding https://blazor.net/docs/host-and-deploy/index.html:

• Should say developers need to add a reference to Microsoft.AspNetCore.Blazor.Server
• When giving instructions to update index.html, should clarify that this is the file under wwwroot, and not the similarly-sounding Index.cshtml.

These suggestions taken from https://github.com/aspnet/Blazor/issues/961

We should have a topic around the new component library template that shows how to build, package, and share libraries of components.

See https://blogs.msdn.microsoft.com/webdev/2018/04/17/blazor-0-2-0-release-now-available/ for some existing content.

Would be nice to be able to export docs to PDF. DocFx supports PDF export, but has a dependency on wkhtmltopdf which might be a little hard to integrate with the GitHub pages hosting.

I think the way to do this would be to integrated it into the AppVeyor build. There's a Chocolatey package for wkhtmltopdf, and AppVeyor supports Chocolatey installs, so that may be one way to do it. Another is just to use the wphtmltopdf installer.

Once that dependency is in place, we just need to add a pdf section to our docfx.json file and we'll have a PDF generated.

Excellent introduction. One place for improvement: The databinding didn't make sense. The statement "The Year parameter is bindable because it has a companion YearChanged event that matches the type of the Year parameter." needs to explain the action. Also, what is format-value in <input bind="@StartDate" format-value="yyyy-MM-dd" /> Is this a blazor tag-helper? That needs explanation.

For https://blazor.net/docs/host-and-deploy/index.html#app-base-path, surface that NavLinks must also receive the URL segment to work. The current text adequately covers the <base> tag but nothing is mentioned about the NavLinks.

Title: Troubleshoot Blazor
UID: client-side/blazor/troubleshoot/index
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/troubleshoot

Content: TBD

See dotnet/blazor#685 for lots of details.

Title: Host and deploy Blazor
UID: client-side/blazor/host-and-deploy/index
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/host-and-deploy

• Standalone deployments (notes on Azure CDN, file server, GitHub Pages)
• Redirects for correct routing
• Hosting in ASP.NET Core
• Publishing
• IL trimming

• Blazor development-time testing (as of 0.2.0, live reloading is still in design)
• Blazor unit testing

• HttpClient
• JSON helpers
• Setting fetch arguments for the request (see dotnet/blazor#399 (comment))
• Making cross origin request

Since I just used the Components sample as the demo for the Routing topic on #102, let's move the Components topic sample to a better position in the TOC (up one level) and rename it so that it applies better to any topic in the TOC. We can just run with one sample (for the reference topics only) for a while, which will simplify maintenance of all of the topics during preview. The tutorial will still have its own sample, and it will stay in its current position.

This is low priority work and can be performed at any time. Backlogging it for now.

Convert components sample from 0.2.0-preview1-10155 to 0.2.0 and drop Nuget.config/global.json.

• Component libraries
• Routing
• Built-in Blazor components (as of 0.2.0: NavLink)
• Creating components in C# (F#/VB ?)
• Logging
• Error handling
• Partial classes (not available as of 0.2.0) and/or BlazorComponent base classes

See dotnet/blazor#685 for details

Title: Build your first Blazor app
UID: client-side/blazor/first-app
URL: /build-your-first-blazor-app

• Downloadable sample
• Standalone project using Todo Gist

Reference:

• https://blazor-demo.github.io/
• https://github.com/aspnet/samples/tree/master/samples/aspnetcore/blazor/FlightFinder

We shouldn't have the Blazor assemblies checked into the docs repo. Instead we should have some automation that restores the Blazor packages and extracts the Blazor assemblies and XML doc files that we can then run docfx on.

Blazor JavaScript and TypeScript interop
docs/javascript-typescript-interop.md

Add the JS interop example into the sample app.

Note in Host and deploy pertaining to local hosting of static assets:

Blazor sets up its own static file middleware to handle static file requests to content from the Blazor client app, not from the server project.

Note first tho that a CDN should be used for static assets and mention+link Azure Storage/CDN for this purpose.

Note that static assets for the client-side app can't be hosted in the server-side app using Static File Middleware at this time.

@syedshanu has a nice sample about using Blazor with ASP.NET Core and EF:

• https://www.codeproject.com/Articles/1244729/ASP-NET-Core-Blazor-CRUD-using-Entity-Framework-an
• https://code.msdn.microsoft.com/vstudio/ASPNET-Core-Blazor-122b108a

It would be great to list this sample on the Blazor Community page.

@syedshanu do you want to submit a PR for this? Which link would you prefer we use?

Update API refs for Blazor 0.3.0.

Event handlers can be async and return Task.

• No need to manually call StateHasChanged()
• Improved error handling (exceptions will be caught and logged correctly)

Add the FAQ to the introduction folder.

Link API references to the API topics.

Title: Introduction to Blazor
UID: client-side/blazor/introduction/index
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/introduction/

http://blog.stevensanderson.com/2018/02/06/blazor-intro/

Title: Blazor components
UID: client-side/blazor/components/index
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/components

• Using Razor
• Inline vs code behind
• Event handling
• Data binding and validation
• Rendering child content
• Providing parameters
• Specifying child content
• Routing
• JS/TS interop

We should document how to setup a code behind file using @inherits. Later, we can update this section when we implement support for partials (https://github.com/aspnet/Blazor/issues/278)

https://github.com/aspnet/Blazor/wiki/FAQ

Ex --pathbase

Update screen shots and code snippets taken from the templates

Title: Blazor JavaScript and TypeScript interop
Path: docs/javascript-typescript-interop.md
UID: client-side/blazor/javascript-typescript-interop
TOC: JavaScript/TypeScript interop between Dependency Injection and Host and deploy

Add to toc.md and to the docs index.md page in the same spot as the TOC.

Attribute component parameters with [Parameter]

Component parameters should be private properties. Analyzer will flag parameters defined with public properties.

• Wire up TOC
• Wire up the landing page
• Confirm cross-linking
• Push 0.2.0 assemblies to the repo
• Validate ComponentsSample and BlazorApp1 sample run normally.

In the Dependency injection in services section,
the class and the constructor don’t match

public class DataAccess : IDataAccess
{
// The constructor receives an HttpClient via dependency
// injection. HttpClient is a default service offered by Blazor.
public Repository(HttpClient client)
{
...
}
...
}

See dotnet/blazor#691 for details.

Here:

The "active" class is hitting the wrong list item. The UI scrolls to the right spot, but it highlights the wrong entry.

For the following example, I clicked on "Build a todo list" ... "Dependency injection" is receiving the "active" CSS class.

cc/ @danroth27

• Include StateHasChanged