"sling blade" <sc******@hotma il.com> confessed in
news:11******** **************@ o13g2000cwo.goo glegroups.com:
I have left only the first page of my app on the server and they are
index.aspx, index.aspx.resx and index.vb. (Just to keep the directory
as clean as I could while I try to figure this out)
OK. Your use of the term confused me, as it means something entirely
different with databases.
The file you need on your web site is index.aspx. The .vb and the .resx
files are used in building the .dll and their content is included therein.
If you want only the necessary files for the web, then you don't need these
sources (unless you plan to debug against the server).
You'll need the identical structure on the server that you have on your
workstation. (Of course, you'll need the proper configuration in the IIS
metabase for a website, which is usually done with the IIS administration
MMC file, iis.msc).
You need a bin directory off root where your project.dll is to reside.
You need the web.config file in the root directory, as well as the
global.asax file.
You may also need an aspnet_client directory that contains scripts for js
implementation of downversion clientside web controls.
People generally keep images in a separate img or image directory.
Sometimes they keep other stuff out of the root folder too, to hide content
from search engine robots, or for other purposes.
If your deployment doesn't work, take a look in the web log to see what the
server thinks it needs.
Remember that .net is a managed system, and requires many system components
in place, as well as the proper ACLs in apropriate directories that allow
access to your web application security identity. If the system admin did
his job correctly, then deployment is a snap.
Are their other web applications running on this server? If this is the
first and only, then you might be having problems left over from the
framework install.
Good luck.
-- ipgrunt
