2005 - Partial Classes

[Adrian Parker]

In 2003, we have a usercontrol that we reference as a type i.e. we can pass
the class around to functions to reference it. In 2005, the class is now
partial and doesn't seem to let you reference it as a type anymore, is there
a way around this ?

Thanks
Adrian

[Paul Glavich [MVP ASP.NET]]

Can you provide a code example?

I am not 100% sure I understand what you mean. Partial classes or not, the
end result is a referenceable type.

--
- Paul Glavich
MVP ASP.NET
http://weblogs.asp.net/pglavich
ASPInsiders member - http://www.aspinsiders.com
"Adrian Parker" <ap******@nospam.nospam> wrote in message
news:eV**************@tk2msftngp13.phx.gbl...

In 2003, we have a usercontrol that we reference as a type i.e. we can
pass the class around to functions to reference it. In 2005, the class is
now partial and doesn't seem to let you reference it as a type anymore, is
there a way around this ?

Thanks
Adrian

[Kevin Spencer]

I'm not sure what you're asking. What do you mean by "doesn't seem to let
you reference it as a type anymore?"

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Everybody picks their nose,
But some people are better at hiding it.

"Adrian Parker" <ap******@nospam.nospam> wrote in message
news:eV**************@tk2msftngp13.phx.gbl...

In 2003, we have a usercontrol that we reference as a type i.e. we can
pass the class around to functions to reference it. In 2005, the class is
now partial and doesn't seem to let you reference it as a type anymore, is
there a way around this ?

Thanks
Adrian

[Scott Allen]

On Thu, 4 Aug 2005 22:07:44 +1000, "Paul Glavich [MVP ASP.NET]"
<gl**@aspalliance.com-NOSPAM> wrote:

Can you provide a code example?

I am not 100% sure I understand what you mean. Partial classes or not, the
end result is a referenceable type.

Not for user controls, web forms, and master pages. We have to take
some extra steps to reference those types in 2.0.

--
Scott
http://www.OdeToCode.com/blogs/scott/

[Scott Allen]

It depends on where you try to reference the type from....

A user control (and it's code behind) will compile into a distinct
assembly that is not referenced by any other code in a web
application.

To put a reference in place from a web form you can use an @ Reference
directive, e.g. <%@ Reference VirtualPath="~/MyUserControl.ascx" %>.

If you need to interact with the user control from a class in App_Code
you'll have to create a stub class or an interface in App_Code and
derive your user control from the stub.

I've written some information about these types of scenarios in the
following:

One More On ASP.NET 2.0 Compilation
http://odetocode.com/Blogs/scott/arc...6/30/1889.aspx

Page Controllers and Stand-alone Code Migration
http://odetocode.com/Blogs/scott/arc...8/01/2030.aspx

Precompilation In ASP.NET 2.0
http://odetocode.com/Articles/417.aspx

When Deployment Gets Ugly
http://odetocode.com/Blogs/scott/arc...6/29/1882.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Thu, 4 Aug 2005 08:45:15 +0100, "Adrian Parker"
<ap******@nospam.nospam> wrote:

In 2003, we have a usercontrol that we reference as a type i.e. we can pass
the class around to functions to reference it. In 2005, the class is now
partial and doesn't seem to let you reference it as a type anymore, is there
a way around this ?

Thanks
Adrian

[Adrian Parker]

Ok, we just put our 2003 files in a new area and opened up the project, it
went through a conversion process. We have many user controls that call
other functions passing references to themselves. The other functions have
a parameter of the usercontrol class type. That no longer works.
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:eR*************@TK2MSFTNGP15.phx.gbl...

I'm not sure what you're asking. What do you mean by "doesn't seem to let
you reference it as a type anymore?"

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Everybody picks their nose,
But some people are better at hiding it.

"Adrian Parker" <ap******@nospam.nospam> wrote in message
news:eV**************@tk2msftngp13.phx.gbl...

In 2003, we have a usercontrol that we reference as a type i.e. we can
pass the class around to functions to reference it. In 2005, the class
is now partial and doesn't seem to let you reference it as a type
anymore, is there a way around this ?

Thanks
Adrian

[Adrian Parker]

Thanks for the links Scott,

I'm not looking forward to changing our app to make this work.. it seems
like a step backwards.
"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:cp********************************@4ax.com...

It depends on where you try to reference the type from....

A user control (and it's code behind) will compile into a distinct
assembly that is not referenced by any other code in a web
application.

To put a reference in place from a web form you can use an @ Reference
directive, e.g. <%@ Reference VirtualPath="~/MyUserControl.ascx" %>.

If you need to interact with the user control from a class in App_Code
you'll have to create a stub class or an interface in App_Code and
derive your user control from the stub.

I've written some information about these types of scenarios in the
following:

One More On ASP.NET 2.0 Compilation
http://odetocode.com/Blogs/scott/arc...6/30/1889.aspx

Page Controllers and Stand-alone Code Migration
http://odetocode.com/Blogs/scott/arc...8/01/2030.aspx

Precompilation In ASP.NET 2.0
http://odetocode.com/Articles/417.aspx

When Deployment Gets Ugly
http://odetocode.com/Blogs/scott/arc...6/29/1882.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Thu, 4 Aug 2005 08:45:15 +0100, "Adrian Parker"
<ap******@nospam.nospam> wrote:

In 2003, we have a usercontrol that we reference as a type i.e. we can
pass
the class around to functions to reference it. In 2005, the class is now
partial and doesn't seem to let you reference it as a type anymore, is
there
a way around this ?

Thanks
Adrian

[Scott Allen]

Sounds like you need the stub approach then.

The RTM version of 2005 should successfully migrate this code, but
like I say in the second link, you might be able to come up with an
eloquent solution on your own and decouple the controls from the
algorithms a bit.

I know it takes some work.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Thu, 4 Aug 2005 15:17:44 +0100, "Adrian Parker"
<ap******@nospam.nospam> wrote:

Thanks for the links Scott,

I'm not looking forward to changing our app to make this work.. it seems
like a step backwards.
"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:cp********************************@4ax.com.. .

It depends on where you try to reference the type from....

A user control (and it's code behind) will compile into a distinct
assembly that is not referenced by any other code in a web
application.

To put a reference in place from a web form you can use an @ Reference
directive, e.g. <%@ Reference VirtualPath="~/MyUserControl.ascx" %>.

If you need to interact with the user control from a class in App_Code
you'll have to create a stub class or an interface in App_Code and
derive your user control from the stub.

I've written some information about these types of scenarios in the
following:

One More On ASP.NET 2.0 Compilation
http://odetocode.com/Blogs/scott/arc...6/30/1889.aspx

Page Controllers and Stand-alone Code Migration
http://odetocode.com/Blogs/scott/arc...8/01/2030.aspx

Precompilation In ASP.NET 2.0
http://odetocode.com/Articles/417.aspx

When Deployment Gets Ugly
http://odetocode.com/Blogs/scott/arc...6/29/1882.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Thu, 4 Aug 2005 08:45:15 +0100, "Adrian Parker"
<ap******@nospam.nospam> wrote:

In 2003, we have a usercontrol that we reference as a type i.e. we can
pass
the class around to functions to reference it. In 2005, the class is now
partial and doesn't seem to let you reference it as a type anymore, is
there
a way around this ?

Thanks
Adrian