Razor components vs View Components

Question

I recently upgraded from Asp .NET Core 2.2 to 3.1 and can use Razor Components in razor pages. They look basically like View Components except it uses blazor and everything on the same file. I tried to search but i haven't read anything on documentation that says to use Razor Components instead View Components.

So here is the question...

What is the point of using Razor Components instead View Components in Razor Pages? Is it better? I know View Components are a bit painful to set because you have to set a default view and a code behind file with the logic and you cannot use javascript on it, only on the parent view. Most of my apps are full of View Components and I was wondering what are the advantages of switching to razor components?

Gaige

After assigning bounty, I've found this answer useful: #59262991 – Kessel

Answer 1

While View Components are more like partial views but asynchronous, DI friendly, and kind of independent. They are mostly for view-only purposes (yeah it's possible to add some update logic via AJAX but it's more like a hack rather than a feature) and are used mostly to re-use common UI units like navigation, login block, sidebar, etc.

Razor Components are sort of "full featured" UI components, which can be easily nested, pass parameters through the components hierarchy, raise and handle UI events, and so on. So you can easily use them to manage your app UI, or even create custom UI component libraries.

Heliotropin

are those components used only as Blazor? – Gilleod

can i use javascript inside View Components ?? – Seldun

Yes, see #44511834 – Heliotropin

Answer 2

As you said above, Razor Components uses one file for everything but View Components is a little boring.

Razor Components look better but have a big problem that you can't use Tag Helpers inside them. So that makes it hard to use Razor Components for forms or other similar parts that uses Tag Helpers.

Sauceda