Wednesday, March 14, 2007

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

posted by Aaron Fischer on Wednesday, March 14, 2007 6:05:25 PM (Pacific Standard Time, UTC-08:00)   #    Comments [0]

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

posted by Aaron Fischer on Wednesday, March 14, 2007 3:31:25 PM (Pacific Standard Time, UTC-08:00)   #    Comments [0]

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.

posted by Aaron Fischer on Wednesday, March 14, 2007 5:48:05 AM (Pacific Standard Time, UTC-08:00)   #    Comments [0]
 Tuesday, March 13, 2007

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.
posted by Aaron Fischer on Tuesday, March 13, 2007 9:11:03 AM (Pacific Standard Time, UTC-08:00)   #    Comments [0]

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

posted by Aaron Fischer on Tuesday, March 13, 2007 7:25:14 AM (Pacific Standard Time, UTC-08:00)   #    Comments [0]
 Monday, March 12, 2007

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.

posted by Aaron Fischer on Monday, March 12, 2007 7:28:27 PM (Pacific Standard Time, UTC-08:00)   #    Comments [2]

Is it possible sites like Worse Than Failure do more harm then good to our Development community?   I caught and episode of  TWit today  and an interesting idea emerged could the open source community be stiffed because programmers are worried they would be publicly ridiculed for what they publish?  I know its hard to believe with episodes such as our recent FizzBuzz: the Programmers's Stairway to Heaven were almost we see almost all readers opening them selves to public ridicule by posting adhoc solutions to FizzBuzz 

While  The daily WTF is fun, it must strike fear into the hearts of programmers everywhere what if my code/project shows up?   We've all had our moments of writing poor/lazy code.  What happens when this gets out, do programmers have ego's to damage?  It seems the typical programmer is quite the  introvert.  So what would this type of public mockery affect you?  Would you keep your ideas to your self? would you avoid help to avoid criticism?

Its not only Large web sites that lambaste the programmers for humor.  No you need only browse over to your favorite forum where you can see  people ridiculed for asking questions some one else has deemed childish or stupid.  What breads this type of hostility in our community?  Is it just human nature or some thing else?

posted by Aaron Fischer on Monday, March 12, 2007 7:21:36 PM (Pacific Standard Time, UTC-08:00)   #    Comments [0]

Mary  Foley blogs Microsoft builds a ‘MySpace for financial pros’

I'll be interested to see whether this site gains much traction. Corporate controllers and accountants don't strike me as folks who have a lot of time or interest to blog, chat and share photos and play lists.

It seems they do if you look at Mortgage Grapevine.  Many people are contributing questions and answers it looks like they may have a need for their space.  The real question is will  Microsoft's(Microsoft Dynamics Live Beta Community) start up site have the traction to draw traffic away from the Grapevine and BrokerOutpost?

posted by Aaron Fischer on Monday, March 12, 2007 7:12:42 PM (Pacific Standard Time, UTC-08:00)   #    Comments [0]
 Sunday, March 11, 2007

VS Live is the best opportunity I get to learn Microsoft's new technology.  There are to many tracts and I would like to attend them all.  Today I am trying to pick a pre-Conference

Build Distributed Object-Oriented Apps in .NET 3.0

or

SQL Server 2005: Power to the Developer

or

Making the Tough Choices: Selecting the Right Techniques for Your Application

All very interesting but none match verywell to what I am working on.  I think its time to pick of a coin and start fliping. 

posted by Aaron Fischer on Sunday, March 11, 2007 3:13:12 PM (Pacific Standard Time, UTC-08:00)   #    Comments [0]
 Friday, March 09, 2007

The BBC reports today

Internet phone company Vonage has lost a patent case that could threaten phone services for its 2.2 million customers. Full Story

posted by Aaron Fischer on Friday, March 09, 2007 7:28:58 AM (Pacific Standard Time, UTC-08:00)   #    Comments [0]