Error in LayoutComponent breaks at the wrong location.

If you have an error in the properties of a layout component, the error appears at the parent razor page include line instead of the actual error location.

Example:

Index.razor (this is where the error breaks at): <MyProject.PrintMessage ParameterMessage="@Message"/>

PrintMessage.razor (where the real error is):

public static string LowercaseMessage = "";

     // route the given parameters to static, this is because our JSInvokables are static.
    public static string Message = "";
    [Parameter]
    public string ParameterMessage
    {
        get
        {
            return Message;
        }
        set
        {
             LowercaseMessage = Message.ToLower();   // <--------- this is the real error here since Message is undefined.

            Message = value;
        }
    }

... razor code ..

 [JSInvokable]
    public static string OnMouseClickPrintMessage()
    {
        string message = LowercaseMessage;

        // do something with message
    }
`

This is the error when you try to load the <MyProject.PrintMessage ParameterMessage=“@Message”/> razor snippet. Notice that this error is appearing at this.StateHasChanged() and not at “PrintMessage.razor”

[mkArtakMSFT]

Thanks for contacting us, @Bambofy. We’ll look into this post 3.1 timeframe and will get back to you then.

[captainsafia]

I just gave this a go on VS 16.6 Preview and the exception breaks at the LowercaseMessage = Message.ToLower(); line so it looks like this issue is resolved now.