I have a User Control called DialogControlPanel. The partial class for the user control is in the "Controls" namespace. The default namespace for the application is WOU.Apps.WebPortal, so the fully qualified name for the class is WOU.Apps.WebPortal.Controls.DialogControlPanel

I have a webform which contains this User control. The user control is registerd with ...

This registration is created automatically when I drag the user control onto the webform.

Everything is fine except the following... the desiger.vb file for the webform creates the following entry

This won't compile because I get a "Type Controls.DialogControlPanel is undefined" error. The webform exists in a separate namespace called "Forums". If I provide the fully qualified definition...

Protected WithEvents DialogControlPanel1 As WOU.Apps.WebPortal.Controls.DialogControlPanel,

then it compiles, however, whenever I make a change to the webform, the designer page is recreated and it once again has the unqualified name. Is this a bug in VS, or is there a way to specify that the designer should declare controls with fully-qualified namespaces?

Thanks,

Al

I'm not sure of an option to change the code generation.

Could you add an import/using for WOU.Apps.WebPortal so that the declared type will work?

I can always directly specify the fully-qualified name like so:

Protected WithEvents DialogControlPanel1 As WOU.Apps.WebPortal.Controls.DialogControlPanel

or include an Imports WOU.Apps.WebPortal statement. This will get it to compile.  However, the designer file gets overwritten every time the aspx page is changed, so making manual changes to it obviously won't work. The bottom line is, I don't know why the compiler doesn't recognize Controls.DialogControlPanel as a valid class if the application has a root namespace of WOU.Apps.WebPortal. I shouldn't have to declare this.

You can delete the declaration from the designer file and put it in the codebehind file.  Once moved to the codebehind file it will remain there unaltered -- even if you change the page.  This will allow you to work-around the issue.

There were some bugs related to VB that required us to generate the type differently than normal.  I'm not sure if that is the case here.  Can you post the @Control directive from your user control and the default namespace from your project settings?

Here it is...

<%@ Control Language="vb" AutoEventWireup="false" CodeBehind="DialogControlPanel.ascx.vb" Inherits="WOU.Apps.WebPortal.Controls.DialogControlPanel" %>

Web App default namespace is WOU.Apps.WebPortal

Partial Class for UserControl is called DialogControlPanel and is in namespace Controls

Web Page is in namespace Forums and imports the UserControl