NET Pet Shop - MSDN - Microsoft

.NET Pet Shop 4 - Coding Horror
Photo provided by Flickr
“The .NET Pet Shop application is designed to show the best practices for building enterprise, n-tier .NET 2.0 applications that may need to support a variety of database platforms and deployment scenarios.
... design competetive and comparable to the Microsoft .Net Pet Shop, but without its shortcomings. The ben...
Photo provided by Flickr
In an effort to get some perspective on the controversy, I decided to go straight to the source. I tracked down Scott Stanfield, founder and CEO of , the development house Microsoft asked to build the .NET Pet Shop, and asked him some questions about his experiences developing the project. 基于.NET Framework 3.5下的PetShop。
Photo provided by FlickrNET Pet Shop 2 NET Pe - Scott Hanselman
Photo provided by Flickr.NET Pet Shop 4 – Dan Sellers's WebLog - MSDN Blogs - Microsoft
Photo provided by Flickr
When Java developers need a blueprint for the "best" way to design and build a J2EE application, they turn to Sun's demo application. Pet Store serves as a reference model showing the best practices for architecting and building the ultimate J2EE application. In November of 2001, Microsoft decided to open its own pet shop, only this time in C# and .NET. After benchmarking the .NET Pet Shop against for its own J2EE Pet Store implementation, Microsoft in terms of performance, implementation costs, and developer efficiency. In doing so, quite predictably, Microsoft has created a firestorm of controversy.Since the initial announcement, Oracle and Microsoft have both issued rebuttals. Even IBM has weighed in with comments on its WebSphere application server, which was mentioned in the .NET Pet Shop white paper. Most of the contention seems to revolve around these key issues: