Kentico 9 MVC limitations?

Take a look in the documentation for the limitation list. I believe you can take advantage of Portal and MVC but not all 3. And yes you will be limiting the portal functionality by using MVC.

Thanks Brenden,

I looked through the documentation and I'm still not entirely clear on what you can/can't do. I could do with a list that specifically says that e-commerce isn't supported and how. I know that forms are supported because there is an API example. I'll take a look at the Dancing Goat example to try to figure out more.

I know that it's still early days for Kentico/MVC but I'd like to build some bespoke stuff using MVC but still retain the advantage of Kentico controls for the rest of the business site forums/payment gateways/logon so I'm wondering if there would be a way to split the MVC application without having to serve it on a separate domain or at least obtain 2 licences.

Hi Dan,

If you are looking to combine portal/ascx route with the new Kentico9/MVC features into one site just to forgo the need for your client to pay for a second license, then there is no need as Kentico will give you a free license for the external MVC site.

This question was asked, and answered, towards the end of the recent Kentico 9 - ASP NET MVC Support Webinar

With regards to using the MVC route going forward, we have come to the conclusion (for now) that the MVC route would be a feasible solution for a client requiring a brochure-ware website.

We will continue to develop using a combination of portal and ascx for more complex solutions, but that is not to say this might change as we learn more about the MVC route, and as the product matures.

Best regards, Michael

Hi Michael,

Thanks for this. I'm starting to get my head around it.

I'm building a bespoke service application that I'd like to use MVC for. However, I'd really like to use Kentico for the surrounding site. So I'm thinking that the logon page, blog, sign up, membership levels etc. will be straight up Kentico ASCX/Portal pages and when clicking a link to the MVC application part it'll just serve it up on a separate port/URL.

My understanding from what I've read etc. is that this is all perfectly fine and I should be able to keep, for example, user context between Kentico and my MVC application (that will still use the Kentico API etc.). Does that sound realistic?

Thanks for your input

Dan

What Michael is describing is basically what we're trying to do too. Our client's old site is built in an earlier version of MVC, but they now want some of the Kentico features like Smart Search. We were working on it in Kentico 8, but upgraded to 9 because we thought it would make the MVC part easier, such as bringing in a lot of our existing code, so that it would be a portal/mvc hybrid. The client can work on their content pages, and we can quickly hook up some MVC pages to our existing infrastructure.

However, nothing's working very well right now, we're having a lot of trouble with it. There was a ton of config wrestling to get the MVC site to work as a virtual directory under the CMSApp. Now this error keeps coming back when trying to hit an MVC route: http://stackoverflow.com/questions/1120329/could-not-load-type-mvcapplication

and if that doesn't happen, most of the time when I try to call Smart Search using the API from an MVC controller, the IIS Express worker process crashes, so I have no idea where the problem is.