Technology => Technical babbling

Ajaxify your web application...

noreply@blogger.com (Yash) — Sat, 02 Jan 2010 04:10:00 +0000

Happy New Year!!! This year I have made a resolution that I will blog more about the things I learn :)

Today I am going to blog about how to implement Ajax functionality without using the Asp.Net Ajax.What AJAX functionality means is -- you can make a request to the server from the client without the page being refreshed.It gives a better user experience.

The main object behind Ajax functionality is the XmlHttpRequest Object. This object has a method called send which can make request to the server.

In this application, I will show how to populate a dropdownlist based on user selection without doing a complete postback.

The way I have designed this application is:
1)I have added a HttpHandler which executes functions based on the querystring input.
2)Ajax Request is made to this handler from javascript with appropriate parameters i.e
a)BusinessFunction Name, which should be executed
b)Parameters which the businessfunction needs.

I have created custom attributes which keep track of which classes and functions are business functions, i.e the functions that can be executed from the Ajax Handler. FrameworkHelper is implemented as singleton which will keep all these functions in the dictionary and will execute these functions on the fly using reflection.

You can download this application here

Happy Programming!!!

-Yash

Javascipt Basics - Part 2

noreply@blogger.com (Yash) — Sun, 04 Oct 2009 18:09:00 +0000

I did one blogpost couple of months back regarding Javascript Basics. This is continuation of that post.

A)EncodeUri and EncodeUriComponent -
These are builtin function which are used to encode the parameters.

EncodeUri(uri)-- will encode the part of the Url after the "http://somehostName/{This part will be encoded}

EncodeUrlComponent(url) -- it assumes that you will passing only the parameter that you want to encode. It will encode whatever you pass to the function.

For eg: if you pass

var url = 'http://yashwant.dns.mycompany.com/H ome';
alert(encodeURI(url));
Output:http://yashwant.dns.mycompany.com/H%20ome%3C/defau%20lt.aspx%3E

alert(encodeURIComponent(url));
Output:http%3A%2F%2Fyashwant.dns.mycompany.com%2FH%20ome%3C%2Fdefau%20lt.aspx%3E

B) Functions as Data
Javascripts treats functions as Data. So a function can be assigned to a varaible.
for eg:
var x = function()
{
alert('this is a function');
}
This notation is called as function literal notation

C) Anonymous Functions
Anonymous function are declared in place and dont have a name. Main use of Anonymous functions are it makes the code more elegant. They are used a lot as callback functions. As we know that Functions can be treated as data, so we can pass a function to another function as a parameter in javascript.
For eg:

var y = function (functionParameter)
{
alert('I am in functionA');
//CallBack the anonymous function that you passedin
functionParameter();
}
y(function() { alert('I am the callback function')});

D) Global Objects

When we declare a varaible using the object literal notation i.e

var Person = {
firstName: 'Yashwant',
middleName: 'Jaywant',
lastName: 'Patil',
print: function() //This is a method
{
alert(this.firstName + " " + this.middleName + " " + this.lastName);
}
}

Person property gets attached to the global javascript variable. In this case, since the code is running in a browser "person" property gets attached to the WINDOW object. So you can call the print method on the Person object like this

//Person Varaible gets attached as a property of the Global Object i.e Window object
window['Person'].print();

E)Configuration Objects
The rule I follow while writing javascript functions is :If there are more than 3 parameters that need to be passed to a javascript function, it is better to pass it as a JSON configuration object.

for eg:

//Cofiguration Objects...
var func = function Print(configurationObj)
{
for (var j in configurationObj)
{
alert(configurationObj[j]);
}
}
var obj = {"firstName":"Yashwant",
"middleName":"Jaywant",
"lastName": "Patil"
};
Print(obj);

It makes the code easire to read and understand.

Thanks,
Yash

Facade Pattern

noreply@blogger.com (Yash) — Sun, 16 Aug 2009 19:48:00 +0000

Facade pattern is a very simple but useful pattern.When I think of Facade pattern.. what comes to my mind is composition.

Complex System ----> Sub System 1
----> Sub System 2
----> Sub System 3
----> Sub System 4

For an external system we can create a wrapper which hides all the subsystems and provides an unified interface. Internall this wrapper will dispatch the call to the correct subsystems.

For eg:
public Class ComplexSystem
{
private SubSystem _subSystem1;
private SubSystem _subSystem2;
private SubSystem _subSystem3;

public void SubSystem1Method1()
{
_subSystem.Method1();
}

public void SubSystem2Method1()
{
_subSystem2.Method1();
}
public void SubSystem3Method1()
{
_subSystem3.Method1();
}
public void SubSystem4Method1()
{
_subSystem4.Method1();
}
}

I hope this explanation helps. You can donwload a real world example here: http://dotnetdevblog.googlepages.com/FacadePatters.zip

Thanks,
Yash

Javascript Basics......

noreply@blogger.com (Yash) — Sun, 14 Jun 2009 23:15:00 +0000

Its been long time since I wrote a post. Was busy with lot of things.
Lately I have been working a lot with Javascript. This is the first time I am using Javascript heavily in a project.

Today I want to demonstrate some of the basic javascript concept.
1)Static Methods
2)Public Methods/Variables
3)Private Methods/Varables

In this project.. I created a simple server control which renders a link. Href of this link is a javascript function.

Javascript method CreateArt(...) creats an instance of a Window Object.
var win = new Window();

Window object'ss prototype property has two methods
1)Initialize(..) -- Sets the local variable firstName,middleName,lastName
2)Display(..) -- Displays the names in a table which is attached to the body of the document.

Another way to set the prototype is to add each function individually.

adding public variable/function and a private variable/function to the Window Object.

Declaring a public method is done using the this keyword.

Private methods are declared using a private Variable and then adding a method to that variable. The advantage of this is we dont expose this method from the class.

Static Method can be easily declared by adding that method to the class. for eg:

If you want to download the source code please click here --> http://dotnetdevblog.googlepages.com/JavascriptBlogApp.zip

I started loving javascript as a language after working on this project. I used to think javascript was not for real programmer but now I believe it has lot of goodness in it.

Embrace It :)

Thanks,

Yash

Implementing Strategy Design Pattern...

noreply@blogger.com (Yash) — Mon, 16 Feb 2009 01:21:00 +0000

Implementing the strategy pattern helps in decoupling the application.The main idea behind you can interchange the different implementation of your algorithm without breaking the code.

What I mean by that is .. I have an interface, IGetData which defines a single method which returns a Customer object.

public interface IGetData
{
Customer GetData();
}

This interface is implemented by two different classes...SqlDataSource which gets the customer object from the SqlServer Database, while XmlDataSource gets the Customer object from the XmlDatasource.
The data class encapsulates the interface[IGetData]... in the Constructor of the Data class. you can pass in different implementations of IGetData. i.e you can pass any class which implements the IGetData interface.
By doing this .. you can have some factory method which will return the appropriate class which implements the IGetData interface.

PS: Click on the image to enlarge.

You can decouple more by using either factory or abstract factory pattern.
SourceCode download ---> http://dotnetdevblog.googlepages.com/StrategyPattern.zip

Happy Programming!!!
Yash

Accessing Embedded Resources in an assembly....

noreply@blogger.com (Yash) — Sun, 15 Feb 2009 18:11:00 +0000

Recently I was working on a project where..I had to embed some Config.Xml files in an assembly. That assembly was later on added to the main project.

Accessing the resource:

Step1: Add the resource and make the "BUILD Action" as embedded resource in Visual Studio.

PS: Click on the image, to View the Code..

Step2: Use Reflector to get the resource Name.

Step3: Load the assembly .. and use the method "GetManifestResouceStream" to access the resource..

Assembly assembly = Assembly.Load("MyLib");
Stream st = assembly.GetManifestResourceStream("MyLib.Config.Config.xml");

Its a nice way to access embedded resources from the build..

Happy Programming!!!

Yash

noreply@blogger.com (Yash) — Wed, 28 Jan 2009 23:28:00 +0000

Hello... today I found an interesting class ...PostBackOption class from the
System.Web.UI namespace. PostBackOption's is interesting becuase it lets you create controls like

Different implementation of StateBag

noreply@blogger.com (Yash) — Sun, 18 Jan 2009 23:01:00 +0000

I am going to show some different implementations of StateBag... many times while developing .Net Application, you need to pass some data from one function to another for eg:

A() -> B() --> C()
OR

you want to keep data in some collection and spit it out during page rendering.

Instead of moving the data domain data from function to function, it is a good idea to put the data in the Application Context or in the StateBag.

StateBag -- This is implentation is not a session implentation but its global becuase I am making the stateBag a static variable.

PS:Click on the image to enlarge

StateBag1 implementation:

StateBag1 is a good implementation which exposes a property which will return the StateBag.. The StateBag is stored in the HttpContext. HttpContext provides a items collection where you can dump all your StateBag.This implementation will only work in web centric senario as HttpContext is not available in non web centric application.

