AspDotNetAtoms.com provides daily updates on ASP.NET Tutorials, Programming Resources, .NET Articles, Authors and more.
Categories
Recent Posts
- Handling Files and Directories from your web applications. : Rockin J
Using C#, VB.NET, and ASP.NET to get all files of directory and subdirectory. Simply illustration of - Animated Popup Master/Detail using GridView, DetailsView and JQuery with jqModal & UpdatePanel : Muhammad Mosa
Demonstrate how to build master/details data presentation using GridView, DetailsView as animated pop - Understanding Script Injection Attacks : Sanjit Sil
This article helps to understand the concept of script injection attacks in detail using ASP.NET. Sanjit - Designing An Application Using Test Driven Development : Mohammad Azam
Application design is one of the most important aspects of creating the application. A design serves - Cross-Site Scripting in ASP.NET : SandeepReddy Pasham
Cross-site scripting attacks exploit vulnerabilities in Web page validation by injecting client-side
Search
ASP.NET Resources
Sharing Web Parts across multiple pages : Damon Armstrong
Saturday, July 12 2008
Most Web Parts implementations allow users to create a single portal page where they can personalize the look, feel, functionality, and experience of their "My Home" page in an application. But what if you want to take Web Parts a step further and allow users to define a personalized interface that applies to a series of pages in an application? Wouldn't it be useful if your users could place helpful tools and components on the periphery of your application and have those available on each page they visit instead of just on their "My Home" page? Absolutely! The question is how do you do it? At first glance, it may seem that Master Pages are the solution to the issue, but you will quickly run into a stumbling block: personalization settings for Web Parts are stored on a page-by-page basis. Even if you define all of the Web Part logic in a single Master Page, the Web Parts personalization settings for the pages that use the Master Page are stored separately from one another, preventing you from applying a single set of Web Parts to every page on the site....Pre-compiling the Site : Marco Bellinaso
ASP.NET MVC Tip #10 - Prevent URL Manipulation Attacks : Stephen Walther on ASP.NET MVC
ASP.NET Security [Part I] : Joydip Kanjilal
Executing async task in asp.net : Andrea Colaci
Updated: Implement Kerberos Delegation for Windows 2000 : ASP.NET Whitepapers