March 2009 Entries

Windows Workflow: Debugging Limitations.

In Visual Studio Debugger for Windows Workflow Foundation you MUST set the workflow DLL project as the Visual Studio solution startup project to debug the workflow using F5 Documented in It is not intuitive restriction. I've posted to MS Feedback that it will be good to support workflow Debugging from any startup project. Recently I've noticed, that if workflow DLL project is a startup project, it doesn't support Edit&Continue in a code dlls. ......

ASP.NET Conversion to WAP bug - autoeventwireup Changed to True

When ASP.NET page converted to WAP, it changed autoeventwireup to True- see autoeventwireup Changed to True in C# Conversion to WAP discussion. Autoeventwireup is easier for coding, but there are disadvantages(according to MSDN): One disadvantage of the AutoEventWireup attribute is that it requires that the page event handlers have specific, predictable names. This limits your flexibility in how you name event handlers. Another disadvantage is that performance is adversely affected, because ASP.NET ......

TryXmlSerialize function

I was using XmlSerialize method from a while.Recently I found that sometimes it's safer to use TryXmlSerialize: /// <summary> /// Serialize an object into XML /// </summary> /// <param name="serializableObject"&g... that can be serialized</param> /// <returns>Serial XML representation</returns> public static bool TryXmlSerialize(object objectToSerialize, out string strXml) { bool bRet=true; ......

Windows Workflow: Use of ConditionedActivityGroup activity

One of our developers used ConditionedActivityGroup activity with a single branch. ConditionedActivityGroup is a kind do of loop, but it should not be used instead of the WhileActivity. There are a few reasons for this: 1.Use the simplest tool that satisfy your requirement 2.workflow designer doesn't expand body of ConditionedActivityGroup, and you need to click it to Preview 3. If you have many activities in the workflow, the designer becomes terribly slow(VS 2008) The huge workflows should be considered ......

Remoting asyncronous call to fire and forget

I want to do .Net Remoting asyncronous call with "fire and forget" approach. MSDN statement in OneWayAttribute Class documentation is not clear "The method can execute synchronously or asynchronously with respect to the caller." Thanks to manish godse's blog : OneWay messages in remoting post: invoking a method with [OneWay] attribute the client will not wait for a response and the call will return immediately. In essence the call gets converted to an async call and the client doesnt wait for a server ......