Manually Created Web Site Does Not Work - What am I Missing?

On my XP Pro dev box I have created an ASP.NET Web application using Visual
Studio 2008 pro. It works great. I then went to manually create a copy of
the Web site, with a different name, on the same machine. I did the
following, and the Web site fails to start with a 403 error, or a 404,
depending on the particular resource requested.

Here are the steps I have performed:
1. Created a new NTFS folder structure, with a \bin folder under the site's
root folder.

2. Copied all of the site's dll and ascx files into the folder structure,
with all of the dlls going into the bin folder, as in the VS project's
folder structure.
(note: there are zero aspx files in this site, as all pages requests are
served via custom http handler factory)

3. Set the NTFS permissions to be the same as those for the same project as
created under Visual Studio - including for the ASP.NET account.

4. Manually created the Web site (web application virtual directory) in IIS
(mmc snap-in), being careful to keep the permissions and capabilities the
same as those for the Web application virtual directory that Visual Studio
had created for the original project.

5. Ran aspnet_regiis -s on the new Web site... it ran to completion normally
(no error messages when it ran).

6. Restarted IIS (via MMC snap-in).

After all of the above, the site fails to start. In Global.Init, I write to
an Application event log... writing a brief message stating that the Web
site started. No such message appears in the event log. In my custom
override of Global.Init, I also have good exception handling that writes a
warning or error message to the event log. No such messsage appears. Also,
during my custom override of Global.Init, I have logic that connects to and
queries a local SQL Server database. As I monitor DB activity, the database
receives no attempts to connect from this particular ASP.NET Web
application.

So it's as if this thing isn't starting at all - at least not my custom
logic. If I create a really simple default.aspx file (with static html only
and no code-behind), then that is served to the browser just fine. But even
in these cases, nothing else works (as described above... no messages
written to the event log, so I know my custom Global.Init isn't running.

What could I be missing? What to do now? Thanks!




.

Relevant Pages

  • Re: Manually Created Web Site Does Not Work - What am I Missing?
    ... You can copy *those* files to any IIS server which has the corresponding ... only way some of the folders differ); created the Web site in IIS; and copied the underlying SQL Server ... The ASP.NET Dev Server runs as the Administrator account in VS 2008. ... I was hoping that my Web site would not need to have the same name or folder structure as my VS project. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Companyweb is not using .Net Framework 1.1.4322 (Sharepoint?)
    ... If you have to change companyweb to use ASP.Net v1.1.4322 then you will ... Take part in SBS ... Default Web Site 1.1x ... custom error settings for this application prevent the details of the ...
    (microsoft.public.windows.server.sbs)
  • Re: Manually Created Web Site Does Not Work - What am I Missing?
    ... The ASP.NET Dev Server runs as the Administrator account in VS 2008. ... I was hoping that my Web site would not need to have the same name or folder structure as my VS project. ... Copied all of the site's dll and ascx files into the folder structure, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Add Macro to Toolbar in Word 2007
    ... Graham Mayor - Word MVP ... Word MVP web site http://word.mvps.org ... I also have created some custom OL forms, ... macros to the QAT (Quick Access Toolbar) - near the bottom of the ...
    (microsoft.public.word.customization.menustoolbars)
  • Re: Manually Created Web Site Does Not Work - What am I Missing?
    ... folder structure as my VS project. ... Copied all of the site's dll and ascx files into the folder ... copy of the Web site, with a different name, on the same machine. ...
    (microsoft.public.dotnet.framework.aspnet)