DisplayDirection not liked

member4953 · March 30th, 2009, 03:06 PM

On page 281, when I change from this line:

Code:

<Wrox:Banner ID="Banner1" runat="server" />

to this line

Code:

<Wrox:Banner ID="Banner1" runat="server" DisplayDirection="Horizontal" />

I get this error in the browser

Compiler Error Message: CS1061: 'System.ComponentModel.ISite' does not contain a definition for 'Classes' and no extension method 'Classes' accepting a first argument of type 'System.ComponentModel.ISite' could be found (are you missing a using directive or an assembly reference?)

I have my Direction.cs file in the directory Site.Classes.

Intellisense seems to know about DisplayDirection as it offers it as a property as well as the two values.

I am using C# and have included "using Site.Classes;" in MasterPage.Master.cs and Banner.ascx.cs.

If I simply remove the DisplayDirection="Horizontal" from the control declaration in the MasterPage.Master the image will display in the browser horizontally.

I am missing something but cannot see it.

Thomas

Imar · March 30th, 2009, 03:46 PM

>> have my Direction.cs file in the directory Site.Classes.

You keep referring to namespaces as folders., which is a bit confusing. Is it in the Site.Classes namespace, or do you have a folder called Site.Classes?

Also, is the DisplayDirection type recognized in the Code Behind of the User Control? I just ran a quick test in a Web Application Project and it works fine. o, few things to check:

1. namespace for the Enum

2. using statement in the UC to bring the enum in scope

3. @Register tag in the page using the UC

Also, make sure you don't have any compile errors in your site before you try this out.

Finally, I don't think that Site is a very good root namespace. Each page has a Site property that is used for design time purposes. Maybe that's causing the problem. Usually, I avoid these problems by using something like CompanyName.ProjectName.Layer as the root namespace. E.g. SomeCompany.CorporateSite.Web for a web project.

Cheers,

Imar

member4953 · March 30th, 2009, 04:00 PM

Imar,

The top of my WAP solution is "Site". There is a folder under that called "Classes". Therein is "Direction.cs".

Within "Direction.cs" is the following:

Code:

namespace Site.Classes
{
    public enum Direction
    {
        Horizontal,
        Vertical
    }
}

Once I added "using Site.Classes" the the Code Behind for the User Control the type for "DisplayDirection" was recognized (the font changed to turquoise).

I have the "using Site.Classes;" statement in the User Control's code behind file.

I had in the previous "Try It Out" removed the "@ Register" from the Master page. The previous "Try It Out" worked as advertised.

There are no compile errors when I compile by keying F6.

I now understand that using "Site" was a poor choice. Everything has worked so far and I think changing it is a big deal.

Thanks.

Thomas

Imar · March 30th, 2009, 04:05 PM

>> Everything has worked so far and I think changing it is a big deal.

Is it? A simple Find and Replace action should do the trick...

>> Once I added "using Site.Classes" the the Code Behind for the User Control the type for "DisplayDirection" was recognized

So is it working now?

Imar

member4953 · March 30th, 2009, 04:22 PM

Quote:

Originally Posted by Imar

>> Once I added "using Site.Classes" the the Code Behind for the User Control the type for "DisplayDirection" was recognized

So is it working now?

Imar

No. I have the using statement in the UC before I wrote the note. It works with

Code:

<Wrox:Banner ID="Banner1" runat="server" />

In MasterPage.Master, but not with

Code:

<Wrox:Banner ID="Banner1" runat="server" DisplayDirection="Horizontal" />

even though when I added "DisplayDirection" to the declaration Intellisense knew of it and aided it adding it.

Thomas

Imar · March 30th, 2009, 04:27 PM

It might still be the Site problem. Have you tried renaming the namespace?

One way to test out how it's supposed to work (which is what I did) is to create a brand new WAP. Add the Enum, the UC and a page and you can see how things are supposed to work. Then you can "reverse engineer" your code and find the issue in your site.

Alternatively, you can send me a zipped version of the entire solution and I'll take a look.

Cheers,

Imar

member4953 · March 30th, 2009, 04:35 PM

I will send you a zipped file of the solution and try the new, small WAP.

What is your e-mail address? I do not think I can send a file through the forum, can I?

Thomas

member4953 · March 31st, 2009, 10:23 AM

Imar,

I can make this work if I dispense with the separate "Direction.cs" file in the "Site.Classes" namespace. Rather I created an Int32 with the name "DisplayDirection" in the "Banner.ascx.cs" file, and used the values of 0 and 1.

Interestingly, when I put the enum Direction in the "Banner.ascx.cs" file, before the "public partial class Banner : System.Web.UI.UserControl", but within the "namespace Site.Controls" I get the same old error. It is as if VS simply does not see the enum statement. The error now complains "Compiler Error Message: CS1061: 'System.ComponentModel.ISite' does not contain a definition for 'Controls' and no extension method 'Controls' accepting a first argument of type 'System.ComponentModel.ISite' could be found (are you missing a using directive or an assembly reference?)". Note its reference to "Controls".

I'd like to understand this since I know it will come up again in a project in the future.

Thanks.

Thomas

Imar · March 31st, 2009, 03:21 PM

Hi Thomas,

I renamed (site wide) the Site namespace to TestProject and everything worked fine.

Like I hinted earlier, Site is a more or less reserved word as the Page class has a Site property. Apparently, it has trouble keeping the two apart.

Cheers,

Imar

member4953 · March 31st, 2009, 04:28 PM

Well I'll be danged! I just completely missed that in trying to interpret the error message. I changed it here and it worked immediately.

Thanks for your patience, Imar.

Thomas

Quote:

Originally Posted by Imar

Hi Thomas,

I renamed (site wide) the Site namespace to TestProject and everything worked fine.

Like I hinted earlier, Site is a more or less reserved word as the Page class has a Site property. Apparently, it has trouble keeping the two apart.

Cheers,

Imar