In a few months MicrosoftDotNet will be celebrating its fourth year of existence. A new version DotNetFramework, supported by VisualStudioWhidbey will become a reality.  And major enhancements in CsharpLanguage and VbDotNet is expected as well.

Presumably DotNet will be "coming of age" soon, now that Whidbey has reached "Released to Manufacturing" RTM status. 

Within the new "Enterprise version" of VisualStudioWhidbey (called Team Foundation server) there are supposed to be two SDLC process templates. These are:
* "MSF for Agile Software development"
* "MSF for CMMI Process Improvement"

The above information taken from Jun05 blog at http://blogs.msdn.com/vstsue/articles/429078.aspx, and represents what the vendor thinks the users and managers of the DotNetPlatform needed.

----
Has the DotNet community gravitated towards any systematic approach to addressing the SystemsDevelopmentLifeCycle yet? I am interested in information on what "system development method(s)" are in use in small to medium inhouse DotNet shops. -- DavidLiu

I'll offer two nearly insignificant data points from the DotNet community, whatever that is:
* Personally, as an occasional user of VisualStudio DotNet, I couldn't care less.
* I recently discussed development methodologies with a colleague who is a strong proponent of DotNet.  His tongue-in-cheek response (slightly paraphrased) to my mention of using XP was, "Huh?  What's wrong with using the 'methodology' called 'just get on with it?'" ''Answer: I am seeking TheRoadMapToRepeatableSuccess. Need a mechanism to apply ProjectManagement techniques.''
----
CategoryDotNet CategoryDiscussion aiming for CategoryMethodology and CategoryEnterpriseComputingConcerns later