I have encountered an issue with the newer versions of DNN - would appreciate some feedback, as I'm not sure if this should be considered a bug or just a "gotcha".

The problem is related to two things:

• The recent change to rename unused modules (in Install\Module\) from ".zip" to ".resources"
• Installing DNN to a folder named "Portal" (ie. c:\Inetpub\wwwroot\Portal\) instead of "DotNetNuke"

Taken from the DNN 4.5.1 Library source, the code of interest is in ResourceInstaller.InstallPortal():

If strFile.ToLower.IndexOf("\portal\") <> -1 Then
    'Check if valid portals file
     If strFile.ToLower.IndexOf(".resources") <> -1 Then

When InstallResources happens, it is basically looking at the different install locations to determine what to do with the contents. Because of the way the "if" statements are structured, it will always execte the InstallPortal() method. This means that when it is processing the "Install\Module" folder, it will execute InstallPortal().

In my scenario, it hits the above code processing the contents of "Install\Module".

• Since my site is installed to "Portal", the first check validates to true
• Since the "Install\Modules" folder contains a bunch of .zip files that have been renamed to ".resources", it passes the second check and attempts to process them as XML files
• This results in an exception thrown parsing the first .resources file it hits

You should be able to repeat this by simply installing DNN to a local folder named "Portal" instead of "DotNetNuke".

I have temporarily resolved it by renaming the all the Install\Module\ ".resources" files to a different file extension. The other solution would be not to install the site to "Portal", however in my scenario this is not something easily changed. Historically, this worked just fine... but the renaming of .zip to .resources is causing the issue.

I see a couple ways this could be resolved in DNN, wondering what you guys think.