Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / August 2006

Tip: Looking for answers? Try searching our database.

Removing the " Web Form Designer Generated Code " region after converting from ASP.NET 1.1 to ASP.NET 2.0

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Nathan Sokalski - 05 Jul 2006 04:24 GMT
I recently converted some ASP.NET 1.1 projects of mine, created with Visual
Studio .NET 2003, to Web Application Projects in Visual Studio .NET 2005 so
that I could use ASP.NET 2.0 (All my ASP.NET is done using VB.NET). After
converting, everything was fine, and worked and compiled correctly, but I
noticed one big difference between the VB.NET code of the converted files in
the projects and the VB.NET code in new pages. The new pages use partial
classes and do not have the " Web Form Designer Generated Code " region
where the controls were declared. When I try to modify the code in the
converted files to be like this, I recieve the following error:

Name 'mycontrolid' is not declared.

I am sure this is simply because I am not doing something or I am doing
something wrong, but I cannot figure out what. Any ideas? Thanks.
Signature

Nathan Sokalski
njsokalski@hotmail.com
http://www.nathansokalski.com/

Göran Andersson - 05 Jul 2006 07:01 GMT
The separation of markup and code changed from "code-behind" in VS 2003
to "code-beside" in VS 2005. The @Page directive contains different
properties in the new model.

> I recently converted some ASP.NET 1.1 projects of mine, created with Visual
> Studio .NET 2003, to Web Application Projects in Visual Studio .NET 2005 so
[quoted text clipped - 10 lines]
> I am sure this is simply because I am not doing something or I am doing
> something wrong, but I cannot figure out what. Any ideas? Thanks.
Nathan Sokalski - 05 Jul 2006 21:32 GMT
That's great, but it still doesn't help me know what I should change my code
to. Here is my current @Page directive and Class definition from my
TextFiles.aspx and TextFiles.aspx.vb files:

<%@ Page Language="vb" AutoEventWireup="false"
Codebehind="TextFiles.aspx.vb" Inherits="WebApplication1.TextFiles"
enableViewState="False"%>

Public Class TextFiles

What changes do I need to make to this?
Signature

Nathan Sokalski
njsokalski@hotmail.com
http://www.nathansokalski.com/

> The separation of markup and code changed from "code-behind" in VS 2003 to
> "code-beside" in VS 2005. The @Page directive contains different
[quoted text clipped - 15 lines]
>> I am sure this is simply because I am not doing something or I am doing
>> something wrong, but I cannot figure out what. Any ideas? Thanks.
Göran Andersson - 06 Jul 2006 00:18 GMT
As far as I can tell, you only have to change Codebehind to CodeFile.

> That's great, but it still doesn't help me know what I should change my code
> to. Here is my current @Page directive and Class definition from my
[quoted text clipped - 7 lines]
>
> What changes do I need to make to this?
Nathan Sokalski - 06 Jul 2006 03:56 GMT
That makes sense, but here are several comments I have about that:

1. When I create a new WebForm it still uses Codebehind. I don't know if
this has something to do with the fact that I am using the Visual Studio
.NET 2005 Web Application Project model instead of the Visual Studio .NET
2005 Website model.

2. If I do change Codebehind to CodeFile I recieve an error saying
'TextFiles' is ambiguous in the namespace 'WebApplication1'.

3. I tried creating one of my simple WebForms from scratch (deleting the
*.aspx and *.aspx.vb files and recreating it using the same controls and vb
code). It compiled and worked with no errors, but when I modify all the
lines of code in other WebForms to look the same (the @Page directive and
!DOCTYPE tag in the *.aspx file and add the Partial keyword to the class
definition in the *.aspx.vb file), it does not work. Is there some
configuration file that gets modified when you create a new WebForm by going
to Add->New Item?

I am not sure why, but simply modifying the *.aspx and *.aspx.vb files of a
WebForm won't let me get rid of the "Web Form Designer Generated Code "
region that used to get added by Visual Studio .NET 2003. If anyone has any
ideas, I would appreciate them.
Signature

Nathan Sokalski
njsokalski@hotmail.com
http://www.nathansokalski.com/

> As far as I can tell, you only have to change Codebehind to CodeFile.
>
[quoted text clipped - 9 lines]
>>
>> What changes do I need to make to this?
Dune - 28 Aug 2006 22:51 GMT
Hi there,

I'm having the exact same problem.

Just wondering if you ever found a resolution or workaround in the end?

Cheers

> That makes sense, but here are several comments I have about that:
>
[quoted text clipped - 32 lines]
> >>
> >> What changes do I need to make to this?
Nathan Sokalski - 29 Aug 2006 01:28 GMT
What I discovered is that ASP.NET 2.0 organizes the code slightly
differently. The control declarations created by the designer are now put in
a file with the extension *.aspx.designer.vb or *.ascx.designer.vb. If you
want to copy and paste the declarations from ASP.NET 1.1 code into one of
these files, I would suggest that you create one file from scratch so that
you can see what the file looks like, the file layout is very basic. Good
Luck!
Signature

Nathan Sokalski
njsokalski@hotmail.com
http://www.nathansokalski.com/

> Hi there,
>
[quoted text clipped - 47 lines]
>> >>
>> >> What changes do I need to make to this?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.