Dear Wrox

I have having a problem when I click on the Admin tab in that the error message below appears in the browser.

Compiler Error Message: BC30456: 'Theme' is not a member of 'ASP.management_default_aspx'.

Source Error:
Line 1: <%@ Page Language="VB" MasterPageFile="~/AdminMaster.master" AutoEventWireup="false" CodeFile="Default.aspx.vb" Inherits="_Default" title="CMS Management Home Page" %>
Line 2: <asp:Content ID="Content1" ContentPlaceHolderID="MainContentPlaceholder" Runat="Server">
Line 3: <h1>Welcome to the Wrox CMS</h1>


Source File: C:\inetpub\wwwroot\CMS\Management\Default.aspx Line: 1

I've also tried it in debug where a number of errors are thrown up.
The errors seem to relate to properties and classes not being found. A couple of samples are (from the 42 total) are:

Error 97 Make sure that the class defined in this code file matches the 'inherits' attribute, and that it extends the correct base class (e.g. Page or UserControl). C:\inetpub\wwwroot\CMS\Management\ContentList.aspx .vb 7

Error 127 'Theme' is not a member of 'ASP.management_contentlist_aspx'. C:\inetpub\wwwroot\CMS\Management\ContentList.aspx 1
Error 128 'Title' is not a member of 'ASP.management_contentlist_aspx'. C:\inetpub\wwwroot\CMS\Management\ContentList.aspx 1
Error 129 'InitializeCulture' is not a member of 'ASP.management_contentlist_aspx'. C:\inetpub\wwwroot\CMS\Management\ContentList.aspx 1
My setup is as follows:
Windows XP Pro, IIS6, SQL Server 2005 Standard, VS2005 Professional.

I read another Message thread CMS - Can't Login where this problem was touched on but not really resolved. FYI I've downloaded the new DB and config files and updated the config file to reflect the SQL Standard connection as follows:

<connectionStrings>
     <add name="Cms"
         connectionString="Data Source=localhost\Development;
            Initial Catalog=CMS;
            User ID=CMSDevUser;
            password=password"
         providerName="System.Data.SqlClient" />
</connectionStrings>

This is the only change I've made to the config file.

Any help gratefully received.

Nick

OK.

Further development - some of the problems were caused by the fact that the classes for pages Default and Management\Default both had classes called _Default. Renamed the Management\Default class and errors down to 27. Begs the question why this doesn't affect everyone who's installed the CMS ?

Nick

Dans l'amour veritable c'est l'ame qui enveloppe le corps.

Aha. The rest of the errors were caused by exactly the same problem as above with regards the ContentList and Management\Contentlist.
So thanks to me for all my help:).

Still leaves the question of why everyone doesn't get the problem. Is it because I've got it running under IIS as opposed to Cassini ? Another mystery to add to life's rich tapestry.

Dans l'amour veritable c'est l'ame qui enveloppe le corps.

You can certainly say so. I have ran all of the apps from the book that I wrote both under Cassini and IIS, and never ran into this.

It's probably a good idea to give pages / classes unique names anyway, so had I know of this problem, I would certainly have called them differently...

Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.