StateBag2 implementation:

This implementation is similar to StateBag1 but can be used in non web-centric as it uses the CallContext object if HttpContext is not available.

Creating your ApplicationContext:

This is bascially a wrapper class around the HttpContext. You can store this AppContext object in the CallContext, this way only one instance is created per thread.I like this implementation a lot.

You need to searlize this StateBag before the page renders as a hidden string. When postBack happens that time you need to desearlize the StateBag to get the parameters back.

If you want to download the SourceCode ---> http://DotNetDevBlog.googlepages.com/WebApplication1.Zip

I hope you like the implentations :)

Happy Coding!!
Yash

Adding Reflector as External Tool in Visual Studio

noreply@blogger.com (Yash) — Sat, 17 Jan 2009 21:27:00 +0000

I spend most of my dev time in Visual Studio. I hate to go out of VS and open some other programs like fiddler or reflector. In Visual studio you can easily add the tools that you use a lot by adding these tools as external tools.

All you have to do is go to Tools->External Tools, configure your tool over there ... Heres a screen shot of to configure Reflector in Visual Studio..

Thats it.... next time you want to use the reflector... all you have to do is go to tools and select Reflector.

Thanks,
Yash

Tools I use....

noreply@blogger.com (Yash) — Sun, 28 Dec 2008 00:36:00 +0000

Today, I am going to list the tools that I use often in my day to day development activities.

1)Reflector
2)Notepad++
3)Fiddler2
4)LinqPad
5)SOAP UI
6)WCF Trace Viewer
7)Firebug
8)IE development toolbar
9)SlickRun
10) Live Headers (FireFox plugin)
11) Thunderbird

Happy holidays!!!

Thanks,
Yash

Fiddler with ASP.Net Development Server...

noreply@blogger.com (Yash) — Mon, 08 Dec 2008 00:34:00 +0000

Fiddler is one a tool that I use very often while debugging,to see what paramaters are going in the request etc....

Today I was doing some Custom Server Control development, where I was passing some paramaters using Http POST.I thought that Fiddler will automatically capture the request to the dev server, but it doesnt.

If you are doing any dev work on the ASP.Net Development and want to use fiddler -- try this.

Suppose the url is: http://localhost:1203/MyApp/Default.aspx

if you just try to capture the request using Fiddler it wont work, you need to change the
url to: http://localhost.:1203/MyApp/Default.aspx

Just append "." after localhost

Nice little info....

Enjoy!!!
Yash

Commands that I use Everyday

noreply@blogger.com (Yash) — Sat, 11 Oct 2008 20:29:00 +0000

Today I am going to list some of the commands that I use all the time while coding... You can type these commands in the Run Prompt.

1) For Windows Server 2003:

a) tsadmin (Terminal Services Manager) ---> Used to connect to a computer and see who has logged in, to logoff the users.. etc.
b) qwinsta /server:servername ---> to query windows station.
This is a command line tool that I use to see who has logged into a particular machine...
c) rwinsta ID /server:servername ---> Used to logoff an user from a particular server based on the ID.
First get the ID of a particular user using qwinsta and then logoff the user using rqinsta.
d) mstsc -- to launch the remote desktop connection.
e)inetmgr -- to launch IIS
f)devenv -- to lauch visual stuido 2005 and 2008.
g)lusrmgr.msc -- Used for adding a New User or adding a existing user to a group.
h)query --- to query a session etc..

2)Windows Server 2008
The only command that has changed from the windows server 2003 is
a) tsadmin.msc .... now you have to add the .msc extension to launch the Terminal Services Manager..

3)Visual Studio Commands
a) Control + "." to add the usings
b)Control + Alt + "D" --- to view all the breakPoints set in the application
c)Alt + Enter -- to view the properties window
d) Ctrl + Alt + "F" -- to search for some string in the entire solution
e)Ctrl + "F" -- to search for some string in the current file
f) shift + F12 -- to find all the references for a function.
g) Getting VisualStudio CommandPrompt -- Control + W + A
h)Go to LineNumber in code-- > Control + G
i) Open folder in VisualStudio -- > Control + O
j)Go to defition of a fucntion etc - F12
k)Formating Code - Control + K + D

4) windows general shortCuts I use
a) wins..Key + "R" to get the Run prompt.. very use full for me
b) wins..Key + "D" to get to the Desktop
c) Control Panel -- at the Run prompt type .. control
d) Add remove features -- at the Run prompt type control appwiz.cpl

