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.
--
Nathan Sokalski
nj********@hotmail.com http://www.nathansokalski.com/
"Göran Andersson" <gu***@guffa.comwrote in message
news:OU*************@TK2MSFTNGP03.phx.gbl...
As far as I can tell, you only have to change Codebehind to CodeFile.
Nathan Sokalski wrote:
>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?