Cannot get a handle on web UserControls in ASP 2.0

[Greg Smalter]

I'm converting some ASP web projects from VS 2003 to VS2005/ASP 2.0. The
worst problem I've run into is all references (in codebehind CS files) to
UserControls fail.

I get the error "The type or namespace 'MyUserControl' does not exist in the
namespace 'The.Correct.Na mespace' (are you missing an assembly reference?)"
even though the user control in question is named 'MyUserControl' and is
explicitly wrapped in the namespace block 'namespace The.Correct.Nam eSpace
{'. And, obviously, it worked in the previous framework so it's not a typo.

Is there an approach for overcoming this conversion issue?

Thank you.

Greg Smalter

[clintonG]

The verbiage in the page directive has changed in beta 2. This article [1]
may help. What bothers me is there does not appear to be a central location
where changes have been documented. This of course is FUBAR.

I'm going to post to MSDN Product Feedback [2] and ask for a centralized
page or blog that tracks changes and ask you to do the same

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee. com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

[1] http://west-wind.com/weblog/posts/2122.aspx
[2] http://lab.msdn.microsoft.com/Produc...k/Default.aspx

"Greg Smalter" <Gr*********@di scussions.micro soft.com> wrote in message
news:84******** *************** ***********@mic rosoft.com...

I'm converting some ASP web projects from VS 2003 to VS2005/ASP 2.0. The
worst problem I've run into is all references (in codebehind CS files) to
UserControls fail.

I get the error "The type or namespace 'MyUserControl' does not exist in
the
namespace 'The.Correct.Na mespace' (are you missing an assembly
reference?)"
even though the user control in question is named 'MyUserControl' and is
explicitly wrapped in the namespace block 'namespace The.Correct.Nam eSpace
{'. And, obviously, it worked in the previous framework so it's not a
typo.

Is there an approach for overcoming this conversion issue?

Thank you.

Greg Smalter

[Greg Smalter]

That explains a little about how the compilation models are different, but it
doesn't mention namespaces or how to address a transition. Good information
though, thanks.

I still need a way to make my existing ASP 1.1 framework web sites work in
ASP 2.0 by resolving this namespace issue and getting a handle on control
classes. It seems possible, because if I create a new web site and create a
control loose in the root, I can access it statically from the default page.
But if I create it in a folder, I can't. And there's no way for me to find
out what namespace it's using for the control in the folder, either. I need
to be able to statically access control classes no matter where they are,
like I used to.

Thank you.

Greg Smalter

"clintonG" wrote:

The verbiage in the page directive has changed in beta 2. This article [1]
may help. What bothers me is there does not appear to be a central location
where changes have been documented. This of course is FUBAR.

I'm going to post to MSDN Product Feedback [2] and ask for a centralized
page or blog that tracks changes and ask you to do the same

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee. com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

[1] http://west-wind.com/weblog/posts/2122.aspx
[2] http://lab.msdn.microsoft.com/Produc...k/Default.aspx

"Greg Smalter" <Gr*********@di scussions.micro soft.com> wrote in message
news:84******** *************** ***********@mic rosoft.com...

I'm converting some ASP web projects from VS 2003 to VS2005/ASP 2.0. The
worst problem I've run into is all references (in codebehind CS files) to
UserControls fail.

I get the error "The type or namespace 'MyUserControl' does not exist in
the
namespace 'The.Correct.Na mespace' (are you missing an assembly
reference?)"
even though the user control in question is named 'MyUserControl' and is
explicitly wrapped in the namespace block 'namespace The.Correct.Nam eSpace
{'. And, obviously, it worked in the previous framework so it's not a
typo.

Is there an approach for overcoming this conversion issue?

Thank you.

Greg Smalter

[Juan T. Llibre]

Clinton,

I think that what you're requesting was published
at MSDN in November 2004 :

http://msdn.microsoft.com/asp.net/wh...ta2update.aspx

The centralized page for ASP.NET Beta 2 information is at :

http://msdn.microsoft.com/asp.net/beta2/default.aspx

Bookmark it.

I go there at least weekly to get up to speed with changes/features.

Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"clintonG" <cs*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..

The verbiage in the page directive has changed in beta 2. This article [1] may help.
What bothers me is there does not appear to be a central location where changes have
been documented. This of course is FUBAR.

I'm going to post to MSDN Product Feedback [2] and ask for a centralized page or blog
that tracks changes and ask you to do the same

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee. com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

[1] http://west-wind.com/weblog/posts/2122.aspx
[2] http://lab.msdn.microsoft.com/Produc...k/Default.aspx

"Greg Smalter" <Gr*********@di scussions.micro soft.com> wrote in message
news:84******** *************** ***********@mic rosoft.com...

I'm converting some ASP web projects from VS 2003 to VS2005/ASP 2.0. The
worst problem I've run into is all references (in codebehind CS files) to
UserControls fail.

I get the error "The type or namespace 'MyUserControl' does not exist in the
namespace 'The.Correct.Na mespace' (are you missing an assembly reference?)"
even though the user control in question is named 'MyUserControl' and is
explicitly wrapped in the namespace block 'namespace The.Correct.Nam eSpace
{'. And, obviously, it worked in the previous framework so it's not a typo.

Is there an approach for overcoming this conversion issue?

Thank you.

Greg Smalter

[Greg Smalter]

The article basically mentions the changes necessary to the markup, which the
Visual Studio 2005 project upgrade utility has already done for me. It
doesn't mention namespaces at all. But it's a good article, thanks.

I'll try to describe the problem a little differently. I have a project in
which .cs files (not code-behind) existed in the same namespace as .ascx.cs
files (codebehinds for user controls). After upgrading to ASP 2.0, I have
access to the namespace, but only to the non-codebehind elements in it. None
of the classes that exist in codebehind files show up. It's as if they are
no longer part of the namespace, even though the namespace is explicitly
defined in those codebehind files (as was always the case in ASP 1.1).

I need a way to statically access classes and their static methods that
exist in user control codebehind files from other user control codebehind
files and from loose .cs code files, as was possible in ASP 1.1.

Thank you.

Greg Smalter.

"Juan T. Llibre" wrote:

Clinton,

I think that what you're requesting was published
at MSDN in November 2004 :

http://msdn.microsoft.com/asp.net/wh...ta2update.aspx

[Scott Allen]

Hi Greg:

Unfortunately, this scenario has gotten insanely complex in 2.0, at
least as of beta 2. The problem is not a namespace issue, but a "which
assembly to reference" issue because web "projects" are no longer
projects.

Each web form, and each user control can compile into a single
assembly - think of each web form and each user control as a separate
class library project. An island unto themselves.

These posts might shed some insight:
http://odetocode.com/Blogs/scott/arc...6/30/1889.aspx
http://odetocode.com/Blogs/scott/arc...6/29/1882.aspx

To establish assembly references between pages and user controls
you'll need an @ Reference directive with a VirtualPath attribute
pointing to the control you want to reference.

Getting to a user control from a loose .cs file, which I assume is in
App_Code, is a bit more difficult. You'll need to define a 'stub'
class in App_Code for the user control. That is a class that your
UserControl class will then inherit from - this is the only way to
access ASPX/ASCX code from App_Code. In post beta 2 the runtime will
generate stub classes for you.

All of this complexity exists for people who like to randomly drop
files into a web application and have it just work...

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Mon, 4 Jul 2005 05:12:01 -0700, Greg Smalter
<Gr*********@di scussions.micro soft.com> wrote:

The article basically mentions the changes necessary to the markup, which the
Visual Studio 2005 project upgrade utility has already done for me. It
doesn't mention namespaces at all. But it's a good article, thanks.

I'll try to describe the problem a little differently. I have a project in
which .cs files (not code-behind) existed in the same namespace as .ascx.cs
files (codebehinds for user controls). After upgrading to ASP 2.0, I have
access to the namespace, but only to the non-codebehind elements in it. None
of the classes that exist in codebehind files show up. It's as if they are
no longer part of the namespace, even though the namespace is explicitly
defined in those codebehind files (as was always the case in ASP 1.1).

I need a way to statically access classes and their static methods that
exist in user control codebehind files from other user control codebehind
files and from loose .cs code files, as was possible in ASP 1.1.

Thank you.

Greg Smalter.

"Juan T. Llibre" wrote:

Clinton,

I think that what you're requesting was published
at MSDN in November 2004 :

http://msdn.microsoft.com/asp.net/wh...ta2update.aspx

[Juan T. Llibre]

Hi, Greg.

re:

None of the classes that exist in codebehind files show up.
That's strange. They do show up for me.

In my vb source ( sorry for using VB, but it should work the same for C# )
I have the following :

Namespace ObjetoDatosVB
Public Class RegistrosSQL
etc...

When I open my aspx file to work on it, and place
<%@ Import Namespace="Obje toDatosVB" %>
at the top of my aspx, and then write

Dim RS as New

and hit the space bar, the available classes show up
and RegistrosSQL is available and is filled in by Intellisense.

Are your *.cs files in the App_Code directory ?

That's the only place where VS.NET Beta 2 will recognize them.


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"Greg Smalter" <Gr*********@di scussions.micro soft.com> wrote in message
news:3C******** *************** ***********@mic rosoft.com... The article basically mentions the changes necessary to the markup, which the
Visual Studio 2005 project upgrade utility has already done for me. It
doesn't mention namespaces at all. But it's a good article, thanks.

I'll try to describe the problem a little differently. I have a project in
which .cs files (not code-behind) existed in the same namespace as .ascx.cs
files (codebehinds for user controls). After upgrading to ASP 2.0, I have
access to the namespace, but only to the non-codebehind elements in it. None
of the classes that exist in codebehind files show up. It's as if they are
no longer part of the namespace, even though the namespace is explicitly
defined in those codebehind files (as was always the case in ASP 1.1).

I need a way to statically access classes and their static methods that
exist in user control codebehind files from other user control codebehind
files and from loose .cs code files, as was possible in ASP 1.1.

Thank you.

Greg Smalter.

"Juan T. Llibre" wrote:

Clinton,

I think that what you're requesting was published
at MSDN in November 2004 :

http://msdn.microsoft.com/asp.net/wh...ta2update.aspx

[Juan T. Llibre]

Hi, Scott.

re:
---000---
Getting to a user control from a loose .cs file, which I assume is in
App_Code, is a bit more difficult. You'll need to define a 'stub'
class in App_Code for the user control. That is a class that your
UserControl class will then inherit from - this is the only way to
access ASPX/ASCX code from App_Code.
---000---

I'll agree 100% with you if you limit the comments to ASCX code.

As explained in my previous reply, there's no problem in getting
Intellisense to recognize "standard" code-behind in class files,
as long as they are placed in the App_Code directory and the
Namespace is referenced with an Imports statement in the ASPX page.

I.O.W., accessing classes and their static methods that exist in user control
codebehind files needs the stubs or an @ Reference directive with a
VirtualPath attribute pointing to the control you want to reference,
as you well explain, but classes in "loose .cs code files" show up without
anything being required but placing them in the App_Code directory and
referencing the Namespace.


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"Scott Allen" <sc***@nospam.o detocode.com> wrote in message
news:1b******** *************** *********@4ax.c om...

Hi Greg:

Unfortunately, this scenario has gotten insanely complex in 2.0, at
least as of beta 2. The problem is not a namespace issue, but a "which
assembly to reference" issue because web "projects" are no longer
projects.

Each web form, and each user control can compile into a single
assembly - think of each web form and each user control as a separate
class library project. An island unto themselves.

These posts might shed some insight:
http://odetocode.com/Blogs/scott/arc...6/30/1889.aspx
http://odetocode.com/Blogs/scott/arc...6/29/1882.aspx

To establish assembly references between pages and user controls
you'll need an @ Reference directive with a VirtualPath attribute
pointing to the control you want to reference.

Getting to a user control from a loose .cs file, which I assume is in
App_Code, is a bit more difficult. You'll need to define a 'stub'
class in App_Code for the user control. That is a class that your
UserControl class will then inherit from - this is the only way to
access ASPX/ASCX code from App_Code. In post beta 2 the runtime will
generate stub classes for you.

All of this complexity exists for people who like to randomly drop
files into a web application and have it just work...

--
Scott
http://www.OdeToCode.com/blogs/scott/
On Mon, 4 Jul 2005 05:12:01 -0700, Greg Smalter
<Gr*********@di scussions.micro soft.com> wrote:

The article basically mentions the changes necessary to the markup, which the
Visual Studio 2005 project upgrade utility has already done for me. It
doesn't mention namespaces at all. But it's a good article, thanks.

I'll try to describe the problem a little differently. I have a project in
which .cs files (not code-behind) existed in the same namespace as .ascx.cs
files (codebehinds for user controls). After upgrading to ASP 2.0, I have
access to the namespace, but only to the non-codebehind elements in it. None
of the classes that exist in codebehind files show up. It's as if they are
no longer part of the namespace, even though the namespace is explicitly
defined in those codebehind files (as was always the case in ASP 1.1).

I need a way to statically access classes and their static methods that
exist in user control codebehind files from other user control codebehind
files and from loose .cs code files, as was possible in ASP 1.1.

Thank you.

Greg Smalter. "Juan T. Llibre" wrote:

Clinton,

I think that what you're requesting was published
at MSDN in November 2004 :

http://msdn.microsoft.com/asp.net/wh...ta2update.aspx

[Greg Smalter]

I think we're talking about opposite problems. You are illustrating that you
can access code files (non-codebehind) from an aspx page. My problem is that
I cannot access my aspx (or ascx) (codebehind) classes from a code file.

"Juan T. Llibre" wrote:

Hi, Greg.

re:

None of the classes that exist in codebehind files show up.

That's strange. They do show up for me.

In my vb source ( sorry for using VB, but it should work the same for C# )
I have the following :

Namespace ObjetoDatosVB
Public Class RegistrosSQL
etc...

When I open my aspx file to work on it, and place
<%@ Import Namespace="Obje toDatosVB" %>
at the top of my aspx, and then write

Dim RS as New

and hit the space bar, the available classes show up
and RegistrosSQL is available and is filled in by Intellisense.

Are your *.cs files in the App_Code directory ?

That's the only place where VS.NET Beta 2 will recognize them.

[Juan T. Llibre]

Ok...
It did sound a bit too simple of a problem... ;-)

Have you bugged that at the Feedback Center ?

http://lab.msdn.microsoft.com/produc...k/Default.aspx


Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======

"Greg Smalter" <Gr*********@di scussions.micro soft.com> wrote in message
news:A8******** *************** ***********@mic rosoft.com...

I think we're talking about opposite problems. You are illustrating that you
can access code files (non-codebehind) from an aspx page. My problem is that
I cannot access my aspx (or ascx) (codebehind) classes from a code file.

"Juan T. Llibre" wrote:

Hi, Greg.

re:

>None of the classes that exist in codebehind files show up.

That's strange. They do show up for me.

In my vb source ( sorry for using VB, but it should work the same for C# )
I have the following :

Namespace ObjetoDatosVB
Public Class RegistrosSQL
etc...

When I open my aspx file to work on it, and place
<%@ Import Namespace="Obje toDatosVB" %>
at the top of my aspx, and then write

Dim RS as New

and hit the space bar, the available classes show up
and RegistrosSQL is available and is filled in by Intellisense.

Are your *.cs files in the App_Code directory ?

That's the only place where VS.NET Beta 2 will recognize them.