User group meeting this Thursday at 5:30pm.  This month’s topic:  SQL Server 2012 contained database & SQL Server 2012 Fetch & Offset.  Malathi will be giving the first session and I’ll give the 2nd on TSQL.

I’ve use Redgate for doing diffs on schema for SQL Server. Very handy tool but out of my price range. I’ve found an open source tool that meets my needs (given database x2, differences from x1):  http://opendbiff.codeplex.com/

Open DBDiff is a open source tool and reports differences between two database schemas and provides the SQL Script that synchronizes both databases so that you can use the SQL script to upgrade the database.  Works on 2012 too.

Compiled app:  httpopendbiff.codeplex.com.Binaries.zip (1.32 mb)

Source Code:  httpopendbiff.codeplex.com.Code.zip (4.25 mb)

Join us for a free event – all day learning on SQL Server: http://www.sqlsaturday.com/122/eventhome.aspx.

Friday, 7/20: many pre-conferences.  Space limited.

Need a few more sponsors.  See our options on http://www.sqlsaturday.com/122/sponsorplan.aspx.

Great event!  Looking forward to all the great sessions.

Doing some research - found this great article: http://www.4guysfromrolla.com/articles/012710-1.aspx. 

This hits on a problem I’ve been trying to address.  Problem:  developing a simple framework for doing REST based architectures in .Net.  I’ve used HTTP Handlers with ashx files.  This provides the simple approach but required you to handle all the routing (URL splitting).

With .Net 4,  routing is handled by the System.Web.Routing.  This allows a framework that provides routing for REST architectures while allowing the simple development of ASP.Net pages.  Sure, MVC & WCF provide more… but the cost is complexity.  If you need the extra features – go ahead and use them.  For the problems I deal with, I’ll take the simple and easy (quick) to understand (and code) approach.

In a nutshell, the framework I’m working on is using ASP.NET Routing which allows a developer to define routing rules, which map a route pattern - such as Categories/CategoryName - to a class that handles the request.  My classes are handled in HTTP Handlers.

Brian.

Download the code:

RoutingDemo40.zip (747.17 kb)

Release 1.1 has been finalized.  Many, many improvements; good stuff.

My apps work across platforms as stated in the supported platforms.  One issue I’ve found, and noted in a few places, is how back is supported on the Android.  I have main page –> list page –> detail page.  On Android phones (Samsung Infuse 2.2 & 2.3), after a few times going between the list and detail page – it would skip all the way back to the main page.  Skip the list page on the back.

After some testing and debugging, found a work around:

Add to your javascript file, any master js file:
$.mobile.pushStateEnabled = false;

On List pages, use header with a home anchor:

<div data-role="header" data-theme="f"> <h1>Employee Directory</h1> <a href="../../" data-icon="home" data-iconpos="notext" data-direction="reverse">Home</a> </div>

On the detail page, use the back:

<div id="employeeDetailsPage" data-role="page" class="type-index" data-add-back-btn="true">

Finally, Samsung had an update for my InFuse.

http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00045587&fm_seq=46249#kies_mini

Like a new phone.

First, under server manager – remove "IIS 6 and FTP Publishing service.

Next, Install FTP 7.5: http://learn.iis.net/page.aspx/310/what-is-new-for-microsoft-and-ftp-in-iis-7

Windows firewall can be configured from command line using netsh command. 2 simple steps are required to setup Windows Firewall to allow non-secure FTP traffic

1) Open port 21 on the firewall

netsh advfirewall firewall add rule name="FTP (no SSL)" action=allow protocol=TCP dir=in localport=21

2) Activate firewall application filter for FTP (aka Stateful FTP) that will dynamically open ports for data connections

netsh advfirewall set global StatefulFtp enable

If SSL is required, set it.

Installed a few Win 2008 Server boxes over the last few days.  I like the UI and tools.  Looking forward to Win 8 server.

Building out a few servers today.  I have 2 MSDN accounts with them.  You got to be kidding me….. maxed out – only did ~10 new keys.

All Table Columns should be PasCal Case

Pascal case: LastName
Camel case: myInt

It's customary to use Pascal case for properties and Camel case names for fields.

Pascal case means that the first letter in each word in an identifier is capitalized, camel case is similar except the first letter is in lower case.

As a general rule Pascal case is used everywhere except for parameters and private or protected fields which use Camel case. This is why length is the field but Length is the property.