This Old Code

Microsoft has an interesting site were they followed the money for search spam, using Fiddler.

Strider Search Ranger: War on Search Spam: Shifting the Battleground by “Following the Money”

Ask's little guerilla marketing campaign information-revolution-org seems to be back firing. 

My suggestion before you go after Google. Ensure your search is as good or better then Google.  Unless you just wanted to make every one laugh.

I  have now passed the CodingHorror Certification Program

after testing my blog engine with the following steps:

1. Compile your application code. Getting the latest version of any recent code changes from other developers is purely optional and not a requirement for certification.
2. Launch the application or website that has just been compiled.
3. Cause one code path in the code you're checking in to be executed. The preferred way to do this is with ad-hoc manual testing of the simplest possible case for the feature in question. Omit this step if the code change was less than five lines, or if, in the developer's professional opinion, the code change could not possibly result in an error.
4. Check the code changes into your version control system.

Now I to can proudly display my new logo:

Wal-Mart Now has the right to offer mortgages and debit cards.  I don't know.  I just don't know.

Full story.  A home loan from Wal-Mart?

I was talking about the new crypto algorithms in Orcas with a co-worker today, and since The Moth was kind enough to remind me I figured I would post a link to the .Net Security Blog Covering them

Thought I would pass along this little message to all the Vista users out there

from the IEBlog

Hi, I’m B. Ashok, the Product Unit Manager for Web Development Tools.  As mentioned in my earlier post last summer, we have removed the DHTML Editing Control from Windows Vista as part of making the operating system more secure. 

One application that used the DHTML Editing Control in the past was OWA (Outlook Web Access). We have issued a required update to both Exchange 2000 and 2003 that enables OWA support for IE7 in Windows Vista. However if your server does not have this update applied, you may experience the inability to compose and edit e-mail messages on OWA when running IE7 in Windows Vista. When this happens, you will see a red ‘x’ in place of your e-mail message body.

The Exchange team has a good blog post which explains the issue in more detail, and describes how to update your Exchange 2000/2003 server to remedy this issue. The update does not require a reboot of the Exchange server and will fully enable OWA to work for clients using IE7 in Windows Vista. If you run into this problem, we highly recommend that you contact your Exchange 2000/2003 administrator to make sure they have installed this update.

One other item to note is that the update referenced in this post, was re-released on Feb 2007 to fix two additional issues:

• Fixed inability to edit replies to messages composed in Entourage Exchange client
• Fixed inability to edit replies to meeting requests

If you are running into either of these two issues, installing the current version of the update should fix the problem.

Hopefully this helps anyone using Windows Vista who may be experiencing this issue with OWA.

--Bash

J.D. Meier Blogged about Structuring Projects for Team Foundation Server

Interesting very similar to what we have adopted for our projects.

Other links that I found of use regarding structuring projects all form Microsoft's Patterns & Practices team.

• Structuring Solutions and Projects
• Managing Dependencies
• BuildIt

Source Gear Vault didn't like me this morning and gave me the following error for several files:

 

[3/13/2007 9:54:17 AM] Check in $/Pds/PdsAdmin/main/firstlogin.aspx
[3/13/2007 9:54:17 AM] Upload for item $/Pds/PdsAdmin/main/firstlogin.aspx failed, retrying...
[3/13/2007 9:54:17 AM] Upload for item $/Pds/PdsAdmin/main/firstlogin.aspx failed, retrying...
[3/13/2007 9:54:17 AM] Upload for item $/Pds/PdsAdmin/main/firstlogin.aspx failed, retrying...
[3/13/2007 9:54:17 AM] Ending the transaction
[3/13/2007 9:54:17 AM] Upload for item $/Pds/PdsAdmin/main/firstlogin.aspx failed too many times, aborting transaction.
Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.
The specific error was "The server returned an unknown error header: VaultFileUpload.aspx encountered: FailFileInvalidCheckSum"
An exception was encountered during the transaction. Exception: The server returned an unknown error header: VaultFileUpload.aspx encountered: FailFileInvalidCheckSum at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)
[3/13/2007 9:54:18 AM] Transaction failed
[3/13/2007 9:54:18 AM] Transaction failed

I found a work around but how the server and local file became corrupted is beyond me.

To resolve:

• I copied the file in question firstlogin.aspx
• In the vault GUI I undid my checkout and set local copy to be deleted.
• I checked the file out again.
• I next copied the file back into my work directory.
• Now I can check it in.

It looks like Google pissed off Viacom by not preventing more of their content from being posted to YouTube after they requested a 100 odd thousand clips be removed. 

Link to BBC NEWS | Business | Viacom to sue Google and YouTube

Its events like this that make me wonder why I run my own DasBlog engine and not some Wordpress or Blogger site.

2007-03-12 19:12:51 PM
450
PingbackServerError:
System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at CookComputing.XmlRpc.XmlRpcClientProtocol.GetWebResponse(WebRequest request)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, String methodName, Object[] parameters)
at CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(String MethodName, Object[] Parameters)
at newtelligence.DasBlog.Runtime.Proxies.PingbackClientProxy.ping(String sourceUri, String targetUri)
at newtelligence.DasBlog.Runtime.BlogDataServiceXml.Pingback(String sourceUri, String pingbackService, String pingbackTarget, String entryTitle)
while processing http://thisoldcode.microfisch.com/PermaLink,guid,830a2557-66ad-48e2-ae67-16e2beaccd71.aspx,http://blogs.zdnet.com/microsoft/?p=315.

When DasBlog throws up, it really does a number on your shoes.