5)VisualStudio Command Prompt --
a)np -- add a new project
b)props - open Properties Window
c)View.SolutionExplorer -- for viewing solution explorer
d) open filename -- to open a file from command prompt

Happy Coding!!!
Yash

Implementing Factory Pattern using Reflection and Singleton Pattern

noreply@blogger.com (Yash) — Tue, 07 Oct 2008 21:37:00 +0000

Today I want to demonstrate how to implement Factory pattern using Reflection...

Important point that should be considered whenever you write code
1) Keep the coupling between components as low as possible --

what this means is when you write components, you should always try to keep the code independent of the other components. It should be testable by itself. It should be reusable without the need of other components.

One of the standard technique that lot of people use to reduce the coupling is by using the Factory Pattern.

Generally use the "new" keyword to instantiate a class, but my doing so we make our code dependent on that object.
Factory pattern separates the creation and initialization of object.

To demonstrate this,
Lets see the class diagram

PS: Please click on the image to see the image contents.

Computer is an abstract base class and different computers like (BrandXComputer or ConcreteComputer) inherit from this interface. Computer as an abstract property called Mhz. Different derived classed will override this property.

Similarly, there is an Abstract class called ComputerFactory, it has an abstract method called "GetFactory". Every class you create will have a corresponding concretefactory class which will return an instance of the corresponding Concrete Computer class. Each concrete factory has a Singleton implementation i.e only one instance of these classes are created. This make sense here as we dont want to instantiate the Factory class everyone.. which will be a wastage of memory.

Alright, till now what we have done is standard factory implementation. It gets interesting when you actually get an instance of the factory. The way this is implemented is through Reflection.

All the concrete factories that you need are kept in the App.Config Files...

PS: Please click on the image to see the image contents.

In the config file bascially we keep all the entries of the concrete factory along with their types i.e class names.

There is one more class which is very important in this whole setup and that class is -- ComputerFactories.

Computer factories has one Static method GetFactory which will take the factoryname (i.e key from the app.config file) , from that it will get the type of the factory and using FieldInfo class it will get that singleton instance we created. Reflection is a very powerful and it has been extensively used in the .Net Base Class Library.

As you can see we, the client code doesnt need to know anything about the Computer Object instantiation or initialization. The code is not tightly coupled.

To download the SourceCode -- Click Here

Happy Programming!!!
Yash

Great Plugin for Xml Debugging... Xml Visualizer v.2

noreply@blogger.com (Yash) — Sat, 04 Oct 2008 22:43:00 +0000

While going through the CodePlex website (one of my fvt website) I found this new Visualizer for Xml.

Its a great plugin that you have to copy paste in the "MyDocument\Visual Studio(2005/2008)\Visualizers" directory.

I really wanted a tool where I can just load the Xml into memory and play with the XPath Queries.This visualizer lets me do that and more.

PS: Please click on the image to view the contents of the image.

1) I can easily add a XPath Query and check the results.

PS: Please click on the image to view the contents of the image.

As you can see in this screenshot I have added a XPathQuery and you can see the results in the output. Very nice feature while debugging.... or if you are doing some xml parsing.

2) I can see the xml output in a browser.

3) I can create StyleSheets and use them to style my Xml file contents.

You can download the XmlVisualizer 2.0 from CodePlex.

Link --> Download Location

I think developers can be definitely more productive if they use this tool.

Happy Programming!!!
Yash

How to Query Active Directory for Users and Groups..

noreply@blogger.com (Yash) — Fri, 19 Sep 2008 18:09:00 +0000

Last couple of months I was really busy working on a small ASP.Net project from scratch....

Alright... enough of that.Lets get to the Code....

First of all I want to show you guys how I divided the whole application into small components... here's is a screen shot of the app...

PS: Please click on the image to view the contents.

Each component is a stand alone component for a specific purpose....
So.. lets get into the Auth component...

We had a requirement where we wanted to Authenticate a user against the Active Directory...basically certain pages were not visible to certain groups...

Querying Active Directory in c# is very easy task.. but before that if you are not familiar with the structure of your active directory you can install a great utility from Microsoft called ldp.exe.

I tried it to see what is the structure of our Active Directory.

So basically to query an Active Directory you need a ldappath... like

LDAP://NXdfsdfqwM03.ABC150.org/DC=ABC150,DC=org , A username and password who has access to this Active Directory.

Now to get All the Users in a particular Group this is the code...

This function bascially calls the GetUserByGroup which in turn calls the GetUserDetails function where I am querying the active directory for a particular user.

