iPhone enabled
In anticipation of the impending iPhone launch I’ve taken extra steps to ensure that this blog is iPhone enabled.
These extra steps consist of writing this post and loading my website in Safari. I feel I have utilized the iPhone SDK to the fullest extent possible and I’m excited to bring this to the masses of new iPhone users.
It’s a Safari world after all
Safari running on Windows was announced during the WWDC 2007 keynote and is available for download right now. I’m writing this post using it under Windows XP/SP 2.
Let’s count up where Safari/WebKit is in use as of today.
Adobe AIR uses WebKit as their HTML/Javascript engine.
Safari runs under both OS X 10.4.9 Tiger and 10.5 Leopard and Windows XP/Vista.
Safari runs on the iPhone.
My gut tells me that Safari on Windows combined with AIR using WebKit AND third-party development on the iPhone being done against Safari is going to be much, much more significant than we realize right now.
Depending on the adoption of the iPhone and AIR, the browser war could turn into IE vs. Safari instead of IE vs. FireFox like everyone expected.
ZFS in Leopard
Putting ZFS in Leopard is pretty cool. It looks like a nice filesystem.
So, can I access it under Windows? Without resorting to sharing it as a network share?
It’s 2007, I’m really looking for a filesystem I can format my external USB hard drives with, that doesn’t suck, that I can access from either my Windows or Apple computers. Fat32 is what? 10 years old now? When was Win95 OSR2 released? It’s time for a new system. Hopefully someone will release ZFS drivers for Windows.
In Remembrance of D-Day
Soldiers, Sailors and Airmen of the Allied Expeditionary Force!
You are about to embark upon the Great Crusade, toward which we have
striven these many months. The eyes of the world are upon you. The
hopes and prayers of liberty-loving people everywhere march with you.
In company with our brave Allies and brothers-in-arms on
other Fronts, you will bring about the destruction of the German war
machine, the elimination of Nazi tyranny over the oppressed peoples of
Europe, and security for ourselves in a free world.Your task will not be an easy one. Your enemy is well trained, well
equipped and battle hardened. He will fight savagely.But this is the year 1944! Much has happened since the Nazi triumphs of
1940-41. The United Nations have inflicted upon the Germans great defeats,
in open battle, man-to-man. Our air offensive has seriously reduced their
strength in the air and their capacity to wage war on the ground. Our Home
Fronts have given us an overwhelming superiority in weapons and munitions
of war, and placed at our disposal great reserves of trained fighting men.
The tide has turned! The free men of the world are marching together to
Victory!I have full confidence in your courage and devotion to duty and skill in
battle. We will accept nothing less than full Victory!Good luck! And let us beseech the blessing of Almighty God upon this great
and noble undertaking.SIGNED: Dwight D. Eisenhower
An account of the landing at Omaha beach.
The National D-Day memorial Foundation
Visual Studio Shell
If you create software development tools, you’ll want to consider building on the Visual Studio 2008 Shell. A streamlined Visual Studio development environment, the Visual Studio Shell provides the core foundation so you can focus on building your application’s unique features. Flexible customization options help you deliver optimized experiences for specific markets.
This looks like a really good idea. It allows developers to build the ULTIMATE add-in using the Visual Studio framework. The developers application can either integrate with any version of Visual Studio installed on the users machine or can be compiled as a stand alone application.
You can see the announcement over on the VSX blog.
Just don’t work around any technical limitations in the product.
Re-associate SQL users with logins
I've been getting our test environment in sync with our production environment the past week. Part of this effort involves moving database from our production environment to our test database server. The easiest way to do this is to put the production server into single-user mode, copy the .MDF and .LDF database files over to the test database server, and the attach the database files to the test database server.
The unfortunate side effect of this is that the SQL users in each database are no long associated with the SQL Login. SQL Server has had an sp called 'sp_change_users_login' since SQL Server 2000. You can pass in the 'Auto_Fix' parameter and the name of the SQL user that is orphaned and SQL Server will do it's best to automatically match the user name up with a SQL login. There are a few gotchas that the MSDN article, and people better versed in SQL Server internals than I, can spell out. But for 90% of the cases out there, this SP will work fine. But it only works on one user at a time. So I created the world simplest code generator to help me create all of the statements needed to attempt to reassociate my users with their logins.
-
SELECT 'exec sp_change_users_login ''Auto_Fix'',''' + name + '''' FROM sysusers WHERE uid> 2 AND uid <16000
uid 2 is the guest account and uids > 16000 are the built in "db_*" users.



