Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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 ExtensionsModulesModulesNeed Help!  Module broken after upgrading to Visual Studio 2012Need Help! Module broken after upgrading to Visual Studio 2012
Previous
 
Next
New Post
5/30/2013 4:16 PM
 

I have been working on building a DNN module in VS 2010 under DNN 7.0.3.  My module has a few controls, a web service, and some jQuery/Ajax calls to the web service.  I am working in Windows 7 with IIS 7.  Everything was fine until I upgraded to VS 2012. After that, I was getting 500 errors for all the files I am loading into my control, i.e. javascript files, css files, and even images (never saw a 500 error on an image before!).  I tried rolling back my project to before I loaded it into VS 2012, but that didn't help.  I found this article: http://stackoverflow.com/questions/20... and implemented the suggestion in answer 2 (adding <location... to the web config file).  That fixed most of the problems, but I am still getting 500 errors for 2 HttpHandlers I built (which just spit out some javascript) and for any calls to my web service.  The error I am getting now is:

Parser Error. An error occurred during the parsing of a resource required to service this request.   Please review the following specific parse error details and modify your source file appropriately. 

It kind of looks like it can't find the codebehind for these files.  That makes some sense, since that was basically the problem it was having with all the files before I added the <location> tag to the web.config.

I tried a clean install of DNN 7.0.6 and just installed my module from the package that was created earlier, but still the same errors.  Since I haven't made any change to my code since it was last working, I am pretty sure the problem has something to do with changes the VS 2012 install made to my machine but I have no idea what.  Please help!!! 

Thank you :-)

 
New Post
6/10/2013 8:14 AM
 
one thing that you can look at is if VS2012 automatically created an application of the directory that you are developing your module in. Ie, go to IIS, open the treeview of your site, all the way to your module directory (eg. /desktopmodules/mymodule). If that directory is marked as an application, then right click it, and select remove.

That's a bug in vs2012 (or a feature: it thinks that every web application project (which is the project type of a compiled module) needs a web application defined in IIS. For DNN that is definitely not true!. best way to prevent is is to select "other webserver" in your projects web settings

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesNeed Help!  Module broken after upgrading to Visual Studio 2012Need Help! Module broken after upgrading to Visual Studio 2012


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