PS: Please click on the image to view contents...

PS: Please click on the image to view contents...

PS:Please click on the image to view contents...

Important classes are DirectoryEntry, DirectorySearcher, DirectoryEntires.. etc.

I hope this gives a basic idea about how to query an Active Directory.

Happy Programming!!!
Yash

Pics from the Trip to Philadelphia,PA

noreply@blogger.com (Yash) — Thu, 11 Sep 2008 22:38:00 +0000

Check out the pics at ... http://picasaweb.google.com/DotNetDevBlog/PATrip#

Enjoy!!!
Yash

Foundation of Programming free e-book

noreply@blogger.com (Yash) — Sun, 06 Jul 2008 04:42:00 +0000

Last week while watching Channel 9 video, I came across this good free e-book (Foundation of Programming) from Karl Seguin.

Download it and read it, really good book. I have not covered even 50 % of it, but I love the things that he has explained like ... mock objects,TDD, Dependency injection etc.

Initially its bit tough but very useful in long run.

Grab it!!!!

http://codebetter.com/files/folders/codebetter_downloads/entry179694.aspx

Thanks,
Yash

Lambda Expression

noreply@blogger.com (Yash) — Tue, 01 Jul 2008 05:05:00 +0000

Lambda Expression -- introduced by Microsoft in C# 3.0 is a very fascinating topic. It has been extensively used in LINQ(Language Intergrated Query).

So, what is Lambda Expression?

Lambda Expression is basically nothing but an anonymous function.

In .Net 1.1 we used to create delegates using delegate type. Delegate is a type safe datatype which contains a reference to a function.
Eg:

.Net 2.0 introduced the concept of Anonymous delegates. what is means is you can write the whole function inline. This makes the code more readable and you don't have to define instance or static methods.
Eg:

As you can see the code is readable and concise.

In C# 3.0 the concept of anonymous delegates has been taken to the next level by adding lambda expression.

Lambda expression uses an operator ( =>) which should be read as "goes to".
Eg:

As you can see the code is very elegant and the IL(intermediate language) generated by all the 3 ways of using delegates is the same. So the point to understand here is that the complier will generate exactly the same IL for all the 3 implementations so we don't need a new runtime for executing this code. .Net 2.0 runtime will be able to execute this code for us.

Lambda's can be expression or statements. Lambda statement are nothing but a group of c# statements clubbed together.

IL generate by instance methods:

IL generated by anonymous delegates (.Net 2.0)

IL generated by Lambda Expression

Click here to download the SourceCode:

I hope this will help you understand what Lambda expressions are.

Thanks,
Yash

How to Read custom entries from the Web.Config/App.Config file

noreply@blogger.com (Yash) — Sun, 29 Jun 2008 21:13:00 +0000

Today I am going to blog about "How to read custom entries from the Web.Config/App.Config file."

Working as a .Net Developer, there will be many occasions when we want to store some data (Maybe Key/Value Pair) in the configuration file but we dont want to add to the AppSettings. In such situations, I have always found is very easy to store my Config entires in the Custom Config sections in Web.Config files.

I want to read the custom section shown below.

The idea behind reading or writing to the config files is that -- "You should tell the framework how you want your data to be Serialized/Deserialized.

In .Net 2.0 made it very easy to Read/Write config data into the configuration file by providing the functionality in System.Configuration.dll.

Add the entry shown above, in the ConfigSection so that framework can create an instance of the class at runtime using reflection.

I have attached the SourceCode for this application.

Source Code Loc:

http://dotnetdevblog.googlepages.com/ReadCustomConfigSections.zip

If you like/dislike something, feel free to leave comments.

Thanks,
Yash

Tools to Write Solid code!!!

noreply@blogger.com (Yash) — Sun, 01 Jun 2008 01:28:00 +0000

Today I am going to blog about two important tools most of the developers should have to write solid code.

1)FxCop

This is a free tool from Microsoft which will run through your .dll files and will point out where yo have made design mistakes or where you have violated coding standards.

I started to use this tool sometime back and its really neat.

I would recommend other software developer to use this tool.

2)Stylecop or Source Analysis.

Very nice tool from Microsoft which is free now. Get a copy. It is integrated with visual studio .

Just run it and make your code more readable and pretty.

Happy Programming!!!

Yash

How to Write Solid Piece of Code

noreply@blogger.com (Yash) — Sat, 31 May 2008 22:35:00 +0000

The most important point to consider while designing and writing code

1) Always design code in such a way that it is Open for extension but Closed for modification.

