[BUG] Components no longer load.

[wrharper-AASP]

A new error is coming up that has not existed in the past. For some reason I am getting markup errors despite loading components in _Imports aka @using NAMESPACEHERE.Components However, the Tab.razors still say, "Found markup element with unexpected name 'COMPONENTNAMEHERE'. If this is intended to be a component, add a @using directive for its namespace."

Imports I use: @using System.Net.Http @using Microsoft.AspNetCore.Authorization @using Microsoft.AspNetCore.Components.Authorization @using Microsoft.AspNetCore.Components.Forms @using Microsoft.AspNetCore.Components.Routing @using Microsoft.AspNetCore.Components.Web @using Microsoft.AspNetCore.Components.Web.Virtualization @using Microsoft.JSInterop @using Microsoft.TeamsFx @using Microsoft.Graph @using Microsoft.Graph.Models @using Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage @using System.Text.Json @using NAMESPACEHERE @using NAMESPACEHERE.Shared @using NAMESPACEHERE.Interop.TeamsSDK @using NAMESPACEHERE.Components @using NAMESPACEHERE.Data @using NAMESPACEHERE.Data.JSONS

for some reason it still can't find the component and returns the object instead of loading the page. I have verified it should be in NAMESPACEHERE.Components

[ghost]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

[wrharper-AASP]

Microsoft.TeamsFx version is 2.1.0 & Teams development kit that comes with Visual Studio 2022 17.6.2

[wrharper-AASP]

can confirm this has to do with 17.6.2 in some way because i upgraded to the preview version as a test and now it works again.

[wrharper-AASP]

it would definitely be better to have 17.6.2 fixed for TeamsFx over the preview because it is crashing left and right as expected heh...

[wrharper-AASP]

does anyone know of a way to install an older version as a "temporary" solution? I need to rollback somehow and the option that is supposed to be there is missing. I'm completely down and unable to publish updates due to this problem.

[wrharper-AASP]

This relates to https://developercommunity.visualstudio.com/t/175-crashes-and-warning-issues/10294265 at this point. I tried an OpenAI project and getting the same thing with that. So, this is a Blazor issue overall now.

[Alive-Fish]

@wrharper-AASP Thanks for reporting it and I hope to confirm what your question is.

Do you mean Microsoft.TeamsFx version 2.1.0 has some issue and you want to use the older version? Or you found that it is a Blazor issue and not is a Microsoft.TeamsFx issue.

[wrharper-AASP]

it looks like they re-opened the ticket in the link i provided. i gave them this link for reference since it has everything they should need to resolve the issue. just waiting for that at this point. this will likely be resolved sometime this week "fingers crossed"

[Alive-Fish]

Thank you. Please let us know if you need our team to do something.

[yiqing-zhao]

Hi @wrharper-AASP, I've created a project using VS 17.6.2 and TeamsFx 2.1.0 and added these imports to my code (Tab.razor)

@using System.Net.Http
@using Microsoft.AspNetCore.Authorization
@using Microsoft.AspNetCore.Components.Authorization
@using Microsoft.AspNetCore.Components.Forms
@using Microsoft.AspNetCore.Components.Routing
@using Microsoft.AspNetCore.Components.Web
@using Microsoft.AspNetCore.Components.Web.Virtualization
@using Microsoft.JSInterop
@using Microsoft.TeamsFx
@using Microsoft.Graph
@using Microsoft.Graph.Models
@using NAMESPACEHERE
@using NAMESPACEHERE.Shared
@using NAMESPACEHERE.Interop.TeamsSDK
@using NAMESPACEHERE.Components

But I did not encounter any error or warning messages. Can you please share more details about how to reproduce the error?

[wrharper-AASP]

It last worked in 17.5.5, it breaks in 17.6.2 and uses teamsfx 2.1.0

EDIT: It isn't just this, it happens to ALL blazor products now. Please see the link above your post. it isn't just me and it also happens in 7.0 apparently and i'm using 6.0.