Post New Web Links

Debugging Asp.net application using XML Serialization

Posted By: Farrukh Abbas Posted Date: August 10, 2011 Points: 2 Category :ASP.Net

Debugging on Test or Production server is very difficult task for developers.First of all developers do not have any rights to touch the Test or Production environment and he received the list of bugs mainly due to data problem on production or Test Server.When developers try to reproduce the bugs on development environment is not possible because data in development environment is according to the developer mind set.

View Complete Post

More Related Resource Links

Tip #107 Did you know . How to improve debugging performance for MVC2 application in Visual Studio 2

VS2010 Ultimate included IntelliTrace functionality by default. IntelliTrace captures events (e.g. exceptions), and can affect performance of debugging. The typical performance hit is about 5% in the default mode (collection can be increased to...(read more)

Application hangs (100% cpu) outside debugger, but when debugging it runs ok.

Be prepared, this is a tricky one. One of my customers he is building a proof of concept using my software components. When running outside the debugger, the application will hang, using 100% CPU in the main thread. At this point attaching the debugger is unsuccessful. When running inside the debugger, the application runs fine. (.NET framework 3.5, Windows 7 Ultimate x86, running in VirtualBox (virtual environment)). Using Process Explorer I've tried to find some hints as to what's going on. Showing a callstack in PE at some arbitrary point when the app hangs is shown at the bottom of this post. The one line that caught my eye was this: halacpi.dll!HalClearSoftwareInterrupt+0x355 I googled around a bit, looks like a number of people ran into this, but nobody had found the true cause of/solution to this problem. One that came close was mentioning a patch for .NET framework 1.1, but there seems no information on later framework versions: http://support.microsoft.com/kb/904705 Some more details from my customer seem to point in the direction of GraphicsPath, which is used quite intensively and I know this class does a fair bit of switching to native land and back (PInvoke, also mentioned in the patch above). We really need to get this one solved, so let me know what to do to get some developer support on this one. Thanks, - Wout ntkrnlpa.exe!KeSetEvent+0x2a1 ntkrnlpa.e

The WCF serialization has a bad performance on 64Bit computer as 64Bit application ?

My application has a bad performance while running on the 64bit computer as 64bit application. And I found the reason is that the WCF serialization of contract took most of the time. The serialization and de-serialization's performance is worse than running as 32bit application on the 64bit computer.

I wrote a demo to record the consuming time of serialization and de-serialization of contract. The application running as 64Bit took about twice time than running as 32Bit application. I don't know why the performance of WCF serialization of contract is so much different between 32Bit application and 64bit application. Has anyone encountered this issue?

the part of demo code:

 public static void Read(DataContractSerializer serializera, MemoryStream stream,string description,int time)
    {
      stream.Flush();
      stream.Position = 0;
      Stopwatch watch;
      using (XmlDictionaryReader reader =
         XmlDictionaryReader.CreateTextReader(stream, XmlDictionaryReaderQuotas.Max))
      {
        watch = Stopwatch.StartNew();

Mouse scrolling works while debugging through IDE, but not when running my application separately...

I have an application with a WindowsFormsHost that is hosting a COM component. When I run my application through the IDE, my mouse scroll events are handled correctly and the control scrolls as it should. However, when I run the application by itself, my mouse scroll events don't do anything. I've tried both Debug and Release builds and they both act the same way....as long as I'm running the app through the IDE, Debug or Release, my mouse scrolls act as they should. Has anybody run into this type of issue?

Debugging web application in ASP.NET is not possible anymore

Hi,

I am using VS2005. My problem is I am not able to debug my web application any more.

I read few posts and tried various things but the problem still persists.

Any idea?

Thanks.

Debugging Dotnet application

Hi All

I am trying to debug my asp.net appliction but cant do it

In my web.config file ihave already set the "debug = true" even then it is not debugging.

Pls help.

Microsoft's Collaborative Application Markup Language (CAML) Loop

discovered an interesting error recently while working with Microsoft's Collaborative Application Markup Language (CAML) that, surprisingly, had received no ink. Partly what surprises me about this is that the error may require you to rewrite large sections of your code if you haven't previously considered this SharePoint limitation. I'll start with some context, but first of all the error is:

Integrating a Legacy Web Application in SharePoint

This month we will continue with the theme of deploying Microsoft's SharePoint as a company intranet by describing a method for integrating a legacy Web application inside a SharePoint site.

In many companies the intranet site is not just a home page with announcements. It houses Web applications used by many different departments. In last month's article, I built a page to search the employee table in Northwind (the sample database included in Microsoft's SQL Server). This month, I will move the Web pages used to add/remove records from the table into the SharePoint intranet.

MVC architecture in ASP.Net using C# and Microsoft Data Access Application block

The Model-View-Controller (MVC) pattern separates the modeling of the domain, the presentation, and the actions based on user input into three separate classes [Burbeck92]:

Model. The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller).

View. The view manages the display of information.

Controller. The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate.

High-Performance .NET Application Development & Architecture

It has always been a goal of project architects to plan an effective strategy from the ground up in regards to an new application. All relevant factors are taken into consideration with respect to the application, from its design and layout to a functional website infrastructure. Pre-.NET strategies and design guidelines still effective now were developed with Microsoft's DNA (Distributed interNet Application) platform. This model successfully served the purpose of architecting N(any number of)-Tier (levels) applications. In its basic sense, as in most robust, distributed applications, you'll architect 3 main layers or Tiers: presentation, business rules and data access.


Categories:

ASP.Net	Windows Application	.NET Framework	C#	VB.Net	ADO.Net
Sql Server	SharePoint	Silverlight	Others	All