Posted By: Mike Sampson | Aug 16th, 2006 @ 9:12 AM | 32,722 Views | 22 Comments
Channel9 started as Community Server and FlexWiki but has grown to a lot more. When we started working on10, the goal was to create a new site as well as a stable, extendable code base that we could grow all our communities on. That project is called EvNet and this is the dev team behind it. We dive in to how this all works as well so take a look.
Media Downloads:
Rating:
1
0
erik_
erik_
Tablet Power
Nice, a behind the scenes on channel9 Smiley

Thanks!
TommyCarlier
TommyCarlier
I want my scalps!
This is an awesome video with great technical content.
Looking forward for Channel 9 vNext Smiley

Any history behind "EvNet" Name? [A]
jeffsand
jeffsand
Inch by Inch
ali_raza_shaikh wrote:
Any history behind "EvNet" Name?


The team that creates Channel 9  and 10 is sits organizational in the Evangelism group at Microsoft.

We look at Channel 9 and 10 as a growing part of an overall network of sites.  So the team is known internally as The Evangelism Network Team.

-Jeff
Larsenal
Larsenal
ready to give an answer
Three cheers for the Providers in ASP.NET 2.0!  It's really foundational to the new types of frameworks you can construct.

Great video, guys!  Keep 'em coming!
W3bbo
W3bbo
The Master of Baiters
The video mentions having to sanitize the raw HTML input from the Rich-Edit controls into some variant of XHTML.

Thing is, wouldn't an alternative approach be better? If I was in charge of C9, I'd have everyone use Markdown or some other WYSIWYM (not G) content definition language in the boring <textarea></textarea> element. This makes everything simpler with zero loss of functionality (unless of course, you're the sort that likes WYSIWYG)
HumanCompiler
HumanCompiler
Compiling humans...and code
W3bbo,

I made the Rich Text Box for our code base (it's actually not done, but getting there).  Sometimes Duncan and Adam just go on and on talking...you know...  Wink  I honestly am not sure where Duncan got going about that.  The goal of the RTB I made was to keep things simple while staying XHTML compliant so we don't have to do any filtering after the fact.  The only problem with that approach is you basically have to write some javascript to go through and make sure what's being pasted is xhtml compliant and either clean it or reject it (either that or only allow plain text to be pasted, which is limiting, but keeps the code simple and small).

I'm not sure exactly I follow what you're saying.  Could you go into a bit more detail?

Edit: Actually, after reading what you said again, I think I get it.  You mean to just use plain text and mark it up?  Like UBBCode?  (I think that's the name)
W3bbo
W3bbo
The Master of Baiters
HumanCompiler wrote:
Edit: Actually, after reading what you said again, I think I get it.  You mean to just use plain text and mark it up?  Like UBBCode?  (I think that's the name)


Similar, but Markdown is probably the best implementation of plaintext markup for documents.

As for the Rich-Edit control, what you've done has already been done Wink Check out widgEdit, it filters out "bad" HTML and looks good too.


HumanCompiler
HumanCompiler
Compiling humans...and code
W3bbo wrote:

HumanCompiler wrote: Edit: Actually, after reading what you said again, I think I get it.  You mean to just use plain text and mark it up?  Like UBBCode?  (I think that's the name)


Similar, but Markdown is probably the best implementation of plaintext markup for documents.

As for the Rich-Edit control, what you've done has already been done Check out widgEdit, it filters out "bad" HTML and looks good too.




Well, we'd like to get away from using codes.  If it's a huge request we'll go to it, but otherwise we're trying to keep it simple and make it not much different than using Word or whatever.

Yes, I know what I'm doing has been done.  We looked at a few RTB's and actually used one for a while, but none have really met our needs so we opted to build our own.  We figured it was ok since we weren't doing anything that advanced.
Microsoft Communities