During November Microsoft’s Ron Cundiff will be presenting a series of four “Soup to Nuts” webcasts in which he discusses the basics of using ASP.NET to create your first Web applications. More advanced developers are encouraged to check out the Webcasts page to register for upcoming presentations on ASP.NET, AJAX, Silverlight, IIS, and SQL Server.

We talked for most of the time about Version / Revision Control systems with James giving a quick (un-timed :) ) intro of Mercurial. Here are some of the other products we talked about:

Version / Revision Control Systems:

Mercurial: http://www.selenic.com/mercurial/
SVN: http://subversion.tigris.org/
Team Foundation Server (TFS): http://msdn2.microsoft.com/en-us/teamsystem/aa718934.aspx
Visual SourceSafe : http://msdn2.microsoft.com/vstudio/Aa700900.aspx
GIT: http://www/git.or.cz/
DARCS:  Could not find

Products discussed:

TRAC: http://www.trac.edgewall.org
JumpBox: http://www.jumpbox.com

Future Events (some in planning):

BarCamp on Dec 8th: http://www.barcamp.org/BarCampPhoenix
DevHouse: Just starting the discussions on it.

I had a short video that I needed to share with family this weekend so I thought I'd try out the Silverlight streaming service that's currently free. I started out with this guide Your Video to Silverlight Streaming 101 which seemed pretty straight forward....(read more)

Is it easy to learn database programming in .NET? Find it out by reading Anand's review of the latest book from Murach Publishing. Click here to read full review http://www.amazon.co.uk/exec/obidos/ASIN/1847190871/ http://www.amazon.com/exec/obidos/tg/detail/-/1847190871...(read more)

Learn how ASP.NET 2.0 makes it simple to implement Web site navigation by combining Menu and TreeView server controls with SiteMap data controls. Also discover how to associate client behavior with a server control using the ASP.NET AJAX extender framework.

The Beta of ComponentArt Web.UI version 2007.2 for ASP.NET is now available for download and testing. This release - one of ComponentArt's most significant to date - adds a groundbreaking new Editor control that overcomes browser inconsistencies and delivers uniform XHTML output. Also new in this release is an advanced SpellCheck control that may be used in concert with Editor, or independently with other controls. Bringing the total number of controls in the Web.UI suite to 18, the beta release is available in builds for ASP.NET 1.0, ASP.NET 2.0 and ASP.NET AJAX.

Download now from http://www.componentart.com/

http://www.amazon.co.uk/exec/obidos/ASIN/1847190871/
http://www.amazon.com/exec/obidos/tg/detail/-/1847190871

Using CSS, Javascript to Fixed Gridview's Header and Footer

I was doing was troubleshooting recently and apart from looking @ DebugDiag, came across the below post from Steve.

http://blogs.orcsweb.com/steve/archive/2006/07/08/Troubleshooting-process.aspx 

The blog lists some of the "Usual Suspects" when trying to trace down a unexpected crash/hang symptom

Here is one more link

HTH.

Thanks,
Deepak

 

 

 

I recently received a comment in my Truly Understanding ViewState article about the "ArrayList of controls in the control hierarchy that need to be explicitly invoked by the page class during the raise postback event stage of the life cycle." Such is the 3rd entry in the master Triplet that makes up ViewState as a whole. It was a very excellent question, and in some quick searches I don't see any really clear topics dedicated to answering it, so I decided to answer it with a blog post rather than...(read more)

A simple Windows framework that beginners and intermediate programmers can use as an alternative to MFC. It makes learning to program for Windows easier.

Oren has one of the best one liners about the benefits of Inversion Of Control Containers in a project in this post:

 

"Other people on my team keep adding components, and they aren't even aware that they have IoC there. They just know that if they put the IFooService in the ctor, they will get it when the code is running. And if they add IBarService and BarServiceImpl, they will be available to any component that uses them."

Here's a quick "Getting Started" if you've never seen this before, using the Castle Windsor Container Framework for .NET.

This article discusses how to create an HTML Editor server control for use within an ASP.NET AJAX 1.0 environment.

The .NET Framework 3.5 is shipping later this year at the same time as Visual Studio 2008. The .NET Framework 3.5 is an additive release, meaning that it adds functionality in terms of classes in assemblies to the previous versions 3.0 and 2.0 of the...(read more)

Multicore hardware is spreading very fast, however the programming for Multicore is not an easy job, Parallel FX (PFX) comes to rescue

The decorator pattern meets reflection in a workaround to enable SSL for ASP.NET Health Monitoring e-mail Event Providers.

 

I saw this handy little helper function being used on a MOSS screencast by Todd Bleeker and decided to figure out how he did it :). Basically it allows you to view the public key token of an assembly from within Visual Studio's output window, which saves time when you need to grab the key for use with the safe control entries in the web.config for example.

First step, fire up your copy of Visual Studio 2005 and open up a webpart class library project. Then from the Tools menu select External Tools. This will bring up the following dialog:

 

From the options, click Add and then give your utility a title. Now all we're doing here is essentially grabbing the output from the sn.exe command, so you will need to provide the path to your local sn.exe file. Mine was located in the following folder:

C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe 

Now, just like if we were running the strong name utility from the command line, we're going to need to pass in the correct arguments. Firstly we'll need to pass the -Tp argument, as we want to get the token for the public key, together with the public key itself. Then we need to specify the target assembly, which can be done by clicking on the button to the right of the Arguments field and selecting 'Target Path'. This basically gets the full qualified path to item which is being built, in our case a webpart assembly. Lastly just tick the 'Use Output Window' checkbox and then click ok and you're good to go :)

The new utility you've just created should now show up in the Tools menu, you can go ahead and click it and you should now see the output window popup with the details of the public key. This is a really nice feature of Visual Studio and I'm sure this can be tailored for many other uses.