Biztalk 2006 - Determine Encoding (Flat File Disassembler Algorithm)

I read in following links:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/BTS06Developing/html/0dbe24fb-c431-4edf-8aa9-4c040d6a7b32.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/BTS06CoreDocs/html/3ea69942-7642-4cd8-befe-63d170eafd4f.asp

That the order to determine the character encoding for a given instance
message in disassemble stage is (without worry about BOM):


1º) If the "Charset" in the body part is set, use it.
2º) If the envelope (or document) schema specifies a code page, use
it.
3º) UTF-8

If we want that Flat File Disassembler uses Charset property of BodyPart, we have to set this property previous the Flat File Disassembler Component call Probe method. I
think this doesn't happen in Biztalk 2004....

Windows Workflow Foundation Beta 2.2 Error - "Procedure or function InsertWorkflow has too many arguments specified"

When we have one of the next errors:

"Procedure or function InsertWorkflow has too many arguments specified."

"ActivityEvents 'sqlTrackingWorkflowInstance.ActivityEvents' threw an exception of type 'System.Data.SqlTypes.SqlNullValueException' System.Collections.Generic.IList {System.Data.SqlTypes.SqlNullValueException}"

We have to update our Tracking Database:

1º) Drop the old Tracking Database.
2º) Copy the new sql scripts from C:\WINDOWS\WinFX\v3.0\Windows Workflow Foundation\SQL\EN with the other scripts.
3º) Create again the Tracking Database