Wiley Professional DotNetNuke ASP.NET Portals 978-0-7645-9563-9 ユーザーズマニュアル
製品コード
978-0-7645-9563-9
An Inside Look at the
Evolution of DotNetNuke
As much as I would like people to believe that DotNetNuke was intentionally created as a premier
open source project for the Microsoft platform, it is unfortunately not the case. As is true with
many open source projects, the software was created with commercial intentions in mind, and
only when it was discovered that its true purpose would not be realized was it reconsidered as an
open source project.
open source project for the Microsoft platform, it is unfortunately not the case. As is true with
many open source projects, the software was created with commercial intentions in mind, and
only when it was discovered that its true purpose would not be realized was it reconsidered as an
open source project.
In 2001–2002 I was working for a medium-sized software consulting company that was providing
outsourced software development services to a variety of large U.S. clients specializing primarily in
e-Learning initiatives. The internal push was to achieve CMM 3.0 on a fairly aggressive schedule
so that we could compete with the emerging outsourcing powerhouses from India and China. As a
result there was an incredible amount of focus on process and procedure and somewhat less focus
on the technical aspects of software engineering. Because the majority of the client base was inter-
ested in the J2EE platform, the company had primarily hired resources with Java skills — leaving
myself with my legacy Microsoft background to assume more of an internal development and pro-
ject management role. The process improvement exercise consumed a lot of time and energy for the
company; attempting to better define roles and responsibilities and ensuring proper documentation
throughout the project life cycle. Delving into CMM and the PMBOK were great educational bene-
fits for me — skills that would prove to be invaluable in future endeavors. Ultimately the large
U.S. clients decided to test the overseas outsourcing options anyway, which resulted in severe
downsizing for the company. It was during these tumultuous times that I recognized the potential
of the newly released .NET Framework (beta) and decided that I would need to take my own ini-
tiative to learn this exciting new platform in order to preserve my long-term employment outlook.
outsourced software development services to a variety of large U.S. clients specializing primarily in
e-Learning initiatives. The internal push was to achieve CMM 3.0 on a fairly aggressive schedule
so that we could compete with the emerging outsourcing powerhouses from India and China. As a
result there was an incredible amount of focus on process and procedure and somewhat less focus
on the technical aspects of software engineering. Because the majority of the client base was inter-
ested in the J2EE platform, the company had primarily hired resources with Java skills — leaving
myself with my legacy Microsoft background to assume more of an internal development and pro-
ject management role. The process improvement exercise consumed a lot of time and energy for the
company; attempting to better define roles and responsibilities and ensuring proper documentation
throughout the project life cycle. Delving into CMM and the PMBOK were great educational bene-
fits for me — skills that would prove to be invaluable in future endeavors. Ultimately the large
U.S. clients decided to test the overseas outsourcing options anyway, which resulted in severe
downsizing for the company. It was during these tumultuous times that I recognized the potential
of the newly released .NET Framework (beta) and decided that I would need to take my own ini-
tiative to learn this exciting new platform in order to preserve my long-term employment outlook.
For a number of years I had been maintaining an amateur hockey statistics application as a side-
line hobby business. The client application was written in Visual Basic 6.0 with a Microsoft Access
backend, and I had augmented it with a simplistic web publishing service using Active Server
Pages 3.0 and SQL Server 7.0. However, better integration with the World Wide Web was quickly
becoming the most highly requested enhancement and I concluded that an exploration into
line hobby business. The client application was written in Visual Basic 6.0 with a Microsoft Access
backend, and I had augmented it with a simplistic web publishing service using Active Server
Pages 3.0 and SQL Server 7.0. However, better integration with the World Wide Web was quickly
becoming the most highly requested enhancement and I concluded that an exploration into
05_595636 ch01.qxd 5/10/05 10:06 PM Page 1
COPYRIGHTED MATERIAL