BlogEngine.NET VistaDB Providers update

I found a small bug in my initial release of the VistaDB providers DLL that I released on Friday.  I have made the correction and updated the download.  If you are already using the VistaDB provider, it is only the BlogEngine.VistaDB.dll file that needs to be updated in your site.

Please download the latest version to get the update.

Comments

6/23/2008 3:13:28 PM #

Kal

I am just getting started and thought VistaDB sounded good so I set it up and got the following:
If you see this post it means that BlogEngine.NET 1.3 is running and the VistaDB provider is configured correctly.

I did the same using SQLExpress with similar results.

In both cases I commented out the unused two providers.

In neither the case of MS Sql nor VistaDB am I able to log in. With the XML provider I can log in as expected, although I made no changes there in anticipation of setting up the other providers.

web.config sections:
    <blogProvider defaultProvider="VistaDBBlogProvider">
      <providers>
      <!--
        <add name="XmlBlogProvider"
       type="BlogEngine.Core.Providers.XmlBlogProvider, BlogEngine.Core"/>
        <add name="MSSQLBlogProvider"
       type="BlogEngine.Core.Providers.MSSQLBlogProvider, BlogEngine.Core"/>
           -->
    <add name="VistaDBBlogProvider"
      type="BlogEngine.Core.Providers.VistaDBBlogProvider, BlogEngine.VistaDB" dataSource="~/App_Data/BlogEngine.vdb3" password="" />
    </providers>
    </blogProvider>
  </BlogEngine>
  <system.data>
    <DbProviderFactories>
      <remove invariant="VistaDB.NET20"/>
      <add name="VistaDB.Provider" invariant="VistaDB.NET20" description=".Net Framework Data Provider for VistaDB"
         type="VistaDB.Provider.VistaDBProviderFactory, VistaDB.NET20, Version=3.3.1.54, Culture=neutral, PublicKeyToken=DFC935AFE2125461"/>
    </DbProviderFactories>
  </system.data>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="VistaDB.NET20" publicKeyToken="DFC935AFE2125461" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-3.3.1.56" newVersion="3.3.1.54"/>
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

    <membership defaultProvider="VistaDBMembershipProvider" >
      <providers>
        <clear />
      <!--
        <add name="XmlMembershipProvider"
       type="BlogEngine.Core.Providers.XmlMembershipProvider, BlogEngine.Core" description="XML membership provider" xmlFileName="~/App_Data/users.xml"/>
    <add name="MSSQLMembershipProvider" type="System.Web.Security.SqlMembershipProvider"
       connectionStringName="BlogEngine" applicationName="BlogEngine.NET" />
    -->
    <add name="VistaDBMembershipProvider"
      type="BlogEngine.Core.Providers.VistaDBMembershipProvider, BlogEngine.VistaDB" dataSource="~/App_Data/BlogEngine.vdb3" password="" />
    </providers>
    </membership>

    <roleManager defaultProvider="VistaDBRoleProvider" enabled="true" cacheRolesInCookie="true" cookieName=".BLOGENGINEROLES">
      <providers>
        <clear />
      <!--
        <add name="XmlRoleProvider"
       type="BlogEngine.Core.Providers.XmlRoleProvider, BlogEngine.Core" description="XML role provider" xmlFileName="~/App_Data/roles.xml"/>
    <add name="MSSQLRoleProvider" type="System.Web.Security.SqlRoleProvider"
       connectionStringName="BlogEngine" applicationName="BlogEngine.NET" />
    -->
    <add name="VistaDBRoleProvider"
      type="BlogEngine.Core.Providers.VistaDBRoleProvider, BlogEngine.VistaDB" dataSource="~/App_Data/BlogEngine.vdb3" password="" />
    </providers>
    </roleManager>
**************************
I have this running in a virtual directory.

Any clues?

Kal

Kal United States |

Comments are closed
Recent Comments