A few bugfixes to an existing web application (guaranteed further work if job is well done)

I have an existing web application which is live with customers, many free and a couple paying. The system has a few bugs that I need fixed. If I am happy with the work done in fixing the bugs, I have a load of extra work to be done on this website, including changes to existing functionality, new features, a massive design overhaul, etc. The website is <[login to view URL]> To be qualified for this job: * You must be VERY experienced with JavaScript and CSS. These are used heavily by the site. * You must have excellent skills with ASP.Net, C# and SQL Server * You must have a rating of at least 8.0 OR no rating at all. If you have no rating, I'll need to see examples of your work. People with ratings lower than 8.0 will not be considered. Generic copy/paste applications for this job WILL BE IGNORED. If you want this job, please type a personal response. The bug fixes to be completed are: * Popup dialog boxes aren't always closing correctly. Sometimes they show a second time and sometimes they won't close at all. * In the customer chat window, received messages are often outputted to the window multiple times in a row. * The existing system calculates elapsed time periods erroneously by way of the fact that it assumes that the web server time and the database server time are the same. Seeing as synchronising the server times is not feasible, the code needs to be altered so that all time calculations are based on the current time retrieved from the database rather than the current time on the web server. * Whenever an HttpApplication instance initialises, it runs a database setup script. This needs to be bypassed as it should only be run when required. This could be as simple as commenting out a bit of code. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Monday Jul 9, 2007 9:29:17 AM: Just a quick update. 1. For all of those asking for the URL and/or a list bugs, umm... read the project description? Applying for *any* project and then asking questions that were answered clearly in the project description is never going to endear you to the person who posted the project. They will be thinking "If they can't even read the project description, what sort of attention to detail will they apply to their work?" 2. I am looking for a longer term relationship here with the right person. Guys, there are 4 (FOUR) bug fixes here. One person has posted a $1000 bid! I don't have a lot of money right now, as this is a private venture funded out of my weekly pay packet. If your bid was based on what you thought I could afford, rather than what you actually should charge for the project, feel free to update your bid. There have been a couple of candidates who seem pretty good, but the price range was way too high. So if you want to revise your bid with that in mind, feel free. Remember that more work is to follow. 3. For those who were curious where to find the bugs, you need to sign up. Make a free account and have a click around. Clarification on bugs is as follows: (a) The dialog bug is easy to reproduce, try editing your account settings, also if you set up a website to include the Prospector script and then watch the traffic monitor while testing, you can click on any visitor you see and you'll notice that about 90% of the time, the popup informational dialog box returns a second time after you close it. (b) To see the chat window bug, you'll have to set up your website to interact with Prospector. Don't worry, you'll automatically receive full instructions in your signup confirmation email. Once you've done that, place a chat button on your website and use it to request a chat. Inside Prospector, you'll see a chat request pop up. Respond to the request and type a few messages which you'll see displayed in the client chat window. Respond to the messages (i.e. have a short conversation with yourself) and you'll see the message-repeating bug occur in the client chat window. The chat window inside Prospector seems to work fine at this stage. (c) The time synchronisation bug is related to the traffic monitor. When someone comes to your website, Prospector will spend over sixty seconds in a state believing that you only just arrived at that site. ## Platform The site runs on ASP.Net 2.0 on Windows Server 2003. It's written in C# and uses a SQL Server 2005 database.