-
-
IE7 and .net framework are programmed never to request data localhost
Just change the wording Localhost to your machine Name.
this is a better explanation http://www.fiddler2.com/fiddler/help/hookup.asp#Q-LocalTraffic
-
-
the default web service page is a page that reveals a lot of the internal information of the application, this is something that you want to hide.
Warning this does not really secure your web service. may be you should read something like this
<configuration>
<system.web>
<webServices>
<wsdlHelpGenerator href="yourEmptyPage.aspx"/>
</webServices>
</system.web>
</configuration>
just make sure you add a page to your site’s root folder and name it yourEmptyPage.aspx this way whenever someone navigates to your web services URL that page is going to render
-
-
last week end we have faced memory leaks, we had no idea what was the cause of the problem. we were directed by microsoft to use the debugging tools.
this is a quickest possible startup tutorial for that tool.
[Warning] using this tool affects the performance of your applications dramatically please make sure you don’t run it on a production server unless there’s no other way.
- download link
you are looking for “Install Debugging Tools for Windows xx-bit Version”
you’ll be redirected to the download page u’ll need to look for the “current version”
- install the tool
this is probably the only straight forward step in this tutorial
- Copy SOS.dll *
u need to copy this dll from your framework folder
usually %windir%\Microsoft.NET\Framework\v2.0.50727
to your windbg folder
usually %ProgramFiles%\Debugging Tools for Windows (x86)
- Open the WindDbgTool
- Symbol data
to view internals of assemblies you need symbol data the easiest way is to have it downloaded automatically. you can do that by
and typing in
srv*c:\symbols\public*http://msdl.microsoft.com/download/symbols
just make sure you have internet connection so this can be downloaded.
- Get a Memory Dump of your application
well this is another 3 step tutorial
. - Open the Dump
”File”->”Open Crash dump” (if prompted you don’t have to save.)
select the file and wait for the application to be ready
this is actually an option i like as attaching to the process causes the application to be extremely slow and you can always ask your client to create a dump and FTP it to you
- you need to load “SOS”
in the previous window the text box in the bottom is where you’ll type in commands.
the first you need is to load SOS
so type in .load SOS
AND NOTHING HAPPENS, yes there’s no confirmation that the thing was loaded.
- your first Command
now there’s a whole bunch of commands that can be executed from the SOS you can list all these commands by typing in
!sos.help
- need help
and now you can explore the memory dump of your application on your own just consider the hints in the next box.
//!SOS.help <methodName>
!SOS.help DumpDomain
!SOS.DumpDomain
This is just a quick help to get you started. if you need to understand what’s behind this please refer http://blogs.msdn.com/tess/ thank you Tess for the time
-
-
- First you need to download the tool here is the link
- now just install the tool and run it
- then ignore the wizard and go to the third tab in the application UI
right click your process and select create a full dump, the dump is going to be created
now if you need to configure where these dumps are created go to tools –> options and configure the dumps folder.