Scott Hanselman

Thanks To Everyone Who Attended My Talk At The A Hrefhttp

September 27, '02 Comments [2] Posted in Web Services | Speaking | Bugs | Tools
Sponsored By

Thanks to everyone who attended my talk at the Portland Area .NET Users Group on Thursday on the .NET Compact Framework.  Here's some pointers to follow up information, as well as some of the utilities I used during the talk.

  • Most of the the code and presentation can be downloaded from PADNUG's Presentation page.
  • The Remote Display tool for seeing a Pocket PC screen on your desktop over TCP/IP is a Microsoft PocketPC Power Toy.
  • A version of Zoomin, the screen magnifier, is included with Visual Studio 6.0, but there is a freeware version from Brian Friesen.  Both are great, and I actually prefer the flexiblity of Brian's.
  • The .NET IL Disassembler is called ILDASM.EXE and if you have the .NET SDK, this is installed on your system already in the Framework's BIN directory.  It's your best friend.
  • The AskDotNet Survey application is available from GotDotNet including source in C# or in VB.NET
  • The SOAP tracing tool I used is the fantastically useful YATT from Simon Fell.
  • It looks like the .NET CF Beta 1 is closed, so you'll have to talk to your beta-friends to look at it. 

Rest assured though, it will be included in the next (very soon) version of Visual Studio.NET...check out the roadmap.

I'll be speaking next at the Software Association of Oregon's Developer SIG, probably on Wednesday November 20th, so join me there!  Details will be posted soon.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by SherWeb
Monday, 30 September 2002 17:15:08 UTC
Why are dotNET developers apparently so taken with the disassembler?

Tuesday, 01 October 2002 00:32:47 UTC
I'd say it's probably because the "sealing" point of .NET is so much higher than with COM, that .NET developers (myself included) take comfort in looking at IL. It's a way of reminding oneself of the transparency of the .NET CLR and Framework. ILDASM is a way to look and say, "Hey, that's not magic!"
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.