You receive this error when compiling your application:

Error CS0246: The type or namespace name 'XXX' could not be found (are you missing a using directive or an assembly reference?)

This occurs when you have mistyped or misspelled your application’s namespace, generally for a code customization you have added to your application.

Solution

Namespaces are case sensitive.  Make sure you have used the proper spelling and case for your application’s namespace.

More information on this error is in this Microsoft Knowledge Base article:

http://support.microsoft.com/default.aspx?kbid=304656

NOTE: You will want to confirm if the domain has any email users that are sending from PDA style devices, as this may cause negative effects for those users. More information about this is outlined below. A content filter must be created to accommodate this. (Outlined below)

Refer to the example image below when modifying your SPF Settings.

Add any Trusted Sender domains and email addresses that you would like to bypass the content filters.

Confirm parent domain is NOT in the Trusted Sender list. This can cause an increase in spoofed emails due to the bypassing of the content filters.

Set Spam Filtering to Override spam settings for this domain

Adjust Spam Filtering Actions as outlined in the screenshot below:

Confirm Current Weights are similar to what is listed in the screenshot below:

The screenshot below is an overview of the Content Filters configured for this domain. NOTE: there may be certain variations to the content filter for specific domains.

The remaining screenshots detail the Content Filters outlined above.

Trusted Senders Content Filter Setup:

SMTP Allow Content Filter Setup:

This Content filter should contain IP addresses and Host Names of common cell phone carriers and ISP SMTP servers.

Verify SPF Content Filter Setup:

This Content filter will confirm the sending server is using a valid SPF record established for the domain name. NOTE: Confirm SPF record is setup correctly.

Block Keyword Content Filter Setup:

Block Domains Content Filter Setup:

NOTE:  If you expect to get email from foriegn domains, please confirm the domain extension before adding it to the filter outlined below:

Spam Probability High Content Filter Setup:

Spam Probability Medium Content Filter Setup:

Spam Probability Low Content Filter Setup:

Additional Information:

1. Trusted senders list only applies to spam filters, not content filters. Content filters are still run on emails from trusted senders. (As they should be, for example if I move all words containing the word "ebay" into an ebay folder. They should still go there if someone on my trusted senders list emails me about ebay)

1a. Domain trusted senders list is not used if the user chooses to override the domain spam filtering options. (If the domain admin chooses to trust user@evilspammer.com, the user should have the ability to opt out of this)

2. Spam is not content filtered. (Same example above, if I get spam about ebay, it should end up in Junk E-Mail, not the ebay folder)

2a. Content filters are meant for just that. Filtering legitimate content. They get used as a bandaid for spam however, which has slightly changed their purpose from our original intent.

3. Content filtering "cialis" will end up also matching "specialist". As someone mentioned, you can use "* cialias *" and this will require cialis to contain spaces around it.

4. Domain content filters are run before personal content filters.

5. As soon as one content filter is evaluated as true, processing stops.

6. The AND/OR operators applies to seperate rules, not multiple lines in a single rule. (Correct: Filter must match from address AND subject text. Incorrect: Filter must contain x AND y in the subject) 

If you get this error while trying to create a foreign key, it can be pretty frustrating. The error about not being able to create a .frm file seems like it would be some kind of OS file permission error or something but this is not the case. This error has been reported as a bug on the MySQL developer list for ages, but it is actually just a misleading error message.

In every case this is due to something about the relationship that MySQL doesn’t like. Unfortunately it doesn’t specify what the exact issue is. Here is a running list of causes that people have reported for the dreaded errno 150. I’ve tried to put them in order based on the frequency that I hear about a particular cause.

You may want to start by running the MySQL command “SHOW INNODB STATUS” immediately after receiving the error. This command displays log info and error details. (Thanks Jonathan for the tip)

Note: If your script runs fine on one server, but gives an error when you try to run it on a different server, then there is a good chance that #6 is the problem.  Different versions of MySQL have different default charset setting.

Known Causes:

1. The two key fields type and/or size doesn’t match exactly. For example, if one is INT(10) the key field needs to be INT(10) as well and not INT(11) or TINYINT. You may want to confirm the field size using SHOW CREATE TABLE because Query Browser will sometimes visually show just INTEGER for both INT(10) and INT(11). You should also check that one is not SIGNED and the other is UNSIGNED. They both need to be exactly the same. (More about signed vs unsigned here).
2. One of the key field that you are trying to reference does not have an index and/or is not a primary key. If one of the fields in the relationship is not a primary key, you must create an index for that field. (thanks to Venkatesh and Erichero and Terminally Incoherent for this tip)
3. The foreign key name is a duplicate of an already existing key. Check that the name of your foreign key is unique within your database. Just add a few random characters to the end of your key name to test for this. (Thanks to Niels for this tip)
4. One or both of your tables is a MyISAM table. In order to use foreign keys, the tables must both be InnoDB. (Actually, if both tables are MyISAM then you won’t get an error message – it just won’t create the key.) In Query Browser, you can specify the table type.
5. You have specified a cascade ON DELETE SET NULL, but the relevant key field is set to NOT NULL.  You can fix this by either changing your cascade or setting the field to allow NULL values. (Thanks to Sammy and J Jammin)
6. Make sure that the Charset and Collate options are the same both at the table level as well as individual field level for the key columns. (Thanks to FRR for this tip)
7. You have a default value (ie default=0) on your foreign key column (Thanks to Omar for the tip)
8. One of the fields in the relationship is part of a combination (composite) key and does not have it’s own individual index. Even though the field has an index as part of the composite key, you must create a separate index for only that key field in order to use it in a constraint. (Thanks to Alex for this tip)
9. You have a syntax error in your ALTER statement or you have mistyped one of the field names in the relationship (Thanks to Christian & Mateo for the tip)
10. The name of your foreign key exceeds the max length of 64 chars.  (Thanks to Nyleta for the tip)

The MySQL documentation includes a page explaining requirements for foreign keys. Though they don’t specifically indicate it, these are all potential causes of errno 150. If you still haven’t solved your problem you may want to check there for deeper technical explainations.If you run into this error and find that it’s caused by something else, please leave a comment and I’ll add it to the list.

Many of today's Web pages take too long for users to download. We've all landed on a page, stared impatiently at a blank screen for a minute or two, and become so frustrated that we found another activity to occupy our time.

After responding to the 25 e-mails left minimized on the desktop, we check the page again only to experience a very large image struggling to open before a page times out.

We all know there's a correlation between page load time and page size: an increase in page size means an increase in page load time. Unfortunately, users don't increase the time they spend waiting on your site. Several studies show that most users won't wait longer than 20 seconds for a page to load before leaving the site. Keep the page size less than 50KB in order to keep a user interested in your site.

Even though we know a smaller page size will retain more users, we often come across images larger than 200KB on our own sites. The problem stems from images being posted to the site either directly or through a content-providing template, unknown to the Web administrators. If the latter case is true, you may be able to use a custom tag called CFXImage to control image size and format.

Introducing CFXImage
CFXImage is a DLL that runs only on a Windows 32-bit operating system. The tag uses Microsoft Foundation Classes as a shared library, so "mfc42.dll" and "msvcrt.dll" need to be located in the system path. CFXImage is available for free at www.gafware.com.

Here are some things the tag can do through the actions invoked by the ACTION attribute as taken from the CFXImage documentation:

How to generate a CSR for Apache using OpenSSL

Recommended: Save yourself some time by using our new OpenSSL CSR Wizard to create your apache ssl csr. Just fill in the details, click Generate, and paste your customized openssl command into your terminal.

If you will be using Apache for Mac OS X server 10.5, see our Mac OS X CSR instructions.

Of course if you prefer to build your own shell commands to generate your apache csr, just follow our old instructions below:

1. Login to your server via your terminal client (ssh). At the prompt, type:

   

   openssl req -new -newkey rsa:2048 -nodes -keyout server.key -out server.csr

   where server is the name of your server.

2. This begins the process of generating two files: the Private-Key file for the decryption of your SSL Certificate, and a certificate signing request (CSR) file (used to apply for your SSL Certificate) with apache openssl.

   When you are prompted for the Common Name (domain name), enter the fully qualified domain name for the site you are securing. If you are generating an Apache CSR for a Wildcard SSL Certificate your common name should start with an asterisk (such as *.example.com).

   You will then be prompted for your organizational information, beginning with geographic information. There may be default information set already.

   This will then create your openssl .csr file.

3. Open the CSR file with a text editor and copy and paste it (including the BEGIN and END tags) into the DigiCert Certificate order form.



4. Save (backup) the generated .key file as it will be required later for Certificate installation.