The opinions expressed in these materials are my own and are not necessarily those of Microsoft.
Copyright © Microsoft Corporation. All rights reserved. Unless otherwise indicated, all source code provided is licensed under the Microsoft Public License (Ms-PL).
Updated: March 28, 2003
This command-line tool allows a system administrator to monitor packets on a LAN and write the information to a log file. NetCap uses the Network Monitor Driver to sniff packets on local network segments.
This tool provides a command-line interface to some of the capture functionality of Netmon.
NetCap captures frames directly from the network traffic data stream so they can be examined. You can use it to create capture files for support personnel.
Frames are packages of information transmitted as a single unit over a network. Every frame follows the same basic organization and contains the following:
NetCap requires one of the following operating systems:
I absolutley LOVE the ThinkBalm folks and they have some great stuff going on. If you are into virtual worlds and want to come hang with other like-minded folks then check it out at:
If you want a glimpse of what we are doing there, here is where you can find the article describing the goings on:
Things are off and running at the Virtual Worlds Conference and Expo, LA and sadly I am not there. At least I can read about it in Tish's great articles. Check out her latest at:
This post inspired by a conversation between Sean W. and me the other day...
This How To shows you how to use the CLR Profiler tool to investigate your application's memory allocation profile. You can use CLR Profiler to identify code that causes memory problems, such as memory leaks and excessive or inefficient garbage collection.
CLR Profiler enables you to look at the managed heap of a process and investigate the behavior of the garbage collector. Using the various views in the tool, you can obtain useful information about the execution, allocation, and memory consumption of your application.
CLR Profiler is not a starting point for analyzing problems. Rather, it helps you identify and isolate problematic code and track down memory leaks. Using CLR Profiler, you can identify code that allocates too much memory, causes too many garbage collections, and holds on to memory for too long.
Note CLR Profiler is an intrusive tool that causes your application's performance to be significantly slower than normal (somewhere between 10 to 100 times slower). The tool is not designed for use in production environments.
CLR Profiler is downloaded as a self-extracting executable file. The expanded contents include the source code and the executable file (CLRProfiler.exe). The download also contains a comprehensive document that provides detailed information on CLR Profiler.
Session 1: Demystifying WPF
Today’s applications need to do more than simply work. They need to draw in the user, and provide a differentiated experience. This means moving beyond battleship gray forms, boxy UIs, and providing a positive user experience. Windows Presentation Foundation (WPF) provides powerful capabilities to develop a compelling user interface, the kind that makes an application stand out. In this session, we’ll examine the core concepts of WPF such as layout panels, data binding, styles and control templates, and we’ll use them to develop an application UI from the ground up.
Session 2: Developing Applications with Visual Studio 2008 and .NET Framework 3.5 Service Pack 1
Service Pack 1 and Visual Studio 2008 introduce a wide variety of new features for targeting Windows, Office and the Web. This includes more controls, a streamlined setup, improved startup performance, fresh graphics features, improved AJAX support, and much more. We’re also introducing the ADO.NET Entity Framework and ADO.NET Data Services, which are designed to simplify application data access by providing an extensible, conceptual model for data from any source, while enabling this model to closely reflect business requirements. Don’t miss this lively session and learn how to use these powerful new features in your applications.
WHO SHOULD ATTEND?
Anyone who designs, develops, or debugs code. If you are an architect, developer or just enjoy curly braces, join us.
WHERE ARE THE EVENTS?
Events are held in 12 cities across Central Region. To register for this event, please select a link below.
9/10/08 Nashville TN
9/16/08 Downers Grove IL
9/17/08 Indianapolis IN
9/23/08 Irving TX
9/23/08 Waukesha WI
9/24/08 Houston TX
9/25/08 Austin TX
9/30/08 Southfield MI
10/2/08 Columbus OH
10/7/08 Chicago IL
10/7/08 Mason OH
10/9/08 Cleveland OH
WHAT TIME ARE THESE EVENTS?
1:00pm – 4:00pm
Saw this on my buddy Keith Combs' site and thought it would be cool to share...
This is just stuff that popped into my head this morning:
Alabama 3: Exile on Coldharbour Lane
Woke Up This Morning (not the crappy Soprano's version that almost ruined this song for me)
Mao Tse Tung Said
Speed of the Sound of Loneliness
I mentioned this on my webcast yesterday but I wanted to do a post about it as well. I recently found out that I have 5 of the top 10 webcasts at Microsoft http://www.microsoft.com/events/top10.mspx. To say that is an honor of epic (or, for my WoW players, epic mount) proportions is an understatement. I just wanted to say a deeply heartfelt
for putting up with my rants and making the New Features of Visual Studio Series a resounding success! You all rock!
Finally available to the public!!!! Check this out:
Source Analysis is similar in many ways to Microsoft Code Analysis (specifically FxCop), but there are some important distinctions. FxCop performs its analysis on compiled binaries, while Source Analysis analyzes the source code directly. For this reason, Code Analysis focuses more on the design of the code, while Source Analysis focuses on layout, readability and documentation. Most of that information is stripped away during the compilation process, and thus cannot be analyzed by FxCop.
The ultimate goal of Source Analysis is to allow you to produce elegant, consistent code that your team members and others who view your code will find highly readable. In order to accomplish this, Source Analysis does not allow its rules to be very configurable. Source Analysis takes a one-size-fits-all approach to code style, layout, and readability rules. It is highly likely that you will not agree with all of the rules and may even find some of the rules annoying at first! However, the majority of teams using this tool within Microsoft have found that after a short adjustment period, they came to appreciate the rules enforced by Source Analysis, and even began to find it difficult to read code not written in this style.
Get it. Got it? Good :)
For my victims at EDS :)
.NET Framework Learning Resources
WCF Tools in VS2008
Creating, Configuring, and Consuming a WCF Service in IIS 7
Intro to WCF
VS2005 Extensions for WCF
WCF Service Bus
Debugging WCF Services