Wiley Professional DotNetNuke 4: Open Source Web Application Framework for ASP.NET 2.0 978-0-471-78816-4 Manual Do Utilizador
Códigos do produto
978-0-471-78816-4
ASP.NET
The second critical item that Microsoft delivered at this point in time was a community forums page on
the
the
www.asp.net
web site (see Figure 1-2). This forum provided a focal point for Microsoft developers
to meet and collaborate on common issues in an open, moderated environment. Prior to the release of
the forums on
the forums on
www.asp.net
, there was a real void in terms of Microsoft community participation in the
online or global sphere, especially when compared to the excellent community environments on other
platforms.
platforms.
One discussion forum on the
www.asp.net
site was dedicated to the discussion of the IBuySpy Portal
application, and it soon became a hotbed for developers to discuss their enhancements, share source
code enhancements, and debate IT politics. I became involved in this forum early on and gradually
increased my community participation as my confidence in ASP.NET and the IBuySpy Portal
application grew.
code enhancements, and debate IT politics. I became involved in this forum early on and gradually
increased my community participation as my confidence in ASP.NET and the IBuySpy Portal
application grew.
To appeal to the maximum number of community stakeholders, the IBuySpy Portal was available in a
number of different source-code release packages. There were VB.NET and C#.NET language versions,
each containing their own VS.NET and SDK variants. Although Microsoft was aggressively pushing the
newly released C# language, I did not feel a compelling urge to abandon my familiar Visual Basic roots.
In addition, my experience with classic ASP 3.0 allowed me to conclude that the new code-behind model
in VS.NET was far superior to the inline model of the SDK. As luck would have it, I was able to get access
to Visual Studio.NET through my employer. So as a result, I moved forward with the VB.NET/VS.NET
version as my baseline framework. This decision would ultimately prove to be extremely important in
terms of community acceptance, as I’ll explain later.
number of different source-code release packages. There were VB.NET and C#.NET language versions,
each containing their own VS.NET and SDK variants. Although Microsoft was aggressively pushing the
newly released C# language, I did not feel a compelling urge to abandon my familiar Visual Basic roots.
In addition, my experience with classic ASP 3.0 allowed me to conclude that the new code-behind model
in VS.NET was far superior to the inline model of the SDK. As luck would have it, I was able to get access
to Visual Studio.NET through my employer. So as a result, I moved forward with the VB.NET/VS.NET
version as my baseline framework. This decision would ultimately prove to be extremely important in
terms of community acceptance, as I’ll explain later.
Figure 1-2
3
An Inside Look at the Evolution of DotNetNuke
05_788163 ch01.qxp 6/13/06 6:13 PM Page 3