There is nothing directly which does what you want, but many of the pieces are available in the code for the Host > Extensions page. Specifically, the more extensions tab will allow you to download code from a well known URL and then install those pieces directly.  The problem is, the system would still see those as separate packages so you would need to figure out how to manage installation yourself (it could be as simple as unzipping files to the appropriate directories). 

---

Joe Brinkman
DNN Corp.

IIS7's default maxRequestLength is 28.6MB (30,000 kbytes). I don't know where the current DNN 12M size came from. Maybe a left over from an earlier version of IIS?

The default maxRequestLength needs to be larger. Modules and extension sizes are getting bigger. Just few days ago a DNN theme creator said he created a theme which is 120M big.  I am pretty sure zipping this with maximum compression, it's still bigger than 12M.

The reason there's a maxRequestLength was to protect IIS from possible disruptive large file uploads or requests. This is a valid protection measure. However the extensions installer and uploader lives in a protected area which is not accessible by the public. The default maxRequestLength can stay as is but add a web.config exception for the extensions page like this. I propose DNN starta shipping with this added config setting:

(Pasting html is not working so I converted the angle brackets to square ones)

[configuration]

…

  [location path="nameofextentionspage.aspx"]

    [system.web]

      [httpRuntime maxRequestLength="102400"/]

    [/system.web]

  [/location]

…

[/configuration]