Have a look at this article.

You could make your own custom textbox that inherits the built in textbox, and that has a DefaultText property. To easily reset all textboxes, keep a static Arraylist in the class, where each textbox adds a reference to itself when it is created. Then add a static method to the class that loops through the Arraylist and resets the text of each textbox. --- b { font-weight: normal; }

i find delegates to be the same as function pointers in C/C++. so then we would be able to pass the address/delegate of some function as a parameter some_func(my_delegate); some_func(Delegate a) { a; //would call the function }

Yes, I see. So it is one other usage of delegates. Thank you --- "Art happens when you least expect it."

There's nothing built in, but a few free and commercial products around to do this. Otherwise, you're on the right track. Christian Graus - Microsoft MVP - C++

VS 2003 builds for .NET 1.1 . It uses the .NET 1.1 (or 1.0) compiler, so could you write in .NET 2.0 won't be compiled. You will indeed need to use VS 2005 for all your .NET 2.0 stuff. And I believe that if the syntax is right you can just run it on IIS and IIS will JIT compilation of all your files. That is a new thing in 2.0, that you don't have to do pre compilation of your code behind files (which actually don't really exist in 2.0) For 2.0 compilers: if you installed .NET 2.0, you should have all the compilers in the .NET directory: C:\windows\Microsoft.NET\Framework\v2.0.40607 The minor version might be different on your system, so just check under the Framework directory for the right directory. Gidon

Jesee gave you an excellent reply. However, I will say that my preferred method is to pass the information using the QueryString. In other words, set up your links to the second page like this: Webform2.aspx?messageID=123 Then inside Webform2 you can retrieve the value by using Request["messageID"]. Regards, Alvaro You know what they say about arguing over the Internet...

Client IP Address: Request.UserHostAddress Current User (if any): User.Identity Regards, Alvaro You know what they say about arguing over the Internet...

This is not the way to read from a MessageQueue. Read up on MessgaeQueue.BeginReceive and handling the the event with an eventhandler of type MessageQueue.ReceiveCompleted. Basically, you put all your reading logic in the event handler. Then you make a call to .BeginReceive in your main startup code. When the queue receives a message, your handler will be called, then you end the handler with another call to .BeginReceive. Here is some code: static void MyStart() { Type[] AllowedTypes = {Type.GetType("MyNamespace.Type")}; //Create queue object q = new MessageQueue("queuePath"); //Initialize que to handle your message objects q.Formatter = new XmlMessageFormatter(AllowedTypes); //Set up event handler q.ReceiveCompleted += new ReceiveCompletedEventHandler(q\_ReceiveCompleted); //Start receiving messages q.BeginReceive(); } private static void q_ReceiveCompleted(object sender, ReceiveCompletedEventArgs e) { //Put code here to read from the queue //... //... //Now wait for another message q.BeginReceive(); }