This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 56.00000000000001%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
I've published and deployed a web site, but IIS doesn't display it correctly. None of the mark up is displayed in the browser, only comments and page title from my asp.net page. So, it resolves, but doesn't render everything. This is what it looks like.
I've run aspnet_regiis.exe, but it nothing changed. Any idea why the things below are the only ones displayed and what I need to do to display my content?
It sounds like you're encountering two main issues:
IIS Configuration
It appears your Internet Information Services (IIS) is not configured correctly, as it's returning source code instead of processing it. IIS should be set up to serve web pages, not display the underlying code.
ASP.NET MVC Usage
You seem to be working with an older version of ASP.NET Model-View-Controller (MVC), and it looks like you're trying to access a view directly. In MVC, you don't directly access views. Instead, you call a controller action, and that action then returns the appropriate HTML (view) to the browser.
To help you troubleshoot this, could you please provide more details about what you're trying to achieve and your experience level with web development and ASP.NET MVC? This will help us guide you more effectively.
Does your ASP.NET app work properly under your development environment using Visual Studio and IIS Express?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
it doesn't look like the IIS website is configured correctly as an asp.net application. check the the app pool for the website is using the correct runtime. also check that asp.net feature is enabled for IIS and the correct .net framework version is installed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 1%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJD%3C/text%3E%3C/svg%3E)
Hi kwoo,
Thank you for reaching out to Microsoft Q&A. I understand you're experiencing an issue where your deployed ASP.NET website is not displaying content correctly in the browser—only the page title and comments are visible, with no actual markup rendered.
Based on the information you've provided, I suspected that you're on a modern version of Windows with IIS 8 or later, where the aspnet_regiis.exe -i command is no longer supported for registering ASP.NET.
Run this in Command Prompt as Administrator:
dism /online /enable-feature /featurename:IIS-ASPNET45 /all
dism Stands for Deployment Image Servicing and Management — a command-line tool used to manage Windows features and packages.
/online Tells DISM to apply the changes to the currently running Windows installation (as opposed to an offline image).
/enable-feature Instructs DISM to enable a specific Windows feature.
/featurename:IIS-ASPNET45 Specifies the feature to enable: ASP.NET 4.5 support in IIS — this is required to run .aspx pages and ASP.NET Web Forms apps.
/all Ensures that all parent dependencies of the feature are also enabled automatically.
This command:
Installs ASP.NET 4.5 support in IIS. Ensures that your IIS server can correctly process .aspx pages. Fixes issues where IIS returns 404 or 500 errors due to missing ASP.NET handlers.
Once done, restart IIS:
iisreset
Then try accessing your aspx page again.
You can also check server logs: Review IIS logs (typically located in C disk -> inetpub ->logs->LogFiles) and Windows Event Viewer for errors related to ASP.NET or page loading.
Next Steps If the above steps do not resolve the issue, please provide the following details to assist further:
If you need further assistance, feel free to reach out. If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".