New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDNN 8.0 doesn't support @Html.Action in MVC modules?DNN 8.0 doesn't support @Html.Action in MVC modules?
New Post
1/18/2016 8:23 PM


This is now another limitation where the MVC module support in DNN doesn't support a core ASP.NET MVC functionality. First there's no support to return partial views or other kinds of action results like json in controller actions. I tried to use @HTML.Action as a workaround and now I find out it's not supported either!!

RenderPartial doesn't solve my  issues. There are third party mvc extensions that need to call controller actions to update themselves asynchronously. For example when a grid needs to use a filter or sort its data. It seems we can only create mvc modules where user actions will require full page refreshes only instead of in-place ajax updates through Javascript. I am stuck with how some third party MVC controls work. I am not talking about my using my own Javascript or doing SPA with SPA modules.

When dnnsoftware announces that they support modules developed ASP.NET MVC, they should have also mentioned the support is limited and they should have listed the core ASP.NET functionality that is not supported instead of the developers spending hours or days to be surprised that they might hit some roadblocks because of missing information.

So why the missing support? Insufficient time? I hope you don't consider the missing functionality as unimportant.

As the MVC support in DNN stands now, it doesn't fit my needs and it's not useful enough. I think I will have to wait till these functions are added or wait for vNext.



New Post
1/20/2016 1:07 PM

I haven't written a skin or container at all in years. I find it overly time consuming to code my own skins since the DNN Store has many to offer that fulfill most needs. However, the skins I bought from 2 different major developers have problems with DNN 8.  One still uses ACTION and ACTIONBUTTON functionalities in their skins.  When I contacted them about the tests on our development server, they were unaware of the problem.  Since contacting them, they are now rewriting their skins to remove the ACTION and ACTIONBUTTONS calls. The second developer's menu doesn't display and they are investigating. 

I really feel for anyone creating web sites that upgrades without having a development testing server like I do.  If they research carefully prior to applying the latest release, they might find the problem listed or not realize what the impact is before their production site is totally hosed up.

Since DNN owns the store, has there been any proactive notification to sellers about the removal of functionalities?  I know, there are plenty of release notes, etc. But as both the developer of the architecture and the wholesaler of products, I feel the wholesaler arm should be responsible for some notifications.  After all, not all skin developers are worried about the changes.  They might be a small shop or even a 1 or 2 time seller and then they are gone.

Lastly, taking out a features that is as wide-ranging of an impact as ACTION and ACTIONBUTTONS seems very short-sighted.  You have hundreds of thousands of web sites running DNN with some skins that are very old.  Sure, everyone should upgrade to mobile-ready skins that were developed very recently, but the truth of the matter is that many customers don't want to spend the money for a redesign.  But they will care when the developer upgrades to the latest version of DNN and their site breaks.

I applaud the efforts to move forward, but some sort of customer feedback prior to actually making breaking changes should be put directly to your clients.  Maybe taking a page from Microsoft's new playbook and have a feedback about features would be helpful.  And I'm not talking about putting bug reports in.  Too formal, too time intensive.  Just something to tell us what's planned and open it up for comments.  If you haven't used the feedback in Windows 8 or 10, you should check it out.

New Post
1/20/2016 3:57 PM


Do the ACTION menus use @HTML.Action(...)? I am not sure how old skins are using this syntax. 

"Since DNN owns the store, has there been any proactive notification to sellers about the removal of functionalities?"

You're hoping for too much. They haven't been proactive in many areas. They made a general statement that DNN 8.0 will support MVC modules when the truth is that the support is pretty limited. They should have indicated that the support is partial and provided a release note on what is not supported instead of having developers believe they'r getting full support. Just like developing ASP.NET MVC apps. I am getting one unpleasant fact from this after another. Instead of coding with pleasure, I am fighting DNN with the unseen limitations. So I am putting my module development on hold until better MVC support comes along. I believe module developers are better off using SPA modules (if they don't want to use WebForms).



New Post
1/22/2016 11:54 AM

Actually, I'm not sure if the ACTION and ACTIONBUTTONS use it.  Besides skins, I haven't written any modules since 2007, so I'm in the dark here.

But to the point about the store.  DNN bought the store a few years ago and I was hoping that it, being under the corporate umbrella, would be more in tune with the sellers on the marketplace.

But, I have contacted all the sellers of the skins that I have still in use.  Of those that responded, 1 is fixing them soon, 1 is investigating and 3 haven't answered.  With the number of DNN sites out there, and I am sure many haven't been redesigned with newer skins, I'm surprised that this type of functionality is removed.

Sorry if I stepped into a conversation that is not about ACTION functionality per se.

New Post
1/22/2016 1:33 PM
Yeah I think your issue has nothing to do with what I am reporting. My issue is very MVC specific and MVC support only came out last week. There's no way a skin, new or old, is going to experience it now. I am just reporting I am discovering that DNN's new MVC support is pretty limited. Well... cripplingly limited to the way *I* program MVC apps.
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDNN 8.0 doesn't support @Html.Action in MVC modules?DNN 8.0 doesn't support @Html.Action in MVC modules?

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out