Hi,

I have been using the code with this book to create my own CMS. I have copied the code 99%. However I am getting the following problem.

An error occurred creating the configuration section handler for xxxCMS: Could not load type 'xxxCMS.ConfigSection' from assembly '__code'.

<configSections>
<section name="xxxCMS" type="xxxCMS.ConfigSection, __code"/>
</configSections>

This occurs when i try to interact with the database.

Could someone help me please, I am hoping it is only something small.

Do you have the xxxCMS section following the configSections? It should look something similar to this:

<xxxCMS ...>
...
</xxxCMS>

If you haven't renamed the section from the Beerhouse example then that is the problem.

Thanks very much for your reply.

I do have the following

<xxxCMS defaultConnectionStringName="LocalSqlServer">

</xxxCMS>

Any ideas what else it could be?

Make sure your Globals.Settings (in App_Code) property is pointing to the correct section.

If you're early on in the book, and haven't got the SQL database set up then remove the defaultConnectionStringName parameter from the section.

Forgive my ignorance, but how i do locate the property you speak of?

I tried removing " defaultConnectionStringName="LocalSqlServer" but still same problem.

Thanks.

I uderstand what you mean now. The following is the code I have from the Globals.cs file in App_Code

namespace xxxCMS.DAL
{
    public static class Globals
    {
        public readonly static xxxCMSConfigSection Settings = (xxxCMSConfigSection)WebConfigurationManager.GetSe ction("xxxCMS");
        public static string ThemesSelectorID = "";

        static Globals()
        {

        }
    }
}

I think i have this coded correctly.

Still getting the same error though.

You actually have two problems:

One is your Globals namespace, because the Globals class isn't a DAL class.

Second is definition of Settings. You should change it to:
   public readonly static ConfigSection Settings = (ConfigSection)...

The incorrect namespace was the problem.

The second point you made only created another problem for me so I returned that to its original.

Thanks for your help, much appreciated.