J
Jonathan Wood
Okay, so forget about precompiling for now. I'll just FTP the files to my
site as this seems it will be trouble enough.
So, I see my web.config file has grown to well over 100 lines since
upgrading to VS2008. Now I need a web.config file for my site. I took the
existing one and changed the connection strings. Of course, it doesn't work
now. The error that appears is pasted below my signature.
My question is, how are we supposed to be dealing with this? Is it just
assumed that we will know what each and every line means that VS put there
and we'll know which lines to change, remove, and keep. Or is there actually
some sort of other method that can be used so my project will actually work?
Thanks.
--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Server Error in '/' 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".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
site as this seems it will be trouble enough.
So, I see my web.config file has grown to well over 100 lines since
upgrading to VS2008. Now I need a web.config file for my site. I took the
existing one and changed the connection strings. Of course, it doesn't work
now. The error that appears is pasted below my signature.
My question is, how are we supposed to be dealing with this? Is it just
assumed that we will know what each and every line means that VS put there
and we'll know which lines to change, remove, and keep. Or is there actually
some sort of other method that can be used so my project will actually work?
Thanks.
--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Server Error in '/' 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".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>