ASP.NET Web Services vs .NET Remoting

Over time, it has become common practice to build applications as a set of components that are distributed across a network of machines and work together as part of one overall program. Traditionally, distributed application logic called for component-object technology such as the Microsoft® Distributed Component Object Model (DCOM), the Object Management Group's Common Object Request Broker Architecture (CORBA), or Sun's Remote Method Invocation (RMI). These technologies provided reliable, sca

.NET Remoting vs. ASP.NET Web Services

ASP.NET Web services and .NET Remoting provide a full suite of design options for cross-process communication in distributed applications. In general, ASP.NET Web services provide the highest levels of interoperability with full support for WSDL and SOAP over HTTP, while .NET Remoting is designed for common language runtime type-system fidelity and supports additional data format and communication channels.

Master Memory Management

The .NET Framework changed the rules for managing memory. Whether you come from VB6 or C++, you should learn how your apps can take advantage of these new inner mechanisms rather than work against them. Knowing the details of .NET memory management can make the difference between a sluggish application and a super-fast one; I'll show you several techniques that can help you write optimized code. For starters, I'll review quickly how the .NET memory manager works. When you create a new object,

Improve ASP.NET Application Performance

ASP.NET's Web Forms event model enables you to create interactive Web applications that behave more like Windows applications. They respond to events raised by controls, but unlike a Windows application where the client handles events, ASP.NET handles events on the Web server. Submitting your page to the Web server every time an event is fired impacts the page's performance negatively. You need the ability to create interactive Web pages without requiring a full-page refresh to handle events.

ASP.NET Feature Saves Development Time

ASP.NET provides Web developers with the ability to efficiently handle many tedious tasks that can eat up an application's development time. To be able to effectively maintain state, server controls, and debugging through the Trace object are just a few examples of its advantages. At least 75% of my development time involves gathering a little bit of information from the user, querying the database, and returning some data based on that query. The easiest way to do that usually involves splittin

Performance Monitoring the .NET Way

In the article Introduction to Performance Monitoring I have explained the basic workings of performance monitoring. In the follow up article Monitoring of ASP reading the performance counter in an ASP page was the topic - using a component. In today's article I will show you how much easier it is in ASP.NET using the System.Diagnostics Namespace of the .NET framework. No more external components, more functionality instead. You can even reconstruct parts of the NT performance monitor without

Displaying Performance Monitor Information

In two previous articles - Displaying Information about the ASP.NET Process and How Long has the Web Server Been Up? - I examined how to display system-level information through an ASP.NET Web page. In the first article, information about the ASP.NET process was displayed, while in the second page the time the Web server had been running without a reboot was provided. While both of these articles showed how to provide useful system-level information through a Web page, I hinted in those articles

Performance Tips and Tricks in .NET Applications

This article is for developers who want to tweak their applications for optimal performance in the managed world. Sample code, explanations and design guidelines are addressed for Database, Windows Forms and ASP applications, as well as language-specific tips for Microsoft Visual Basic and Managed C++. (25 printed pages)

Boosting Your .NET Application Performance

Confused about the tiers, performance or scalability of your .NET apps? If so, James has come to the resue with his personal insight, tips and tricks on how best to structure your .NET apps.I often ask other developers which phase of the development process is the most difficult and most important. 90% of the time the answer is the planning and design phase, not the building/programming phase. Then I ask them another question. "Which part of the development phase do you enjoy the most?". Most de

ASP.NET - Application Performance Report

In this tutorial he tell us how to show application performance report.

Optimization Tips For ASP.NET Applications

Although the ASP.NET model has been revised and many new features have been added to enhance the web application development and execution, still there exists the need for optimizing your application performance by keeping the resource utilization to the minimum. Here are some tips for optimization. Disable the session state when it is not required. By default the session state variables are set to true. If not required or being used in your applications, these should be set to false, b

Build a Versatile .NET Code Execution Timer / Logger

When you build ASP.NET applications that have multiple assemblies and a lot of business logic going on, it becomes extremely valuable to be able to trace and log the execution times of various operations within the application, and log them to a file or database where items can be grouped by function, calling assembly, time, elapsed time, method name and so on. This ability gives you the power to isolate and identify bottlenecks in your code, and to know the "real time" execution path your appl

Stress-Test Web Forms and Services With ACT

Matt Odhner's "Web Services Testing Using Application Center Test" Tech•Ed 2002 presentation (DEV343) gave many attendees an introduction to Microsoft's newest ASP and ASP.NET stress-testing tool. If you've ever attempted to set up and run the original Web Application Stress Tool (WAS), formerly code-named Homer, you'll welcome ACT's VBScript macro recording feature and built-in graphing capability. ACT is a Web application and service-capacity planning tool included with Visual Studio .NET

Process Monitor Information Sample

Several people have asked whether there is anyway to remotely identify how an ASP.NET worker process is behaving. Now that ASP.NET has built in memory leak, crash and deadlock detection. ASP.NET automatically track errors and auto-cycle the worker process if necessary. There is no obvious way to tell when a problem occurred. Of course, this is a good thing since it means your users don't know anything went wrong either. However, if you do want to see what the ASP.NET Process Model is doing un

Other ways to stress test

In the last article I looked at stress testing using the Application Center Test (ACT). However, ACT is just a tool that comes with VS.NET and although it can provide a total solution, there are some other applications that can do more. This article will take a look at some of those applications. Microsoft Web Application Stress Tool (WAS) This is another tool from Microsoft and it's like ACT, but you can get it without VS or VS.NET. WAS seems to still be in testing, but I ran it o

Stress Testing : Push your application to the limits

Pushing your application to the limits is something that must be done to an application that will be released in the public domain. This ensures that that application will be able to handle demands without falling over. If you have read part 5 of the WSM series, you will have seen stress testing discussed in relation to the WSM project. This article will look at how to test your application with the Microsoft Application Center Test. What is stress testing? Stress testing is usuall