Excuse my ignorance, but I don't understand the Inherits= parameter that
gets stuffed into the @Page directive. I have several old asp sites that I
maintain using Visual Interdev 6.0. I want to start using Visual Studio.Net.
When I open a new project in Visual Studio.Net pointing to the existing site
(let's say "www.xxxxx.com") and create new aspx pages, I get an Inherits=
parameter in the @Page directive that looks like
'Inherits="www.xxxxx.com.webform1"'. If I create a new folder off the root
folder using Visual Studio.Net (let's say "test") then create a new Web Form
in that folder, I get an 'Inherits="www.xxxxx.com.test"' stuffed into the
@Page directive. The page cannot be delivered until I remove this parameter
but Visual Studio.Net keeps putting it back.
What is this and how do I adapt it to allow me to slowly convert to .Net on
existing sites?
Thanks. 5 1214
This is fundamental to the way that ASP.NET architecture works. In ASP.NET,
for each web page you have, you'll also have a "code-behind" page, which is
where you will actually write your VB code.
At run-time, when the user requests the .aspx page, it "locates" the correct
code-behind code using that inherits statement. The code in the code behind
is run and using the html in the .aspx page, a new class is created. This
class is written to temporary memory in IIS and it is this class that is
used for future page requests.
In short, the inherits directive is essential to the correct operation of
ASP.NET.
"Rick Lemons" <ri***@cdldata.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... Excuse my ignorance, but I don't understand the Inherits= parameter that gets stuffed into the @Page directive. I have several old asp sites that I maintain using Visual Interdev 6.0. I want to start using Visual
Studio.Net. When I open a new project in Visual Studio.Net pointing to the existing
site (let's say "www.xxxxx.com") and create new aspx pages, I get an Inherits= parameter in the @Page directive that looks like 'Inherits="www.xxxxx.com.webform1"'. If I create a new folder off the root folder using Visual Studio.Net (let's say "test") then create a new Web
Form in that folder, I get an 'Inherits="www.xxxxx.com.test"' stuffed into the @Page directive. The page cannot be delivered until I remove this
parameter but Visual Studio.Net keeps putting it back.
What is this and how do I adapt it to allow me to slowly convert to .Net
on existing sites?
Thanks.
Thanks. I understand the code-behind pages. What I don't understand is why
it generates a name in the Inherits= parameter of a page that doesn't even
exist. The code-behind parameter is OK and the Inherits= parameter is
supposed to be for the root page (or so I thought). But the name it places
in the Inherits= parameter doesn't exist anywhere and the compilation fails
unless I remove it.
"Scott M." <s-***@badspamsnet.net> wrote in message
news:e%***************@tk2msftngp13.phx.gbl... This is fundamental to the way that ASP.NET architecture works. In
ASP.NET, for each web page you have, you'll also have a "code-behind" page, which
is where you will actually write your VB code.
At run-time, when the user requests the .aspx page, it "locates" the
correct code-behind code using that inherits statement. The code in the code
behind is run and using the html in the .aspx page, a new class is created. This class is written to temporary memory in IIS and it is this class that is used for future page requests.
In short, the inherits directive is essential to the correct operation of ASP.NET.
"Rick Lemons" <ri***@cdldata.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... Excuse my ignorance, but I don't understand the Inherits= parameter that gets stuffed into the @Page directive. I have several old asp sites that
I maintain using Visual Interdev 6.0. I want to start using Visual Studio.Net. When I open a new project in Visual Studio.Net pointing to the existing site (let's say "www.xxxxx.com") and create new aspx pages, I get an
Inherits= parameter in the @Page directive that looks like 'Inherits="www.xxxxx.com.webform1"'. If I create a new folder off the
root folder using Visual Studio.Net (let's say "test") then create a new Web Form in that folder, I get an 'Inherits="www.xxxxx.com.test"' stuffed into
the @Page directive. The page cannot be delivered until I remove this parameter but Visual Studio.Net keeps putting it back.
What is this and how do I adapt it to allow me to slowly convert to .Net on existing sites?
Thanks.
The name listed after inherits is the name of the assembly and class
(assembly.class) defined in the code-behind page. This is how the .aspx
page knows what class within the assembly to make an instance of. You say
that removing it allows the project to compile. That doesn't sound right,
it just sounds like it was somehow corrupted and you've removed the entire
compilation of the class.
Have you tried deleting that page and creating a new page from scratch
(without modifying the inherits statement this time)?
"Rick Lemons" <ri***@cdldata.com> wrote in message
news:uY**************@tk2msftngp13.phx.gbl... Thanks. I understand the code-behind pages. What I don't understand is why it generates a name in the Inherits= parameter of a page that doesn't even exist. The code-behind parameter is OK and the Inherits= parameter is supposed to be for the root page (or so I thought). But the name it places in the Inherits= parameter doesn't exist anywhere and the compilation
fails unless I remove it.
"Scott M." <s-***@badspamsnet.net> wrote in message news:e%***************@tk2msftngp13.phx.gbl... This is fundamental to the way that ASP.NET architecture works. In ASP.NET, for each web page you have, you'll also have a "code-behind" page, which is where you will actually write your VB code.
At run-time, when the user requests the .aspx page, it "locates" the correct code-behind code using that inherits statement. The code in the code behind is run and using the html in the .aspx page, a new class is created.
This class is written to temporary memory in IIS and it is this class that is used for future page requests.
In short, the inherits directive is essential to the correct operation
of ASP.NET.
"Rick Lemons" <ri***@cdldata.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... Excuse my ignorance, but I don't understand the Inherits= parameter
that gets stuffed into the @Page directive. I have several old asp sites
that I maintain using Visual Interdev 6.0. I want to start using Visual Studio.Net. When I open a new project in Visual Studio.Net pointing to the
existing site (let's say "www.xxxxx.com") and create new aspx pages, I get an Inherits= parameter in the @Page directive that looks like 'Inherits="www.xxxxx.com.webform1"'. If I create a new folder off the root folder using Visual Studio.Net (let's say "test") then create a new
Web Form in that folder, I get an 'Inherits="www.xxxxx.com.test"' stuffed into the @Page directive. The page cannot be delivered until I remove this parameter but Visual Studio.Net keeps putting it back.
What is this and how do I adapt it to allow me to slowly convert to
..Net on existing sites?
Thanks.
You're right. I was not compiling the pages before accessing them from the
web site so the dll was not being created with the new class. Not used to
compiling code first. Never had to do that in the old ASP world.
Thanks.
"Scott M." <s-***@badspamsnet.net> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... The name listed after inherits is the name of the assembly and class (assembly.class) defined in the code-behind page. This is how the .aspx page knows what class within the assembly to make an instance of. You say that removing it allows the project to compile. That doesn't sound right, it just sounds like it was somehow corrupted and you've removed the entire compilation of the class.
Have you tried deleting that page and creating a new page from scratch (without modifying the inherits statement this time)?
"Rick Lemons" <ri***@cdldata.com> wrote in message news:uY**************@tk2msftngp13.phx.gbl... Thanks. I understand the code-behind pages. What I don't understand is
why it generates a name in the Inherits= parameter of a page that doesn't
even exist. The code-behind parameter is OK and the Inherits= parameter is supposed to be for the root page (or so I thought). But the name it
places in the Inherits= parameter doesn't exist anywhere and the compilation fails unless I remove it.
"Scott M." <s-***@badspamsnet.net> wrote in message news:e%***************@tk2msftngp13.phx.gbl... This is fundamental to the way that ASP.NET architecture works. In ASP.NET, for each web page you have, you'll also have a "code-behind" page,
which is where you will actually write your VB code.
At run-time, when the user requests the .aspx page, it "locates" the correct code-behind code using that inherits statement. The code in the code behind is run and using the html in the .aspx page, a new class is created. This class is written to temporary memory in IIS and it is this class that
is used for future page requests.
In short, the inherits directive is essential to the correct operation
of ASP.NET.
"Rick Lemons" <ri***@cdldata.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... > Excuse my ignorance, but I don't understand the Inherits= parameter that > gets stuffed into the @Page directive. I have several old asp sites that I > maintain using Visual Interdev 6.0. I want to start using Visual Studio.Net. > When I open a new project in Visual Studio.Net pointing to the existing site > (let's say "www.xxxxx.com") and create new aspx pages, I get an Inherits= > parameter in the @Page directive that looks like > 'Inherits="www.xxxxx.com.webform1"'. If I create a new folder off
the root > folder using Visual Studio.Net (let's say "test") then create a new Web Form > in that folder, I get an 'Inherits="www.xxxxx.com.test"' stuffed
into the > @Page directive. The page cannot be delivered until I remove this parameter > but Visual Studio.Net keeps putting it back. > > What is this and how do I adapt it to allow me to slowly convert to .Net on > existing sites? > > Thanks. > >
Yep. That's just one of the many new features of ASP.NET...Compiled Code!!
Yes!!! And that means, no more VBScript, now it's VB.NET.
"Rick Lemons" <ri***@cdldata.com> wrote in message
news:O9**************@TK2MSFTNGP12.phx.gbl... You're right. I was not compiling the pages before accessing them from the web site so the dll was not being created with the new class. Not used to compiling code first. Never had to do that in the old ASP world.
Thanks.
"Scott M." <s-***@badspamsnet.net> wrote in message news:%2****************@TK2MSFTNGP12.phx.gbl... The name listed after inherits is the name of the assembly and class (assembly.class) defined in the code-behind page. This is how the .aspx page knows what class within the assembly to make an instance of. You
say that removing it allows the project to compile. That doesn't sound
right, it just sounds like it was somehow corrupted and you've removed the
entire compilation of the class.
Have you tried deleting that page and creating a new page from scratch (without modifying the inherits statement this time)?
"Rick Lemons" <ri***@cdldata.com> wrote in message news:uY**************@tk2msftngp13.phx.gbl... Thanks. I understand the code-behind pages. What I don't understand is why it generates a name in the Inherits= parameter of a page that doesn't even exist. The code-behind parameter is OK and the Inherits= parameter is supposed to be for the root page (or so I thought). But the name it places in the Inherits= parameter doesn't exist anywhere and the compilation fails unless I remove it.
"Scott M." <s-***@badspamsnet.net> wrote in message news:e%***************@tk2msftngp13.phx.gbl... > This is fundamental to the way that ASP.NET architecture works. In ASP.NET, > for each web page you have, you'll also have a "code-behind" page, which is > where you will actually write your VB code. > > At run-time, when the user requests the .aspx page, it "locates" the correct > code-behind code using that inherits statement. The code in the
code behind > is run and using the html in the .aspx page, a new class is created. This > class is written to temporary memory in IIS and it is this class
that is > used for future page requests. > > In short, the inherits directive is essential to the correct
operation of > ASP.NET. > > > "Rick Lemons" <ri***@cdldata.com> wrote in message > news:%2****************@TK2MSFTNGP09.phx.gbl... > > Excuse my ignorance, but I don't understand the Inherits=
parameter that > > gets stuffed into the @Page directive. I have several old asp
sites that I > > maintain using Visual Interdev 6.0. I want to start using Visual > Studio.Net. > > When I open a new project in Visual Studio.Net pointing to the existing > site > > (let's say "www.xxxxx.com") and create new aspx pages, I get an Inherits= > > parameter in the @Page directive that looks like > > 'Inherits="www.xxxxx.com.webform1"'. If I create a new folder off the root > > folder using Visual Studio.Net (let's say "test") then create a
new Web > Form > > in that folder, I get an 'Inherits="www.xxxxx.com.test"' stuffed into the > > @Page directive. The page cannot be delivered until I remove this > parameter > > but Visual Studio.Net keeps putting it back. > > > > What is this and how do I adapt it to allow me to slowly convert
to .Net > on > > existing sites? > > > > Thanks. > > > > > >
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: mustafa |
last post by:
Dear sir ,
I have built my application in visual basic 6.0 and
crystal Report8.5 , Now i migrated my application to
VB.net using the upgrade wizard.My visual basic form is
upgraded to vb.net...
|
by: Armand Karlsen |
last post by:
I have a website ( http://www.zen62775.zen.co.uk ) that I made HTML 4.01
Transitional and CSS compliant, and I'm thinking of converting it into XHTML
to learn a little about it. Which XHTML variant...
|
by: prabha |
last post by:
Hello Everybody,
I have to conert the word doc to multiple html files,according to the templates in the word doc.
I had converted the word to xml.Also through Exsl ,had finished the multiple...
|
by: Robert |
last post by:
I have a series of web applications (configured as separate applications) on
a server.
There is a main application at the root and then several virtual directories
that are independant...
|
by: Mary |
last post by:
Hi,
Does anyone know of any software out there that would convert an application
written in VBScript to either VB.NET or C#/C++ quite quickly for me, or will
I have to re-write the application...
|
by: Map Reader |
last post by:
Greetings,
I am converting an old VB6 application to use .NET. One of the old controls
loads icons from the disk and displays them. However, the transparent color
turns to blue somewhere in the...
|
by: Frederik Vanderhaeghe |
last post by:
Hi,
I have a problem converting text to a double. Why doesn't the code work:
If Not (txtdocbedrag.Text = "") Then
Select Case ddlBedrag.SelectedIndex
Case 0
Case 1
|
by: Tor Aadnevik |
last post by:
Hi,
I have a problem converting values from Single to double.
eg. When the Single value 12.19 is converted to double, the result is
12.1899995803833.
Anyone know how to avoid this?
Regards...
|
by: gg9h0st |
last post by:
i'm a newbie studying php.
i was into array part on tutorial and it says
i'll get an array having keys that from member variable's name
by converting an object to array.
i guessed "i can...
|
by: shenanwei |
last post by:
DB2 V8.2 on AIX, type II index is created.
I see this from deadlock event monitor.
5) Deadlocked Connection ...
Participant no.: 2
Lock wait start time: 09/18/2006 23:04:09.911774
.........
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: ryjfgjl |
last post by:
In our work, we often need to import Excel data into databases (such as MySQL, SQL Server, Oracle) for data analysis and processing. Usually, we use database tools like Navicat or the Excel import...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
| |