blog documentation should be replaced with only officials docs

[mbcrump]

ToastNotificationService.cs and probably others

        //TODO UWPTemplates: Handle activation from toast notification,
        //for more info handling activation see
        //https://blogs.msdn.microsoft.com/tiles_and_toasts/2015/07/08/quickstart-sending-a-local-toast-notification-and-handling-activations-from-it-windows-10/

[ralarcon]

@crutkas @mbcrump We used this as reference but we need to sync all together to decide what is preferred.

[crutkas]

Docs when 100% possible, else defer to blog. for this example that Crump referenced, does https://docs.microsoft.com/en-us/windows/uwp/controls-and-patterns/tiles-and-notifications-adaptive-interactive-toasts handle it?

[crutkas]

Crump, we need to just do a full walk down of everything now that Codebehind is added.

[crutkas]

Community, thinking this would be a great item for everyone to look at. be sure the documentation makes sense.

[mrlacey]

Having a look now and will raise individual issues but as a general point.
Comments should have a space between the delimiter (//) and the start of the comment.

It's not mentioned explicitly in our code guidelines but is covered in the C# Coding Conventions on MSDN (snippet below.)

Commenting Conventions

• Place the comment on a separate line, not at the end of a line of code.
• Begin comment text with an uppercase letter.
• End comment text with a period.
• Insert one space between the comment delimiter (//) and the comment text, as shown in the following example.

    // The following declaration creates a query. It does not run
    // the query.

• Do not create formatted blocks of asterisks around comments.

[crutkas]

Went through and did a bunch of work on this.
514eba4
ff467ad
94dceaa

I think as is, this is a vague issue and should also be closed out w/ actionable, new bugs