One of the lesser known tricks with CSS is the fact that you don’t have to limit your elements to just one class. If you need to set multiple classes on an element, you add them simply by separating them with a space in your attribute. For example:

<p class=”pullquote btmmargin left”>…</p>

You would assign these as generic classes in your CSS:

.pullquote { … }
.btmmargin { … }
p.left { … }
If you set the class to a specific element, you can still use it as part of a list of classes, but be aware that it will only affect those elements that are specified in the CSS.

Advantages of Multiple Classes
Multiple classes can make it easier to add special effects to elements without having to create a whole new style for that element. For example, you may want to have the ability to float elements to the left or right quickly. You might write two classes “left” and “right” with just “float:left;” and “float:right;” in them. Then whenever you had an element you need to float left you would simply add the class “left” to its class list.

I like to use multiple classes for things that I want to keep standard across the entire site. For example, if I always want the bottom-margin for elements that have a bottom-margin to be 10px. By creating a class that only encompases the botom-margin:10px; I can add it wherever it’s needed.

Disadvantages of Multiple Classes
While they are supported in the major browsers, really old browsers don’t support them. So you should make sure that the first class you list is the one with the most specific information for that element.

Multiple classes can also get really confusing as you apply more and more to an element

Source: http://webdesign.about.com/od/css/qt/tipcssmulticlas.htm

Request.ServerVariables(”SERVER_NAME”)
Request.ServerVariables(”PATH_INFO“)

“Bill Gates’ recent Tech Ed keynote and Tony Chor’s follow-up blog announced that IE8 Beta 2 will be available in August in many languages. We are encouraging sites to get ready for Beta 2 prior to release as it will present a big jump in IE8 browsing traffic.

What does “getting ready for IE8” mean for web sites? IE8 displays content in IE8 Standards mode – its most standards-compliant layout mode – by default. In previous blog posts, we’ve discussed how this aligns with our commitment to Web standards interoperability. However, browsing with this default setting may cause content written for previous versions of IE to display differently than intended. This creates a “get ready” call to action for site owners to ensure their content will continue to display seamlessly in IE8.

The preferred response to this call to action is to update the site to ensure that IE8 is provided with standards content fitting the DOCTYPE. However, we know it is very important to give site owners the chance to update site content on their schedule without affecting user experience. As such, we provide a meta-tag that tells IE8 to display an entire site or a specific page like it did in IE7.

In IE8 Beta 1, that option is the “IE=7” X-UA-Compatible tag, which instructs IE8 to display content in IE7 Standards mode. However, the scenario this doesn’t address is when IE=7 is applied as an HTTP header to a site that contains Quirks mode pages. The IE=7 HTTP header will force all pages – both Quirks and Standards – to display in IE7 Standards mode. Developers using this header while updating their sites would then have to add the “IE=5” tag to each page they want to keep in Quirks mode. This logic is fine for many websites. However, if a site has lots of Quirks mode pages, or for the case where pages with frames host a mix of Strict and Quirks mode content – as brought to light by IE8 Beta 1 user feedback – the compatibility opt-out adds a bit more work than we intended.

In response to the great IE8 Beta 1 feedback we’ve received so far, we are introducing the “IE=EmulateIE7” tag to address this problem. EmulateIE7 tells IE8 to display standards DOCTYPEs in IE7 Standards mode, and Quirks DOCTYPEs in Quirks mode. We believe this will be the preferred IE7 compatibility mode for most cases. Support for IE=EmulateIE7 is available now as part of the IE June Security Update for IE8 Beta 1. Installing this update will enable you to verify you’ve applied the EmulateIE7 tag to your site correctly. ”

http://blogs.msdn.com/ie/archive/2008/06/10/introducing-ie-emulateie7.aspx

- ->
<%@Import Namespace="System.Web.Mail" %>
<%
string strTo = emailToAddress;
string strFrom = Request.Form["txtemail"];
string strSubject = "Franchise Inquiry";

MailMessage mail = new MailMessage();
mail.From = new MailAddress(strFrom);
mail.To.Add(strTo);

BodyText = " " + "\n";
BodyText = BodyText + "First Name: " + Request.Form["txtfirstname"] + "\n";
BodyText = BodyText + "Last Name: " + Request.Form["txtlastname"] + "\n";

mail.Subject = strSubject;
mail.Body = BodyText;

SmtpClient smtp = new SmtpClient("127.0.0.1"); //"rechannel.com"
smtp.Send(mail);

Error: SMTP server: The transport failed to connect to the server
Solution: Firstly if you are using asp.net 2.0 or newer then you should be using System.Net.Mail rather than System.Web.Mail.
http://forums.asp.net/t/1385665.aspx

From http://weblogs.asp.net/scottgu/archive/2005/12/10/432854.aspx
Sending Email with System.Net.Mail
.NET 2.0 includes much richer Email API support within the System.Net.Mail code namespace. I've seen a few questions from folks wondering about how to get started with it. Here is a simple snippet of how to send an email message from “sender@foo.bar.com” to multiple email recipients (note that the To a CC properties are collections and so can handle multiple address targets):

Compiler Error Message: CS0104: ‘MailMessage’ is an ambiguous reference between ‘System.Web.Mail.MailMessage’ and ‘System.Net.Mail.MailMessage’

that class is known in both namespaces hence the error. Since you’re using .NET 2.0 remove the line
Imports System.Web.Mail

Unable to read data from the transport connection: net_io_connectionclosed.

What this error means is that System.net.mail was unable to find the smtp server.

The answer will vary depending on whether you have a fixed IP or a dynamic IP but,
basically, you need to assign a valid IP to your smtp server.

With fixed IP’s this is relatively straightforward.
With dynamic IP’s it takes a bit of tweaking.

Open the IIS Manager and check the properties for the smtp server.

In the Default SMTP Virtual Server’s properties, in the “Access” tab,
in the Connection Control and Relay dialogs, make sure that your local IP is assigned.
( In my case, it’s 10.0.0.2… )

You may also need to modify your hosts file, to point 127.0.0.1 to your machine name.
( \WINDOWS\system32\drivers\etc\hosts )

Then, in your code, assign your machine name to the smtp client :

Dim client As New SmtpClient(”yourmachinename”)
client.Send(mail)

CSS takes precedence over a normal declaration. Both author and user style sheets may contain “!important” declarations, and user “!important” rules override author “!important” rules. This CSS feature improves accessibility of documents by giving users with special requirements (large fonts, color combinations, etc.) control over presentation.

Example(s)”

/* From the user’s style sheet */
P { text-indent: 1em ! important }
P { font-style: italic ! important }
P { font-size: 18pt }

/* From the author’s style sheet */
P { text-indent: 1.5em !important }
P { font: 12pt sans-serif !important }
P { font-size: 24pt }