Deployement

[Prince]

I just did a search on Deployment from Jan. 1, 2003 to
Decmber 2003 and read each post to no avail. Here is my
problem. I don't know if the problem is on my side or
the websever host.

I created a web application using VS.NET. It's a very
basic app with database access in the Global.asax.cs
file. Within that file I open an Access database, read a
table and store it within the Application object which is
then used on one page.

On my local webserver, it works fine. No problem. So, I
registered a domain with .NET1.1 support and FTP the
files to their server. I'm using MyValueHost.com, by the
way so if any of you have dealt with them, please let me
know.

Problem
=========
After ftping the files there I get the following error
message when I access the home page, index.aspx.

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".

My web.config DOES have the line:
<customErrors mode="Off" />
so I don't know what the hell it's complaining about.

Anyway, why wouldn't this just work? I started reading
inside the documentation on deployment and the feeling I
get is that this is either a VERY simple thing to do or
more complicated than it should be.

On one hand, I read, you can just copy the files and
that's it. Then later I've read you have to create a
deployement Project and so on.

Damn, Microsoft, VS.NET should behave similar to Front
Page. There should be a way to just publish your site to
whatever webserver you wish and everything should be
handled automatically. .NET is by far the best but if
deploying is this complicated, sheeesh..

Is there something I'm missing? Do I have to create, God
forbid, a deployment project before ftping my files?

thanks,
Prince

 

[TJS]

look here under deployment

http://www.asp.net/Tutorials/quickstart.aspx



--
================================
http://www.ASPkey.net/
A Resource Site for Web Developers
*Free OnLine web Tools
*Free development services
================================

 

[Mark Fitzpatrick]

VS.Net DOES enable you to publish just like FrontPage. If you click on the
Copy Web icon above your list of items in the Solution Explorer (next to the
refresh icon) it will publish to a server with FrontPage Server Extensions.
It could be that the directory isn't marked as an application or something,
in that case it would explain why it might not be picking up settings in
your web.config file.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage

 

[Munsifali Rashid]

Try commenting out the authentication and sessionState sections in
web.config, to view remote errors. Some webhosting companies have problems
with displaying remote errors when these sections are specified.

Hope this helps,

Mun