11 March 2003

This sounds familiar to me... Maybe I will get broadband after all. Customers in Scotland are going to get broadband through their electrical sockets, maybe one day I will be able to get broadband after all :O) http://www.brandrepublic.com/digitalbulletin/news_story.cfm?articleID=173397&;Origin=DB10032003 [Wibbleshanks - ASP.NET UK New Media] I used to work for a company called RMS Communications that was developing the technology to read electricity meters over power lines for Scottish Hydro. We went all the way to the substation though, and it looks like this is just internal to the house. We went bankrupt though, it was a stupid idea. I wonder if any of my old collegues are involved in this one... What other blogs are saying about this post. 11:32:11 AM    comment []  trackback []

Profilers Free NET Profiler. Reflection is a wonderful thing. With it, you can keep track of exactly what your .NET application is doing. This opens up the possibility of some very interesting tools, of which nprof, a freeware, open-source .NET profiler, is one. nprof is quite simple to use. Browse to the application you want to run, supply any command line, click the Start button. (There's also a VS .NET add-in version of nprof, for tighter integration with a single version). Then just work your application as you usually would. When you're done, close the application and nprof comes back and shows you which methods were called, how many times they were called, and what percent o the total calls and total time they were responsible for. One nice touch is the treeview of namespaces, which lets you filter the list down to only the calls that you're interested in. Of course you can also sort everything. Like any other profiler, nprof will help you drill down on problem code in your application; unlike many of them, it's free. [Larkware News] Here's another one of those things that looks really cool, but I haven't had a chace use yet. I wonder if it works with web apps. I had tried to get two similar tools to profile ASP.NET applications, but I could not get either to work correctly (or at all). [ScottW's ASP.NET WebLog] It's easy (ish). To debug ASP.NET you need to set an environment variable for the process. Take a look at the tools developer guide in the framework sdk tools folders. It contains a file on profilers that explains how to do it. What other blogs are saying about this post. 10:34:03 AM    comment []  trackback []

© Copyright 2004 Jon Shute.