Add Charset and ContentType to ASP.NET web page

The WC3 recommends specifying the Charset and ContentType on all of your web pages. A quick and easy way to do this in a ASP.NET web site with a master page is to add this to the masterpage file:


<%  Response.Charset = "utf-8"%> 
<%  Response.ContentType = "text/html"%>

Comments

Post a Comment

Popular posts from this blog

ToMethodObject Refactoring

Image
I love refactoring code. To refactor code safely you need automated tests. Some code, especially code not written using Test Driven Development(TDD), make it difficult to write tests for the part of the code you are looking to change. Usually what you face are a class that has many dependencies, so in your test setup, you have to create all these dependencies to inject into the constructor even though many or perhaps all of these dependencies don't even have anything to do with the part of the code you are looking to change. Or the method that you want to write a change for is private and the calling public method has a bunch of dependencies which again many will not have anything to do with the part of the code you are looking to change. You are thinking: "If only this code was in a public method it would be so much easier to test". But you may have heard somewhere that changing the code just to make it easier to test is bad.  This is a terrible line of thought that has ...
Read more

How to unlock a file in Team Foundation Server(TFS)

To unlock a file in Team Foundation Server you have to issue the following command at the Visual Studio Command Prompt: TF UNDO filename /WORKSPACE:workspace;checkout_user /SERVER:servername Where you change the lower case words with your particular case.  For more information go here: http://weblogs.asp.net/dmckinstry/archive/2006/07/09/Undo-_2F00_-Unlock-for-Others-with-Team-Foundation-Version-Control.aspx
Read more

Page.ClientScript.RegisterStartupScript not working

Had a website with a master page and in the the page_load event I was calling  Page.ClientScript.RegisterStartupScript to run some javascript based on the current state of the application. In the default.aspx page the script worked fine but in this other page the script was not getting called at all.   After much research I have learned that  Page.ClientScript.RegisterStartupScript only works if the page has a form element that has the  runat="server" set.  Once I added a form element with runat="server" to the other page the script finally started getting called the same as it did on the default.aspx page which of course had already had a form element.
Read more