Need classic ASP app converted to .NET

We currently have an application that manages a vanpool service, which comprises of: *vans *passengers *payment module The system was built in classic ASP and because of limitations and bugs, we need it to be built in .NET. Our main requirments for this project are: *the application to be robust and airtight *no bugs *clean code *reliable support BACKGROUND *There are a number if vans that travel throughout towns, picking up and dropping off passengers at various worksites. *Passengers pay for the service by cash, check, or bank card via a merchant account. *Each van has a coordinator that manages the van. Some vans have more than one corrdinator (alternate-coordinator) *The vanpool service is managed by multiple administraors. Some of the administrators are van coordinators, passengers, and people who do not ride vans at all. *Therefore the roles defined in the system are: administrator, coordinator, passenger. *Every person has a profile, every van has a profile. *A van's monthly fee charged to the passenger varies for each van and is calculated by an administrator. The administrator enters this figure month by month for each van. In turn, the coordinator takes the figure and calculayes what each passenger needs to pay. The coordinator sends an email to all passengers each month and the passenger has the option of cash, check, or paying online. *When the passengerpays online, an email confirmation is sent and their records are updated automatically in the system. *Passengers can view all the historical data of their payments and they also have the ability to edit their profile. *Coordinators can see their own payment history as well as the payment history off the passengers belonging to their van. They can also view, add, and edit passengers for their van. They can also edit certain aspects of their van. *Administratos can see and edit everything described above and more. They can edit all aspects of the application. *Van Availability: when a coordinator notes a vacancy on their van, this automatically appears on the van availability grid that the public can view as a means of joining a van. There is also a waiting list form that the public can submit if there are no vacancies for a particular van of for a route that doesn't exist yet. REQUIRED FIXES/ADDITIONS *.NET application needs to integrate seamlessly with our merchant account. *Need to manage vans better: would like to keep track of all oil changes for each van. The coordinator or administrator can ass the dates for each oil change and the vendor that performed it. The system will keep track of all oil changes. *Would like to discuss the primary key for passengers in the current system. The email address is the primary key. However,people will leave the vanpool (status:disabled) then return at a later date to join a different van perhaps with a different email. Thus we have a duplicate entry for the same person but with a different email address, creating confusion in the system. *Another issue is sometimes the coordinator changes for a van. After a new person is designated the coordinator, it does not automatically update the coordinator field for passengers belonging to that van. When the new coordinator logs in, he cannot see the passenger profiles because it still shows the old coordinators name. *Autopay feature *Improved user interface, dashboard features *Condensed views, pop-up windows displaying more information. *At certain mileage intervals (every 15,000 miles) the van is required to do a maintenance check. Enclosed is a mockup form that a coordinator or asdministrator can submit to the application. The application needs to keep track of all maintenance entries for each van. *Currently, passengers belong to a van. Sometimes a van has to be switched out for various reasons (maintenance, wrecked, etc.). The current system will not allow us to switch out the van. We were thinking of having passengers and a van belong to a route instead, That way the van can be changed. We are open to suggestions on this issue. ENCLOSED ARE SCREENSHOTS OF THE APPLICATION WITH NOTATIONS OF WHAT IS NEEDED *We would like to see multiple examples (screenshots ok) of your work, related to this project. *Favorable ratings are required. *expert experience in .NET and msSQL. *We will have a QA person checking and auditing the application and checking the code and functionality while the project is ongoing. *We expect to be updated often as to the progress of the application. We require availability for questions, comments, or to just chat about the project. *If we make contact via email and do not recieve a reply within 2-3 days, we will have to terminate the agreement/project between parties. *We are open to suggestions for thhis application. *We would like to have a maintenance agreement after the project is completed. PLEASE DO NOT MAKE A BID OR SHOW INTEREST IN THIS PROJECT UNLESS YOU ARE COMMITTED TO DOING THE WORK IN THE AMOUNT OF TIME THAT YOU SPECIFY. ALSO, COMMUNICATION IS THE MOST IMPORTANT COMPONENT OF THIS AGREEMENT. Thank you for taking the time to read and review the specifications. We want to make a selection soon and proceed with the project. specs/screenshots - [login to view URL]