Installing BlogEngine via Web Application Gallery

Discussion in 'Third-party applications' started by sebulba, Apr 23, 2011.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. If I install BlogEngine.net via the Web Application Gallery am I giving up anything as far as the ability to customize BlogEngine.net? One of the main things I need to do is install BE in a sub-directory (i.e. example.com/blogs). I may also need to do other customizations though beyond just skinning BE. My DASP server type is Windows 2008 - IIS 7.0.
     
  2. Joseph Jun

    Joseph Jun DiscountASP.NET Staff

    No, there aren't any limitations if you install applications through the Web Application Gallery Installation Tool so you'll have full functionality.
     
  3. I'm not sure if this is the correct place to post this, but I am having issues installing BlogEngine.net via the web app gallery. I'm trying to install it in a subdirectory of my site (.net 4.0 web application) and am getting the following config error when navigating to the site:

    There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined
     
  4. Thanks wisemx.

    I removed the following sections from the BlogEngine web.config and was able to log on to the site

    Code:
    <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
          <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
            <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
            <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
              <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
              <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
              <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
              <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
            </sectionGroup>
          </sectionGroup>
        </sectionGroup>
    Now on to the next error :)
     
  5. ...Good job ;-)

    btw, Just read your post, (Celia Rae and Isabel Lynne), Congratulations Senior.
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page