While goining through code,saw this interesting stuff..basically used to specify the typename of a base class and its associated code-behind class. Check this on MSDN .
We have heard of Cross-Site Scripting attack....basically two types of cross site scripting is normally explained everywhere.. Non-Persistent CSS - which normally occurs when the input is directly echoed on the browser which causes the script in the input to execute. This script can steal the cookie using document.cookie and may post the values to attacker's site. Persistent CSS occurs when the input (from querystring, form variables) is stored in the database and later retrieved to display it on webpage causing the script to execute.
If we can use document.cookie so why not we use document object itself !! DOM based attack works on this principle..If our code uses document.url or document.location.href etc..these can be exploited using this technique.
In .NET, we can use requestValidate=True as page directive to prevent from such kind of attack. However this can also be bypassed, so also use HtmlEncode, UrlEncode to tightly filter input and write output urls. Also, a great library called IOSEC is available which goes further to filter malicious input.
For more info abt CSS:
http://www.webappsec.org/projects/articles/071105.shtml
http://crypto.stanford.edu/cs155/CSS.pdf
http://www.owasp.org/index.php/Category:OWASP_Project
This is my first post. Hope this place will be a great place to explore security!!
We can refer the 1.1 framework compiled dlls in Web applications developed in 2.0 without any extra effort. However we can not refer the 2.0 compiled dlls in 1.1 framework application the reason is well illustrated in the thread at ASP.NET Migration forum which says : using COM Interop it won't work because even if it uses COM for "interoperating" it still needs the .NET Framework to run. Since you cannot load 2 versions of the .NET Framework in the same process it will end up running against .NET 1.1 and fail.
However this thread says there is a workaround to refer 2.0 compiled dlls in 1.1 framework application using MSBuild ..!!
With the introduction of Master pages in 2.0, we can now design the page which contains contents repeated on each page -like menus, navigation, logos. We can also combine the functionality used by all web pages at single place and derive all our pages from this master page...
Here is an excellent article on master pages by Scott Allen - providing tips,tricks and traps.
Microsoft also provided 4 design templates based on the category. You can find them here.