J
Jerry Tovar
I am using .Net 2003 on a XPPro running IIS.
I am unable to view any of my ASPX webforms in a browser
unless I modify the .ASPX file
and replace Codebehind="employee.aspx.cs" with
src="employee.aspx.cs".
It looks like my bin/employee.dll file is not being used.
Instead, my employee.aspx.cs file
is being used.
Why is my .dll file being ignored?
These problems are happening on all of my ASP.Net
webforms.
Here's what I tried to get my webforms working. #1
should work but doesn't #2 works but why?
Also, the following is true if I try to place my forms
into production or attempt to view
them in development.
1 I created a new virtual directory and placed my
employee.aspx and web.config and bin/employee.dll
files into the virtual directory. I then tried to view
employee.aspx in a browser but get the
Server Error message below.
2 I then copied my employee.aspx.CS file to the virtual
directory and changed the employee.aspx
line: Codebehind="employee.aspx.cs" to
src="employee.aspx.cs". I then tried to view my
..aspx page in a browser and now everything works! It
doesn't even matter if my employee.dll file
is in the virtual directory root or bin/. I can even
delete my .dll file and the page still
works as long as the .aspx.cs file is in the root. Also,
the src="employee.aspx.cs" has to be
there otherwise I get a Parser Error message.
What does this mean? How can I get my Asp.net
applications to work normally without the need for
the src= in the .aspx file?
Any ideas?
Thanks,
Jerry
----------------------------------------------------------
----------------------
Server Error in '/test1' Application.
----------------------------------------------------------
----------------------
Runtime Error
Description: An application error occurred on the server.
The current custom
error settings for this application prevent the details
of the application error
from being viewed remotely (for security reasons). It
could, however, be viewed
by browsers running on the local server machine.
Details: To enable the details of this specific error
message to be viewable on
remote machines, please create a <customErrors> tag
within a "web.config" configuration
file located in the root directory of the current web
application. This <customErrors>
tag should then have its "mode" attribute set to "Off".
I am unable to view any of my ASPX webforms in a browser
unless I modify the .ASPX file
and replace Codebehind="employee.aspx.cs" with
src="employee.aspx.cs".
It looks like my bin/employee.dll file is not being used.
Instead, my employee.aspx.cs file
is being used.
Why is my .dll file being ignored?
These problems are happening on all of my ASP.Net
webforms.
Here's what I tried to get my webforms working. #1
should work but doesn't #2 works but why?
Also, the following is true if I try to place my forms
into production or attempt to view
them in development.
1 I created a new virtual directory and placed my
employee.aspx and web.config and bin/employee.dll
files into the virtual directory. I then tried to view
employee.aspx in a browser but get the
Server Error message below.
2 I then copied my employee.aspx.CS file to the virtual
directory and changed the employee.aspx
line: Codebehind="employee.aspx.cs" to
src="employee.aspx.cs". I then tried to view my
..aspx page in a browser and now everything works! It
doesn't even matter if my employee.dll file
is in the virtual directory root or bin/. I can even
delete my .dll file and the page still
works as long as the .aspx.cs file is in the root. Also,
the src="employee.aspx.cs" has to be
there otherwise I get a Parser Error message.
What does this mean? How can I get my Asp.net
applications to work normally without the need for
the src= in the .aspx file?
Any ideas?
Thanks,
Jerry
----------------------------------------------------------
----------------------
Server Error in '/test1' Application.
----------------------------------------------------------
----------------------
Runtime Error
Description: An application error occurred on the server.
The current custom
error settings for this application prevent the details
of the application error
from being viewed remotely (for security reasons). It
could, however, be viewed
by browsers running on the local server machine.
Details: To enable the details of this specific error
message to be viewable on
remote machines, please create a <customErrors> tag
within a "web.config" configuration
file located in the root directory of the current web
application. This <customErrors>
tag should then have its "mode" attribute set to "Off".