ThreadAbortException

January 2006 Entries

Microsoft Architecture Forums - There is one for you now !!!

The Microsoft Architecture Forums is the new venue Microsoft has dedicated to architecture on the Microsoft platform.

This is an excellent source of information exchange for Architects and opens up avenues for discussion and brain-storming chats on Architecture.

Microsoft has been showing increased focus in architecture of late and if you had witnessed the Microsoft Architecture Webcasts, you would agree that there was enough wealth of information discussed.

The Forum can be used as a venue for discussion wherein Microsoft folks, architects, MVPs respond to your queries related to Architecture as well as listen to your suggestions, ideas and concerns.

Check out the Forum at
MSDN Forums.

Cheers and Happy Architecting !!!

MUGH Community Launch & Tech Fest 2006



As the world saw the launch of three milestone products from Microsoft, last year November - Visual Studio 2005, SQL Server 2005 and BizTalk Server 2006, the Technical Communities have their own way of launching them.

The MUGH (Microsoft User Group Hyderabad) has its Community Launch and Tech Fest, a combined rare occasion to meet all Community Leads and also participate in contests, brain teasers, win prizes etc.,


Date: February 4, 2006

Venue: Microsoft Campus, Gachibowli,
Hyderabad, India.

Registration: Free

What you get:

01. Mega Launch of the products in localized fashion by local UG (MUGH)

02. Technical Content + Loads of Fun

03. Exciting Contests and Goodies Galore.

04. Expert UG Leads and MVPs as speakers

05. complimentary Software from Microsoft, Cool INETA and Gotdotnet T-Shirt and many more

For more details and registration, check
MUGH TechFest

Cheers !!!

Visual Studio 2005 "Unable to automatically step into the server. The remote procedure could not be debugged" Error

 

UPDATE : October 16, 2008

There are quite a few useful alternative solutions in case your problem doesnt get resolved after following the steps in this post.  Make sure to check out the alternative options posted by readers in the comments.

You may receive the error "Unable to automatically step into the server. The remote procedure could not be debugged.This usually indicates that debugging has not been enabled on the server." while trying to debug a Web Service.

You may receive the error when you try to step into a Web service method from your Web Application or Windows Application through the debugger. This kind of scenario is prevalent in applications using the layered architecture and one of the layers form a Web service.

To resolve this issue, you just need to add a Web.Config file to the Web Service and set the <compilation debug="true"> in the Web.Config file.

While using Visual Studio 2005, this issue may arise because, by default when you create a Web Application or Web Service, the Web.Config file is not created. It is only created when we try to debug the application for the first time. Usually, we try to debug the application from the presentation or UI Layer which consumes the Web service and hence the web.config file gets added to the UI Layer whereas, the Web Service doesnt have a Web.Config and by default the debug is set to false. To resolve this issue quickly, set the Web Service as the Start up project and a Web Service file (.asmx) as the start up page and start debugging. Visual Studio 2005 would ask whether to add a Web.Config file and enable debug to true. Select that option and continue so that Visual Studio 2005 would add a Web.Config to the Webservice layer and enable debugging.

Thereafter, the Web Service can be debugged from the consumer layer (UI Layer or whichever layer that consumes the service) by setting back the Start up project and Start pages respectively in the consumer layer.

Cheers and Happy Debugging !!!

Quick Facts about Visual Studio 2005 - Did you know?

Visual Studio 2005 ! - Wait !! this might definitely be the tenth time you read this term across today !!!. It, no doubt, has created a wave. A Technology wave which defines new standards for creating applications using the .NET Framework 2.0.

Visual Studio 2005 has improved a lot over its predeccessor Visual Studio .NET 2003. There are some quick facts which are handy for new developers

Visual Studio 2005 (no more ".NET" in the name of the IDE) targets .NET Framework 2.0 for developing Windows, Web Applications, Smart Client Applications etc.,

Visual Studio 2005 doesnt require a recompilation (rebuilding) for changes in the code behind. We can just press CTRL+S (Save) and Voila, you can see the changes.

Visual Studio 2005 treats Windows Applications and Web Applications differently. For a Windows Application, you need to go to File - New Project, whereas for Web Applications, you go File - New Website. The same holds for Open also.


Visual Studio 2005 intelligently asks you for refactoring certain mundane lines of code into reusable methods.

Visual Studio 2005 introduces intellisense everywhere - Now you get the Intellisense popup whether you are in the Source(HTML) Mode or Code-Behind.

You can now drag and drop controls from the Toolbox either in the Design Mode or in the Source(HTML) Mode.

The Web.Config file is not added by default when you create a new Website (Web Application).

The first time you RUN the application, it would popup asking you whether to add a Web.Config and enable the Debug Mode (By Default it is set to false).

The Web.Config file can be hand edited as well as its settings managed using the WebSite Administration Page which ships built-in. You can manage as many things as Authentication, Roles, Users, SessionState etc., from this Tool without manually changing the Web.Config.

Visual Studio 2005 can be used to create complex Class Diagrams and generate code from them. The Diagrams can also be exported for Documentation.

The above is just a sneak peek of the exhaustive list of features.

Visual Studio 2005 comes in different editions such as Standard, Professional, Team System and Express Editions.

To View the features and comparison of the editions, check
Microsoft Visual Studio Developer Center

Cheers and Happy Visual Studio Development !!!

ASP.NET 2.0 - "The target '__Page' for the callback could not be found or did not implement ICallbackEventHandler" Error

Client Script Call Back is one of the coolest features in ASP.NET 2.0. The idea of client side refresh in the data wherein the server side execution happens in Remote scripting is a huge leap towards the scalability of web applications. Remote scripting has been around for quite a while in different forms such as Remote Scripting Core, Ajax, Atlas, Client Script Call Back etc., They all have one basic advantage. In order to communicate with the Server, the page doesnt have to do a postback. This avoids the ugly flash and controls state retaining problem.

While implementing Client Script Call Back, you may receive the error "The target '__Page' for the callback could not be found or did not implement ICallbackEventHandler."

This error occurs, if you miss to specify the ICallBackEventHandler Interface in your Page Inheritance.

The typical Code behind class for an ASP.NET 2.0 Webform looks as below:-

public partial class _Default : System.Web.UI.Page

However, in the case of implementing Client Script Call Back, we also need to specify the Interface as follows:-

public partial class _Default : System.Web.UI.Page, ICallbackEventHandler

This specifies that the page implements ICallBackEventHandler interface and can implement client side scripting call backs to the server side code.

This setting might just be overlooked when we create the page since, the partial class declaration code is added by default and we always resort to start writing our code from the Page_Load event and other events and dont interfere with the auto generated code such as the class definition. The ICallbackEventHandler is not added by default. It has to be explicitly specified as mentioned above.

This would resolve your issue.

Cheers and Happy Programming !!!