0

Hard to describe, but this is what is being served by IIS with an ASP.NET 4.0 MVC 2.0 setup. Does anybody have any idea as to why this is happening? It is happening locally for me as well as our staging environment on another server (making me think it's code based...). Let me know what other information would be helpful.

Cheers

alt text

1

Testing a bad ViewData element was causing the freak out. Still strange that it decided to do that instead of return an error message though...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.