February 2008 Entries

Using Nested Master Page in ASP.NET

Master page made the developers life extremely easy where all of the core design (specially headers, footers etc) can be designed and defined in one page which then can be inherited by all the pages in the application without requiring adding the header, footers etc explicitly. However master pages can also be nested, that is in a application, where are there two (or more) set of designs to be followed in two or more set of pages, along with following some common design components (such as header, ...
Print | posted on Posted On Monday, February 18, 2008 5:47 PM | Comments (4)

Using .NET 2.0 Generics for Custom Entity Collection

Generics is a new feature in .NET 2.0 which allows us to create a data structure without committing to a specific data type. In the early age of .net 2.0 (i.e. .net 1.x), while using custom entity model in our application data architecture, we had to create a separate class regarding the collection for each of custom entity. The custom entity public class SystemUser { public string _Name, _Password; public SystemUser(string name, string password) { _Name = name; _Password = password; } public string ...
Print | posted on Posted On Monday, February 18, 2008 5:12 PM | Comments (1)

ASP.NET Role Based Security: The Basics

Authentication and authorization is the two basic part of the user-end security in asp.net web applications. After to successful authentication of a user, authorization takes the place according to which the authenticated user are allowed to access to the corresponding resources in the web application. Role based security is very basic requirements in the current trend of web applications. Mostly there are two roles involved, which are registered user and the admin users. However in a web application ...
Print | posted on Posted On Monday, February 18, 2008 4:31 PM | Comments (2)

Simple C# Delegate Sample

New developers often ask me about C# delegate, as they got a bit confused about the basic concept and specially maximum of the reference contains and discussed from an advanced view. Well I think delegate is really simple, when you grab it's basic idea. So what is delegate? Basically it is similar like the old "C" age function pointer, where functions can be assigned like a variable and called in the run time based on dynamic conditions. C# delegate is the smarter version of function pointer which ...
Print | posted on Posted On Friday, February 15, 2008 2:47 PM | Comments (55)

Unique Data Columns in SQL Server 2005: A Quick Look

- Primary key -- Only one Identity column -- Can't be null - Identity -- Automatic value -- Only one Identity column -- Can't be null -- Can exist in addition of primary key, GUID-auto columns - Uniqueindentifier -- Can be multiple -- Can be null - Uniqueindentifier - rowguid -- Auto generated -- Only one Identity column -- Can be null -- Can exist in addition of primary key, Identity columns - Unique Key -- Can be null -- Can be multiple Technorati Tags: database,design,software development ...
Print | posted on Posted On Thursday, February 07, 2008 1:02 PM | Comments (0)

Normalization Case Study and Theory

Functional Dependencies The value of one attribute in a table is determined entirely by the value of another attribute. For example, the birthday of a Customer can be determined by the primary key of the Customer, in which record the birthday belongs. Here an Customer’s birthday depends on the Customer’s primary key. Customer birthday (depends on) -> Customer ID The notation X -> Y means if and only if each X value is associated with at most one Y value. We can find the birthday of a Customer, ...
Print | posted on Posted On Wednesday, February 06, 2008 6:06 PM | Comments (10)

Software Design Tradeoff Factors

In perfect world you can get all of the best things in one place. But in real world it’s not. In software development there are some basic trade-offs when you consider a specific design feature. Exploring these considerations will help you to create the architecture that matches best with the given context. Performance Security (code level, encryption etc) VS Performance (code level) Caching: Memory VS Performance Object Oriented/Layered Code VS Performance Scalability VS Deployment (n-tier) User ...
Print | posted on Posted On Wednesday, February 06, 2008 6:01 PM | Comments (0)

Copyright © Mohammad Ashraful Alam