[.Net]Debug client script in VS2005

To debug client script in VS2005, You have to first enable Script debug in IE.

From IE's Tools menu, select Option, switch to Advence tab, Under the Browse tree node, uncheck [Disable Script Debugging(IE)] and [Disable Script Debugging(Other)], then open your web application from VS2005

1. First press F5 to run your web application in debug mod
2. From Debug menu item, select Window, then Script Explorer, this bring up a Script Explorer window
3. From the explorer window, choose the script source you like to debug and add break point on the it

[BizTalk]When configuring BizTalk Accelerator for RosettaNet receive error messages

When configuring A4RN 3.3, I got an error message like this:

A Biztalk Isolated host instance configured with the user account was either not running or dose not exist...

This error occurs if when you installing A4RN, there are no trusted host instance configured on your box, hence A4RN installation process could not pick up a trusted user account for further configuration.

The only way I found to solve this error is to uninstall A4RN, then create a new host marked as trusted, the create a new host instance of that trusted host. Then in BizTalk Server Administration consol, I mark the newly created host instance as default host instace.

After all was done, then I reinstall A4RN. And now when configuring A4RN, no compliant will be shown.

In my opion, this is really stupid, they should have ask us for a new trusted user account, not just popup a error message.

[.Net]Stepping thru a unit test generates MDA FatalExecutionEngineError

I got this error message while implementing a CASmf client in C#. The error occurs while the client tries to invoke a CASmf WIN32 API casmf_recv().

So I google for a while and found this error only occurs in the following situation:

1. When we are interop debugging. For example when you are invoking Win32 APIs from managed codes
2. When does a "property eval" of a method that contains a breakpoint. For example when you are "watching" some variables in the debugger.

I totally match above situations, I am interop debugging and there IS a breakpoint on it. So I simply remove the breakpoint, and the clinet works fine.

There are 3 workarounds to this problem:

1. Remove breakpoints
2. Disable automatic property eval(ToolsOptions menu in VS2005). Remember that VS automatically calls ToString() method and property getters, so when your watch window is opened, or when you quick watch the code, this will happen.
3. Use managed debugging only

[BizTalk] Cleanup MessageBox

To cleanup unprocessed messsages in message box, BizTalk Server provides a SQL stored procedure.

Here're steps to cleanup unprocessed message:

1. Do IISRESET.
2. Stop all BizTalk application and host instances
3. Open SQL server management console, browse to [BizTalkMsgBoxDb].
4. Execute bts_CleanupMsgbox stored procedure on BizTalkMsgBoxDb
5. Execute bts_PurgeSubscriptions stored procedure on BizTalkMsgBoxDb
6. Restart Biztalk server

Now your messages are deleted. And you have a emppy message box now :)