Mark Cliggett's WebLog

A Whidbey Wiki?

There's a fair amount of interest in wikis in the Developer Division.  Several of us have been bouncing ideas around for where we could experiment with wikis in our interactions with people outside the company.  I wanted to put one idea out and see if there's interest (or if it Just Happens :-)) - a Whidbey wiki along the lines of Wikipedia only focused on the Whidbey release.  I can see it starting as a simple dictionary/glossary, describing terms or new features, but it could expand in a lot of ways - detailed descriptions of how things work under-the-covers, some higher-level explanation of the user scenarios Whidbey enables (including gaps/issues in those scenarios).  I would expect a significant portion of the content would come from the community, but I know there would be numerous people inside MS contributing as well (and I would encourage the rest). 

Would people see value in this?  Is there anyone out there who is eager to put this infrastructure in place?  If so I'd love to work with you to make this successful.  There is the potential for making this happen inside the company, but lots of people get involved, they have (legitimate) concerns about things like vandalism, there are questions about whether wiki is the best approach, etc..  Your feedback will be helpful in figuring out how much energy to spend on this, and maybe it will come from the community instead - like pdcbloggers or longhornblogs. 

Published Thursday, February 26, 2004 2:57 PM by markcli

Comments

 

Scott said:

I had started this (http://aspnetv2wiki.scottwater.com/) and would be willing to host it, but I have not had time to promote or really get it going.

-Scott
February 26, 2004 3:14 PM
 

Travis Chase said:

I think this is a great idea. I love the Wiki format. This would give the ability for developers outside Microsoft to add information without toting the company line.
February 26, 2004 3:26 PM
 

MasterMaq.NET said:

March 1, 2004 7:41 PM
 

Chris Garty said:

This is a wonderful idea for creating an emerging resource. It could become many things at once; a living FAQ resource, a source of links to articles, and a point of reference out to the wider community with references to blogs and websites. It would also be great for storing asynchronous creator-user conversations for others to see.

You can always have an 'editor' screen the posts and revert versions if you are worried about 'wiki spam'.
March 3, 2004 10:34 AM
 

Robert said:

Scott's site seems very focused on ASP.NET. What we need is a general purpose Visual Studio Whidbey wiki. Personally I consider the application development side far more interesting than ASP.
April 2, 2004 6:17 AM
 

Amr Essam said:

I develop with both C# and VB.NET, but I like VB.NET to be better because I am old VB developer.
I just installed VS.NET 2005 (Technology Preview), and this my prompt feedback

-----------------------------------------------
I surprised that I found productive feature in C# and not
in VB.NET, this features:

1) Refactoring
I tried Refactoring in C#, It is really very productive
feature.

2) IntelliSense/Auto Completion (Keywords)

Now only in C# debugger feel the Language keywords like
(private, public, foreach ...), and auto complete it to
you.

However VB.NET have longer Keywords such as (MustInherit,
NotInheritable,.)

-----------------------------------------------
I dreamt that I can find these features in VS.NET, but
unfortunately I frustrated when I found this feature in C#
not VB.NET :(

Microsoft always say that it concentrate on Productivity
features in VB.NET, How does VB.NET 2005 lack these
very productive features ?!

Looking forward for your reply.

Amr Essam
www.Verizon.com
Consultant & Team Lead
MCSDT + MCT
Dallas, Texas
amr_essam@yahoo.com
May 15, 2004 3:31 AM
Anonymous comments are disabled

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker