Menon Kalipurayath on .Net - Complete .Net Resource

Force non-www URLs to www URLs Umbraco CMS

Menon — Wed, 21 Dec 2011 10:25:23 +0000

You need to add: redirectMode=”Permanent”

Output Line Breaks in XSLT Umbraco

Menon — Wed, 24 Aug 2011 18:45:13 +0000

In the XSLT script, you can nicely formatted with each item on a separate line and indented use indent=”yes”, output will then be indent

eg:

indent=”yes” omit-xml-declaration=”yes” />

HttpResponse.RedirectPermanent in ASP.Net 4.0

Menon — Tue, 26 Apr 2011 09:31:47 +0000

If you want to redirect a page permanently to the new location, ASP.Net 4.0 introduces a new method ie, HttpResponse.RedirectPermanent

example:
Response.RedirectPermanent(“http://www.menonon.net/MyNewPage.aspx”);

Saving changes is not permitted. The changes you have made require the following tables to be dropped and re-created. SQL Server Management Studio 2008

Menon — Sun, 20 Mar 2011 14:46:29 +0000

Error Details:

Saving changes is not permitted. The changes you have made require the following tables to be dropped and re-created. You have either made changes to a table that can’t be re-created or enabled the option Prevent saving changes that require the table to be re-created.

You need to Disable “Prevent Saving Changes that requires the table re-creation”.

Open SQL Server Management Studio (SSMS) 2008
Click ‘Tools’ Menu
Then Click ‘Options’ as shown
In the navigation pane of the Options window, expand Designers node and select Table and Database Designers option as shown in the below snippet

Risks of Turing Off “Prevent Saving Changes that Require Table Re-creation” in SSMS
If you turn off this feature then you can avoid table recreation. However, if you have the Change Tracking feature of SQL Server 2008 enabled to track the table changes then the change tracking information will be lost completely whenever table is recreated. So, it is always advised to use this feature very carefully especially in a production environment.

a potentially dangerous request.form value was detected from the client

Menon — Sun, 13 Mar 2011 07:36:55 +0000

well, this is because your Page ValidationRequest is “True”, by default. you need to modify this in your web.config or on the page directive. You may have to set this like ValidationRequest=”False”

or in web.config under

If you’re using .Net 3.5 or .Net 4.0 you will have to modify web.config with the following or add requestValidationMode=”2.0″ in httphandlers section.

Hope this will help you to solve the issue.. please feel free to comment if you have any issues…