SQL Server stores bytes, so you need to save and read the bytes.

// Turning img into bytes
Bitmap bmp = new Bitmap( FILENAME );
MemoryStream ms = new MemoryStream();
bmp.Save( ms, SOMEIMAGEFORMAT );
byte[] imgBytes = ms.ToArray();

You can now save imgBytes to SQL using varbinary or image column types. to get it back

// Turning the bytes back into an image
byte[] imgBytes = DirectCast( row["IMAGECOLUMN"], byte());
MemoryStream ms = new MemoryStream( imgBytes );
Bitmap bmp = new Bitmap( ms );

Using the wrong tool for the job is half the fun.

Something like this

if( DBNull.Value.Equals( dr["prod2"] ) || dr["prod2"].ToString() == "0")
Label28.Visible = false;
else
Label28.Text = dr["prod2"].ToString();

Using the wrong tool for the job is half the fun.

The theme applied to the page is also applied to the master page, As the master page is rendered within the pages context. Just make sure you set the page theme on the PreInit event.

Using the wrong tool for the job is half the fun.

Are you using the unicode types? nvarchar, nchar and ntext. Also what collation are the fields set to?

Using the wrong tool for the job is half the fun.

Your asking for information that applies to all users, by specifying ConfigurationUserLevel.None. Not a per user level, which is what your trying to save. Try the other types. Also settings should be user level and not application level. Or they'll never change anyway.

Using the wrong tool for the job is half the fun.

Yes it does. It's request header will usually contain all that information for any request made of the server.

Using the wrong tool for the job is half the fun.

The best I ever saw was "There has been an error press ok to try again, or cancel to quit." That was fine accept there was only an OK button. And it always failed... Task Manager to the rescue.

Using the wrong tool for the job is half the fun.

It depends how your sending it. With the standard System.Net.Mail.SmtpClient you can send a System.Net.Mail.MailMessage setting its properties and setting IsBodyHtml to true.

Using the wrong tool for the job is half the fun.

How I wish it was that easy, unfortunately some browsers disable that ability and even then for some reason it doesn't always work. You can however you Page.ClientScript.GetPostBackEventReference(Control, String) to do this.

Using the wrong tool for the job is half the fun.

Erm, I think your missing something from your code, I can't event see a menu tag set.

Using the wrong tool for the job is half the fun.

If no file is specified then the Default content page list is where it looks (Documents Tab in IIS). It goes through the sequence of page names set for the directory, and picks the first one that actually exists, and then processes that file exactly as if it had been called originally. Also IIS checks the processing list before it actually looks for the file, So it goes to aspnet_isapi.dll and passes the request information to it, by default it doesn't even check that the aspx file even exists. (Its a checkbox option of whether to check the file is actually on the server.)

Using the wrong tool for the job is half the fun.

This sounds like a permission issue. Have you tried manually setting the account details when you create your directory entry? Have you set an authentication type? Sometimes I've found this to work.

Using the wrong tool for the job is half the fun.

lastlogon is notorious in fact it doesn't even replicate if you have more than one DC. Try lastlogontimestamp. However this only works with 2003 server and above, and they have to be in the correct 2003 Domain mode. No 2000 servers. Otherwise it's lastlogon and checking all the servers. and even then it might not be accurate.

Using the wrong tool for the job is half the fun.

You could override the ToString() function in the Blog class.

class Program
{
static void Main( string[] args )
{
object obj = "Test from string";
Console.WriteLine("The result of to string is:" + obj.ToString());
obj = new Test();
Console.WriteLine("The result of to string is:" + obj.ToString());
Console.ReadKey();
}
}

public class Test
{
public override string ToString()
{
return "Test from class";
}
}

Using the wrong tool for the job is half the fun.