Title: Hosting Your ASP.NET Assignments
1Hosting Your ASP.NET Assignments
- Minder Chen, Ph.D.
- George Mason University
- Fairfax, VA 22030
- mchen_at_gmu.edu
The Server is donated by Microsoft Special thanks
to Dr. Rajan Sen at Microsoft for securing the
fund for the purchase of the server.
2Install a FTP Client Software
- Get your WS_FTP Lite
- At ftp//mason.gmu.edu/support/www/ws_ftp/
3WS_FP client
- Use your first 4 characters of your last name as
your user name such as abou - Use as your password
4FTP Server
- In this example, the URL for the web application
is http//ebiz.gmu.edu/abou/
5(No Transcript)
6Testing Your Application over the Web
7Security of the file folder on the server
- Right-click on the application folder and ensure
ASPNET user account and if using Windows 2003 the
IIS_WPG account have Modify permissions.
8Security Set up on the Server
- After creating a new local Web site, you can
configure it to run ASP.NET pages and configure
security. The following table shows the
permissions settings that are available in all
versions of IIS, including IISÂ 6.0
Account or Group Permissions
Administrators Full Control
System Full Control
An account or group that you choose to give browse access to the site if you disabled anonymous authentication when you created the virtual directory. Read Execute
The account configured to access system resources for the ASP.NET current user context, such as the Network Service account (IISÂ 6.0) or the ASPNET account (IISÂ 5.0 and 5.1) or IIS_WGP (IIS 7.0 - Windows 2003) Read Execute List Folder Contents Read Write
9Web Application folder on the
- Web application folder on the Web server should
be a Web virtual directory under Internet IIS. - If you cover a web application folder (which
contain a web.config file) as a subfolder under
your remote web folder. It will not work. - The new subfolder needs to be created as a
virtual directory to make it work.
10Copy Web Site
- Click Website at the pull-down Menu
- Choose Copy Web Site
11Set up the Connection to the ftp server
12Set up the FTP Connection
13Active and Passive Mode
- Visual Web Developer can establish connections to
the FTP server in two modes active mode and
passive mode. In FTP, the client (in this case,
Visual Web Developer) and the server communicate
using two ports. One port is used to transmit
commands, and the other is used to transmit data. - Active FTP benefits the server administrator. In
active mode, the client initializes a connection
to the server for the command port and passes to
the server the port address for the data. The
server then initializes a connection back to the
client to open the data port. - Passive FTP benefits a client behind a firewall.
If the client is behind a firewall, the server's
attempt to open a port on the client computer
will likely fail. In passive mode, the client
initializes the connections for both the command
port and the data port. Because the client
initializes the connection for both ports, the
firewall allows the connections. - For more information, see Active FTP vs. Passive
FTP, a Definitive Explanation.
14Upload Multiple Files to the Remote Web Site
15(No Transcript)
16Check off the "Enable debugging"
17(No Transcript)
18(No Transcript)
19- Do you have your virtual directory set up
correctly and mapped to thecorrect dir in IIS? - Is your assembly in a bin folder in the
application root? - Have you built your assembly?
- Is it referencing a start up page? Are your
application pools running? - Is IIS running?
- Answering one of those questions will solve
yourproblem
20- I guess I'm still not clear on what you want to
do.  Do you wish to see the error messages in
detail so you can fix a problem? Do you wish to
supress all error messages? ltcustomErrors
mode"Off"/gt will allow you to see details about
the errorltcustomErrors mode"On"/gt will send
you to the defined page based on the error
code.  However, this requires you to define the
error code to page mapping in the config
file.ltcustomErrors mode"RemoteOnly"/gt will
perform just like "On" when you connect from a
remote machine (not localhost).  This is most
useful because you don't have to worry about
forgetting to change it when you deploy the app
but can still see the error details while
developing.
21- is the directory in which you saved your files
actually an IIS application?Otherwise there is a
confict between the web.config of your app and
that ofthe IIS application plus your binaries
won't be found.gt Either define that app as a
new IIS app or remove web.config and copyyour
dlls to the bin folder of the app root.
22(No Transcript)