Enable MVC Views/Pages to invoke a Component as a TAG

[rynowak]

We want to support views/pages using components using the normal element syntax. This is an upgrade over the current support for using HtmlHelper to invoke a component.

We need to do significant design and scoping work here to figure out the limitations and caveats of enabling this.

[javiercn]

Not sure why this is still open.
@rynowak is this not the HtmlHelper extensions or is this meant to be deeper integration, like calling a component as a tag from a view/page.

[rynowak]

This should track using components AS TAGS from views. Updating the main post.

[LorenDorez]

@rynowak I managed to get RC working in MVC Views but had to update the components.server.js file a bit. repo here

I cant wait for this to be fully integrated into MVC so i dont have to map RC components to random HTML tags. Might need to do a Prefix though since you could have a Component named to a current standard html tag like button

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[mkArtakMSFT]

@danroth27 any objections against closing this?

[danroth27]

@danroth27 any objections against closing this?

No objections from me. We have the component tag helper for rendering components from MVC views and Razor Pages. If you want Blazor component syntax end-to-end you can create a Blazor Web App.