Visual Studio .NET 2005 using Web Application Project

  • Thread starter Thread starter Nathan Sokalski
  • Start date Start date
N

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 'myusercontrolclassname' 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 said:
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 'myusercontrolclassname' 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.
Click to expand...


try to read the tutorial in

http://webproject.scottgu.com/CSharp/Default.aspx

I follow the tutorial and I have no problem in converting 2003 project
to 2005 Web App project.
 
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
 
Thanks! That worked great, it must have saved me days of work and
frustration, I wish I had known about it before I spent the last couple days
trying to figure out how to use 2005's Website stuff. I was confused when
someone else told me about it, since I was scared when I saw the "Conversion
Wizard" window. But after I found out that the Conversion Wizard converts it
to a Web Application Project instead of a Visual Studio .NET 2005 Website
when you had the Web Application Project installed, I felt much more
confident. Thanks again.
 
Like I said before, that tutorial worked great, but there is one thing it
did not mention (or at least I did not notice it) that I am wondering how to
do. I noticed early on in my frustrations and attempts to find an answer
(before you showed me this one) that VB.NET 2005 used partial classes and
the *.aspx.vb file did not include the " Web Form Designer Generated Code "
region, which included the declarations for any controls used in the *.aspx
page. When I remove this region from my *.aspx.vb page, I recieve errors
saying:

Name 'mycontrolid' is not declared.

I am sure that this is simply because there are settings or something I need
to change or add that didn't get changed during the conversion to a Web
Application Project. Can anyone tell me what these might be? Thanks.
 
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/
 
Back
Top