5

When I run either application itself or Azure deployment from Web, my pages are rendered using CSS, but when running the Web role under local fabric, I get plain "no-CSS" style pages.

I have two questions:

  • Anybody knows why does it happen?
  • What is a good way to debug similar issues?
Md Farid Uddin Kiron
  • 16,817
  • 3
  • 17
  • 43
Sergey Aldoukhov
  • 22,316
  • 18
  • 72
  • 99
  • Are you saying that your browser treats the pages differently based on where you are running from? I don't think so. – John Saunders Dec 22 '09 at 06:48
  • I do not know why it happens, because of browser or because of the differences in deployment, but the local fabric deployed pages are completely style-less – Sergey Aldoukhov Dec 22 '09 at 07:48

2 Answers2

10

alt text
(source: asp.net)

I had this problem and this solved it. Open up the Optional Features dialog and check off the option from the screenshot above. (You can get to Optional Features quickly by going to Start and typing optionalfeatures with no spaces.)

As the image is not avaiblable anymore: the following steps solved the problem for me:

  • Open "Active or deactivate Windows-Features"
  • Go to IIS, WWW-Services, Common Features
  • Activate "Static Content"
Glorfindel
  • 21,988
  • 13
  • 81
  • 109
zebra
  • 1,330
  • 1
  • 13
  • 26
  • Right on! Since dev fabric relies on IIS instead of ASP.Net development server, we ca see the difference. – Sergey Aldoukhov Jan 02 '10 at 21:10
  • I wish I could upvote this twice! I had actually checked the IIS 7 settings using IIS Admin and found that a StaticFile handler was installed, so I thought this wasn't the problem. But I didn't have it enabled in Optional Features. Enabled in Optional Features fixed the problem. – Paul Keister Sep 04 '10 at 19:28
0

Run HttpWatch, Firebug, or IE Developer Tools, refresh your page, and you'll quickly see where the problem lies. It's likely just a pathing issue.

Aaron
  • 475
  • 3
  • 14
  • This particular problem cannot be spotted by running any debugging tools, because what happens is that if Static Content is not checked, the server returns empty CSS and not an error. – Sergey Aldoukhov Jan 02 '10 at 21:58
  • 1
    It may not have solved it, but returning an empty css would still have provided a clue. – Aaron Jan 03 '10 at 17:33