Module Output Templates Agility .net core - differences between View Component and Partial View? What about Controller Action?

With .net core and the creation of ViewComponents, Agility now utilizes this new .net core feature:

Are there differences in performance between these two ways to invoke the module in .net core? For example, if defining the partial view path directly, would you lose out on the benefits of Async ViewComponents?

Also, with modules you can no longer chose a controller/action, is this still possible somehow in Agility's .net core version?

Thanks!

1

Comments

2 comments
  • Official comment

    Hi there - not a huge perf difference between the ViewComponents and direct to Partial Views.  ASP.Net Core removes the notion of Partial Controllers and replaces it with ViewComponents, so you can no longer use a Controller Action to render a Module.

    The best part about moving to .Net Core is the ability to do everything async.

    Comment actions Permalink
  • Cool thanks Joel :) 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post