This is really a quick note more than anything. I've had peers many times ask me to lend my eyes to a problem they've had when testing some web code. Typically, the code works on the server but not on the local machine.
Without fail, 99% of the time the problem is the developer is running the ASP.NET Development Server (Cassini) on the local machine rather than running the application through IIS.
The built-in web server for ASP.NET is ok for simple things; like does a page display correctly, but lousy for testing full features of your application.
Namely, here a few things that don't work using the ASP.NET web server. Keep in mind, I haven't tried these things in VS2010 so I'm not sure if its still an issue or not...
1. doesn't except any connections from remote machines (localhost only, so you can't have peers look at your work)
2. Server.MapPath doesn't work
3. Some File IO operations don't wory
4. IIS security type things don't work
5.Can't run non-ASP.NET pages (IE, no classic ASP and other types of scripting)
6. SSL may not work (haven't tried it)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment