http://gizmodo.com/5498412/sql-injection-license-plate-hopes-to-foil-euro-traffic-cameras

Fighting Big Brother! Love it. Ha!

This is extremely helpful for figuring out how to get CSS web design elements positioned and spaced exactly like you want.

Thanks for the heads-up, Trent!

Unfortunately, in order to configure your FTP server to utilize passive connections you have to manually change the IIS Metabase. There isn’t any user-friendly IIS Manager checkbox or anything you can just click to make it happen. The easiest tool to use to browse and edit the IIS Metabase is Microsoft’s Metabase Explorer which is included in the IIS 6.0 Resouce Kit.

To enable passive FTP connections and set the port range, do the following:

1. Install the IIS Resource Kit on your server and open the IIS Metabase utility

2. Browse to [ServerName] (local) -> LM -> MSFTPSVC

3. Right-click on MSFTPSVC and create a new string record entry (New -> String Record)

4. Choose PassivePortRange as the Record Name or Identifier and String for the Data Type

5. Enter the range of ports you would like the FTP Server to use for passive connections; i.e. 5500-5525

6. Close the Metabase Explorer and bounce the IIS services or reboot the server to make sure the changes are put into effect

If your server is also running Windows Firewall, you will also have to allow incoming connections via the port range you specified for your passive connections. This is truly a pain since there isn’t a nice and easy way to define a firewall rule for a range of ports in the Windows Firewall admin utility. You have to enter a rule for each port in the range individually – ugh. But with the use of a simple script, you can automate this process. I originally found this info on David Eedle’s site and wanted to pass it on.

The following will add a Windows Firewall rule for each of the specified ports – 5500 thru 5525 – and name them “Passive FTP [port#]”

FOR /L %I IN (5500,1,5525) DO netsh firewall add portopening TCP %I “Passive FTP” %I

The last step is remembering to also open up the same TCP port range on any hardware firewall / router you may have in place; all pointing to the internal IP address of your FTP server.

http://scmccart.wordpress.com/2009/05/04/using-expressions-for-fun-and-profit/

http://www.smashingmagazine.com/2009/04/08/from-table-hell-to-div-hell/

http://www.trentjones.net/index.php/2009/03/cs/

http://websearch.about.com//od/bestwebsites/tp/free-images.htm

When the model generation tool analyzes your database and generates the model you may see a warning message similar to the following:

The table/view ‘[TABLE NAME]‘ does not have a primary key defined. The key has been inferred and the definition was created as a read-only table/view.

Since there is no primary key assigned to this table, the model generation tool does its best to figure out what it thinks the key should be based upon the table definition and the data that is currently in the table. The bigger issue here is that there is no primary key constraint defined either. If there is no primary key constraint, you can’t guarantee that future data changes won’t violate the primary key definition that was inferred by the modeling tool. So, the entity set is created in a read-only mode; no record inserts, updates, or deletions will be allowed for this table.

If you are certain that there will never be a situation where data added to or updated in this particular table would violate the inferred key constraint, you can manually remove the read-only configuration in the model by executing the following steps:

1. Close the model designer in Visual Studio if it is still open and re-open the .edmx file in an XML editor
2. Find the edmx:StorageModels -> Schema -> Entity Container -> EntitySet element that refers to the table in question
3. On the EntitySet element, rename the store:Schema attribute to Schema
4. Remove the store:Name attribute altogether
5. Remove the opening and closing DefiningQuery tags and everything in between them
6. Save and close the .edmx file

You should now be able to make changes to your table data via the data context and entity classes.

Note: You will have to repeat these steps if you ever refresh your model from the database since your changes will be overwritten.

http://www.smashingmagazine.com/2009/03/08/70-new-useful-ajax-and-javascript-techniques/