Debug And Fix You

Wrong:

The list controls – radiolist, dropdownlist- that come part of asp.net 2.0 has an event called OnSelectedItemIndexChanged. In this event we can capture the event when an item in the list control changes its index. There seems to be bug in this event handling. This event is called twice even though a single item is clicked. This is because the page is sent to the server for both deselect of the previous item and select for the new item, and not simply select. The eventargs parameter does not have any indication that the item was selected rather than deselected. The sender parameter does not say the name of the control it is working with. To get around his problem, we can derive a new list control from the asp.net control and override the OnSelectedItemIndexChanged event.

Right:

The OnSelectedItemIndexChanged was called twice because it was invoked twice. The trap was the keyword AutoEventPostBack to set to true as well as wiring of the event through Handles event (in vb.net). This forced two calls rather one.

Which is more soa? The WCF is. The SOAP is exposed through an asmx page. This runs only on asp.net platform. There is overhead with this implementation. The WCF has a unified approach. The wcf does not have to run asp.net. Interface programming is hard with web services. The SOAP web services exposes web methods, so the developer has to start with an Interface and then implement a concrete class. The WCF always starts with a service.svc and generates interface. The WCF has more soa than SOAP web services, and is a better middleware. This has helped the application server (IIS, Apache) to fulfill it’s dream to implement a middleware. Applying security in the binding is easy in WCF while WS needs to implement the WS* extensions to do that. The WCF can be hosted anywhere unlike SOAP XML web service which requires a IIS. In WCF, we can have our own custom binding and use a separate data contract parser.