i.e when a new requirement comes don't add new code to the classes that work but create new classes to fulfill those requirement . i.e the previous code is locked.

The more code code you add to the existing working code the more possibility of introducing new bugs and ofcourse you have to change the UnitTest Code too.

ALWAYS TRY TO USE DESIGN PATTERN LIKE FACTORY,SINGLETON ETC.

USE OOP CONCEPTS TO KEEP THE DEPENDENCY TO MINIMUM.

I will give you an example here...

Create a Abstract base class... and derive your classes from that i.e different version of classes.

This way you can use the factory pattern and create the appropriate version of the classes depending upon the requirement.

This way you keep the dependency to minimum.

VERY USEFUL TECHNIQUE----

2) ALWAYS GO BACK AND REFACTOR YOUR CODE (Very Important)

As new requirement come always go back and try to refactor you code, create new classes, delegate functionality to different classes, this makes the individual code more testable.

Very important while writing code.

When you have implement something..

a)Start with simple things... make then work as desired.
b) Then go back and add new functionality to it.
c) Side by Side your integration code should go on, i.e think about how you will integrate with you add i.e creating MSI, installers etc...

If you write code this way, there are more chances of finding the edge cases and your code will be more solid. Always implement small components i.e small projects and then integrate with the main application.

Don't code the whole thing in one shot, Very important concept to remember.

When designing api's, try to separate out the common things from the things that differ. Designing good api is a very important thing in software developers life (atleast for me it is the single most important thing) .

If you follow this, your code will definitely be more solid and testable.

These are some of the points I learned from my Manager here in Redmond, WA.

Update:

Before writing code two things to remember

1) Code should be as testable as possible.
2) Code should be reusable.

Consider each functionality as a seperate set of class.-- Always think how I can refactor this functionality into different set of classes. (Very important for good design.)

Happy Programming!!!

Yash

Hello There!!!

noreply@blogger.com (Yash) — Wed, 28 May 2008 22:11:00 +0000

Hello Friends,

Its been a long time, I have not blogged. Lot of things happened during the last couple of months.

Most important was I left my Job at Telecom Industry to join one of the biggest companies in software development.

I loved my job back in Oklahoma but I had to make the tough decision as I am still learning lot of new things in software development and coming here in Seattle,WA was a very important decision in my life.

I believe that no decision is right or wrong. Everything depends on the how we look at it.

I struggled a lot here in Seattle initially, but now I have feel like I have come to terms with the new job.

Learning curve is huge. Lot of new ways of builing apps, writing apps among other things.

I miss my freinds in tulsa,OK but life goes on ...

Will be writing some new blogs about the things I learnt here in Seattle, WA.

Thanks,
Yash

Happy Xmas and Have a Great New Year....

noreply@blogger.com (Yash) — Wed, 26 Dec 2007 02:20:00 +0000

Thank you for reading my post.. I wish you and your family a Happy Xmas and a prosperous New Year(2008!!!!!!)

Happy Programming!!!

Yash

How to Design UserInterface.... AND Custom Validation

noreply@blogger.com (Yash) — Thu, 08 Nov 2007 19:51:00 +0000

1) While Designing the User Interface (Presentation Layer) always put all your controls in a Table.

Place Control 1 Here ...

Place Control 2 Here...

2) While designing the Web-Page make use of PlaceHolder Control. The advantage of this technique is that

a) You can Dynamically Load and Place the control at runtime... i.e Suppose you have a app- Setting Key/Value pair in your web.config file --- which you can read in from the web.config file and depending upon what you get from the WeB.Config file you can select which control to Load in the Palce Holder.

b) This gives a uniformity and Flexibility to get User-Interface Design.....

c) This way you can totally concentrate on creating the UserControl and not worry about the Presentation Layer.

-------------------------CUSTOM Validator-------------------------------------------------

With Custom Validator you get to validate the Control at the

ServerSide -- By Creating a function OnServerValidate()
ClientSide -- By writing a function in the ClientSideValidation()

That all that it is...

Thanks,
Happy Programming!!!!!

Asp.Net -- Informative URL's

noreply@blogger.com (Yash) — Wed, 31 Oct 2007 19:03:00 +0000

--- This is a good informative Url for CrossPagePosting ---

http://msdn.microsoft.com/msdnmag/issues/05/09/CuttingEdge/

--- This is a good Informative Url for Asp.Net Page Life Cycle ---

http://msdn2.microsoft.com/en-us/library/ms178472.aspx

Thanks,
Happy Programming!!!