Re: ASPNET: Master Files in subsidiary directories not published



Hi Mark,

The compilation I mentioned is the "precompilation" of ASP.NET 2.0. The
precompilation in ASP.NET 2.0 (can be set when publishing your site or use
aspnet_compiler.exe ) let you pre generate some of the aspx page(and other
dynamic compile stuffs) into assemblies so as to boost the runtime
performance. And there are different precompile models, therefore, I asked
you whether you've customize the precompile setting when publish your site.
Anyway, is it possible that you reproduce the problem through a very simple
project? If so, you may send it to me so that I can try some tests against
it on my side.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Newsgroups: microsoft.public.vsnet.general
Subject: Re: ASPNET: Master Files in subsidiary directories not published
Date: Thu, 17 Jan 2008 12:45:08 -0800

Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!tornado.f
astwebnet.it!tiscali!newsfeed1.ip.tiscali.net!newshub.sdsu.edu!border1.nntp.
dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!news.gigane
ws.com.POSTED!not-for-mail
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.vsnet.general:4109
X-Tomcat-NG: microsoft.public.vsnet.general

Steven,

Reply interleaved:

From your description, when you try publishing a VS 2008 website
application, it will not upload the master page in subdirectory to the
target location, correct?

Correct

As for the master page, have you used it in the project, also when you
publish the site, are you using partial precompile or full precompile
mode,
or whether you're publishing it to IIS or a local file folder?

Yes, it's used in the site -- that's how I found out that it hadn't been
uploaded, because the application crashed when a page using
the master was accessed.

I'm not sure what you're asking about compilation. The project is a web
application, so I think that means it's fully compiled when
published.


.



Relevant Pages

  • Re: Publishing Web Sites with VS 2005 - Lessons Learned
    ... takes 50 minutes to upload 409 files. ... So every page is slow the first time it is accessed. ... There is byte code compilation and JIT compilation. ... I have to precompile and upload the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Publishing Web Sites with VS 2005 - Lessons Learned
    ... so I understand the need to upload everything some times. ... So every page is slow the first time it is accessed. ... There is byte code compilation and JIT compilation. ... I have to precompile and upload the ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: Deploy VS 2005 / asp.net 2.0 application by hand copy / past over ftp
    ... application compilation model of ASP.NET 2.0/VS 2005 web application ... means we do not need to precompile any codebehind into assembly at ... Microsoft MSDN Online Support Lead ... response from the community or a Microsoft Support Engineer within 1 ...
    (microsoft.public.vsnet.general)
  • Re: Can i use VS .Net 2003 to develop w/ ASP.NET 2.0?
    ... ASP.NET MVP ... > cs, vb, etc files and it does all the compilation at runtime. ... > 2) You precompile everything. ... > all your ASPX, ASCX, ASAX, cs, vb, etc files. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Publishing Web Sites with VS 2005 - Lessons Learned
    ... I just use WS_FTP to upload the ddl and or affected aspx files etc, ... So every page is slow the first time it is accessed. ... There is byte code compilation and JIT compilation. ... I have to precompile and upload the ...
    (microsoft.public.dotnet.framework.aspnet)

Loading