Chris Pattinson

We’re going to run a contest during our Highlander field test. It should be fun and a good way to encourage the field testers to work closely with the development team. Call it an ‘Iron Chef - Coding’ event, if you will. And the ingredient to be served up is ….

The new ASP.NET Provider.

To enter, you’ll need to apply to the Highlander fieldtest.

Here are the general details:

ASP.NET Provider Application Contest

Task

The contest tasks you to build an application that demonstrates and exercises several of the new features under development in Highlander.

• Submitted application should have the following features as a minimum:
  • Application should exercise the ASP.NET provider
  • Application should compile
  • Application should be deployable
  • Application should have a project page with instructions to use/extend
    • This is an HTML page that will describe the project, how it can be used, and how it can be expanded.
  • Must be built using Highlander

Application should exercise (if applicable):

• Membership
• Roles
• Session state providers
• Profile - where you store information specific to a user (eg: shopping cart)

Example Solutions

• Template Library
  • File New | Blog
  • File New | E-Commerce
  • File New | Content Management System
  • Any sort of online database requiring user access, authorization, and authentication

Process

• Applicants must agree that all submissions become the property of CodeGear
• Bug reports via Quality Central
• Submissions via .binaries in single .zip to field test newsgroups
• The ASP.NET provider fieldtest newsgroup will be used for discussions and issues surrounding the project.
• Participants will have to sign NDA and participate in Field Test
• Submissions must be received by August 15th
  • Winners will be announced on 29 August
  • Top three may ship with product (Other options: CodeCentral)

Extra Points

"Extra Points" will be given for applications that:

• are Database Agnostic - multiple database usage (Interbase, MSSQL, Oracle, Sybase, DB2, Informix, MySQL)
• have a thorough project page
  • No need to be localized
• are skinnable or come with various themes
• are ready to be shipped in the product
• exercise the features thoroughly
• result in finding bugs in the Provider implementation
• demonstrate complex session state providers/roles/membership
• use of ATLAS components
• use the ECO provider

Judges

• Nick Hodges - Chairman, Mark Edington - R&D, Jim Tierney - R&D, Chris Pattinson - QA

Prizes

• TBD: T-Shirt for all participants that meet minimum criteria
• CDN article to recognize all participants who met minimum criteria
• Recognition in Shipped Product 
• Product Licenses

Share This | Email this page to a friend

This entry was posted on Tuesday, July 3rd, 2007 at 3:27 pm and is filed under RADStudio, Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.