Visual Studio .NET 2005 using Web Application Project

[Nathan Sokalski]

Because I wanted the builds for my ASP.NET sites to be a single *.dll in a
/bin/ directory (like VSNET 2003), I decided to try the Web Application
Project download. However, I am still pulling my hair out because it doesn't
want to recognize any of the Controls (not even the ones that are part of
ASP.NET). All of the Controls show the following error:

Name 'mycontrolid' is not declared.

And my UserControls show the following error (all my UserControls are in the
same directory as my Pages and I do have them registered with the register
directive):

Element 'myusercontrolc lassname' is not a known element. This can occur if
there is a compilation error in the Web site.

Can anybody help me find an easy way to move my 2003 ASP.NET code to Visual
Studio .NET 2005 and be able to have a single *.dll generated? Thanks.
--
Nathan Sokalski
nj********@hotm ail.com
http://www.nathansokalski.com/

[Cor Ligthert [MVP]]

Nathan,

That way of using ASPNET creates more code pages than the website style did
you got those.

There has to be as well a pages as

Mypage.designer .vb

In that are your controls declared in a kind of global way to the page.

Cor

"Nathan Sokalski" <nj********@hot mail.comschreef in bericht
news:%2******** *******@TK2MSFT NGP03.phx.gbl.. .

Because I wanted the builds for my ASP.NET sites to be a single *.dll in a
/bin/ directory (like VSNET 2003), I decided to try the Web Application
Project download. However, I am still pulling my hair out because it
doesn't want to recognize any of the Controls (not even the ones that are
part of ASP.NET). All of the Controls show the following error:

Name 'mycontrolid' is not declared.

And my UserControls show the following error (all my UserControls are in
the same directory as my Pages and I do have them registered with the
register directive):

Element 'myusercontrolc lassname' is not a known element. This can occur if
there is a compilation error in the Web site.

Can anybody help me find an easy way to move my 2003 ASP.NET code to
Visual Studio .NET 2005 and be able to have a single *.dll generated?
Thanks.
--
Nathan Sokalski
nj********@hotm ail.com
http://www.nathansokalski.com/

[Rick Strahl]

Do you see the .designer.cs or .vb file for your Page class? Make sure that
exists and that the control definition you are trying to access exists
inside of the file.

If you ported your application from a stock project, make sure you Convert
to Web Application first as this will convert a standard page to a WAP page
with the required designer files. VS2005 from then on should update that
..designer.cs file when you make a change. In my experience this isn't 100%
reliable unless you go into the visual designer and save - making changes in
the HTML source view often doesn't update the .designer file.

Hope this helps,

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/weblog
http://www.west-wind.com/wwThreads/
"Nathan Sokalski" <nj********@hot mail.comwrote in message
news:%2******** *******@TK2MSFT NGP03.phx.gbl.. .

Because I wanted the builds for my ASP.NET sites to be a single *.dll in a
/bin/ directory (like VSNET 2003), I decided to try the Web Application
Project download. However, I am still pulling my hair out because it
doesn't want to recognize any of the Controls (not even the ones that are
part of ASP.NET). All of the Controls show the following error:

Name 'mycontrolid' is not declared.

And my UserControls show the following error (all my UserControls are in
the same directory as my Pages and I do have them registered with the
register directive):

Element 'myusercontrolc lassname' is not a known element. This can occur if
there is a compilation error in the Web site.

Can anybody help me find an easy way to move my 2003 ASP.NET code to
Visual Studio .NET 2005 and be able to have a single *.dll generated?
Thanks.
--
Nathan Sokalski
nj********@hotm ail.com
http://www.nathansokalski.com/