CSS and Javascript not loading in Asp.Net WebSite and WebApplication

Today we came across a very strange and unique issue. The Asp.Net WebApplication has everything perfect and virtual directory and other configrations is perfect, but when we run the application, CSS and Javascript files were not included. The refrences and inlcude scripts were perfect and we cross checked everything. But in vain.

Finally, we found the following solution from this Blog
http://weblogs.asp.net/anasghanem/archive/2008/05/23/don-t-forget-to-check-quot-static-content-service-quot-in-iis7-installation.aspx?CommentPosted=true#commentmessage

The contents of this Blog are as follows

Don't forget to check "Static content service" in IIS7 installation
Before a couple of days ,I started to work on Vista and IIS 7, and since the default installation for Vista doesn't includes IIS7, I started by trying to install IIS 7.So I went to control panel, Programs and features, then to " turns windows features on or off",
After the dialog displayed , I navigate to application development features and checked asp.net and IIS management console, then I selected to install them , after the installation finishes , I prompted to restart the computer and i did. after i logged in a gain , and after i added an existing website to in IIS, i requested the website from the browser,then the problems started ,the browser displayed an empty page with no images , no scripts ... I tried to restart, reinstall with no luck , after many hours I find it ,

I didn't checked the "Static Content service" , look at the red Box in the Image below :

Note that the "static content" service is responsible for serving the Static contents like images, scripts , style sheets file, ....
In my opinion , if the user doesn't checked this option( which will be checked by default if you checked the " internet information service " root node ) windows vista must displays an alert or something , so that the user doesn't waste the time to know the problem ...
I have posted this problem and hoping to help some one in the future.

BTW: this problem still exists in windows 7 and window server 2008

Comments

Post a Comment

Popular posts from this blog

Export Data from AX 2012 - using DIXF (Data Migration Framework)

Importing is a well known task using DIXF, but at times we do need to export as well and then import it back in AX 2012. The export task can be done with the help of this information. https://technet.microsoft.com/en-us/library/dn144987.aspx Define the format of your source data Open  Data Import/Export Framework  >  Setup  >  Source data formats . Click  New , enter a name and a description, and then select  AX  from the  Type  list. Define a processing group to export data from Microsoft Dynamics AX Change the company to  CEU . In  Data Import/Export Framework , click  Common  >  Processing group , and then click  New  to create a new processing group. Set the group name to  Export-Cust  and add a description. Click  Entities  to select the entities to include in the processing group. In the  Select entities for processing group  form, click  New , and then, for an entity name, select  Customer . In the  Source data format  fiel
Read more

The virtual path maps to another application, which is not allowed

Image
During the development we came across this issue, which wasted a lot of our precious time. So I decided to share its solution with everyone. We have Project and Sub-Project Structure i.e. we have a root project and several sub-projects. The ROOT Project is entitled as TEMS8 and all other subprojects have been configured as per the image below. (Click on the image for large size) Now after setting up everything on a new Machine, we came across the Error as The virtual path maps to another application, which is not allowed Finally after investigation, we figured out that we have created multiple virtual directories which mainly causes the issue. For instance, we have another virtual directory created for DATADEF which is inside the virtual directory of TEMS8. So this was the main issue. The resolution was to remove the DATADEF Virtual Directory. Everything worked out perfectly, once we removed the inner virtual directory. We should not have something like this image below  W
Read more