• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 446
  • Last Modified:

asp.NET 4 Web Application Project - Master Page Not rendered after publishing to IIS 6

I have developed an asp.net v4 web application project in Visual Studio 2010 using a master page with 2 content holders.  The main page of the sight has 2 dropdowns in one contentholder and a formview control in the other, which display and edit information from an Access 2007 database.  When rendering the page on the local machine with the local .net development server the page displays and works as expected with the master page layout and the content.  When I publish the sight to our Windows 2003 R2/SP2 IIS 6 server with the .net framework 4 loaded and configured for the sight to use,  the main page will display and function correctly,, but the master page layout is not loaded into the page.  There is no error displayed, and I have tried creating a new aspx with some simple content with the master page and the same scenario, the page displays the master page content correctly on the local asp server but the not on the IIS server when published.  Any ideas how to correct or a suggested workaround?
0
allej0ly
Asked:
allej0ly
  • 3
1 Solution
 
allej0lyAuthor Commented:
Ok, I have resolved the issue....the styles.css file was not being copies to the IIS server when I published.  I manually copied the file and the master page is now being rendered as expected.  I wonder if this is the exptected behavior when publishing?
0
 
CodeCruiserCommented:
Is the CSS file "Linked" into the master page?
0
 
allej0lyAuthor Commented:
I had not markesd the css file to be copied with the project to the target
0
 
allej0lyAuthor Commented:
Thanks
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now