Search code examples
iis-7dotnetnukedotnetnuke-moduledotnetnuke-7

DotNetNuke Module keeps converting itself into Application in IIS7


Bit of a weird one. For some reason one of my DNN modules keeps being converted into an Application in IIS7 in my development environment. Meaning when I try to view a page that contains that module it can't find the module correctly. It's ok if I go into IIS and delete the application, then restart the site but is a bit of a pain and am little worried it might do this when uploaded to the live server and disable the whole site.

Anyone encountered anything like this before? Any thoughts?


Solution

  • This is a common problem with my VS templates, though not for everyone, and it doesn't happen all the time. It stems from Visual Studio, so it shouldn't ever be a problem on your production servers, unless you upload source and try to compile there, than it might be an issue.