ASP.NET Communicating with a server/service

We are in need of working two-sided software code examples described below. We are only looking for a fast start-up based on the written example, the real development will be done by us internally. So we need code samples that will show us the route we will follow. We are not forcing for a specific way to achieve the goal. Coder can advise and use his technique. There will be a server, service or an .exe running on a computer. Let's say it an "engine". An ASP.NET page(later this can be another exe) will communicate with this engine, and request to store a record on MYSQL, or MS-SQL database, and will be wait for if the operation is successfull. ## Deliverables We need an "ENGINE" example and aspx example communicating with the engine. As an example, there will be a simple database table with few columns in MS-SQL. An aspx page will have some entries appropriate with the MS-SQL database. When a button is clicked user filled entries will be sent to "ENGINE"(we dont know how they will communicate, its your business). Engine will place the entries to the MS-SQL table and report the results back to aspx. aspx somehow should know if the record is stored in database or not. Our main goal to have a working example that an aspx page communicate with an engine. We later will put our functions to the engine. For example engine will allow only authorized access, or an aspx can send some commands and parameters, so that engine will execute. The communication structure should maintain an aspx page can communicate with the engine, also another exe can communicate with the engine. Our initial thought was these software can communicate over a database. But we dont know if there are easier or better way to do it. We will develop the applicationand at the final we will have an engine running on a server computer, and people-empployee can connect to this engine and view or edit or store records from web based software(aspx), from exe files on their computers, or from PDAs. We will put functions who can connect to engine who can edit, or store or delete a record. Engine will create reports etc...This will be a very customized ERP or MRP type company software as growing by time. We need to make the first start quickly by your working examples and they will be our sturcture. Main programming language should be C#(not VB) **Centeral Engine/Server:** It will be a centeral engine developed using web services. It will be host it on any web server. Its functinality will be written in web services with a SQL Server back end. We will be able to write as many functions as we want to extend its functionality. It will require user authentication to communicate with client applications. **Client Web Page:** An aspx page which we will be able to host any where on internet or intranet. It will have UI to connect and use centeral engine functionality. This web page will function as: - It will have an UI for user name and password for server side authentication - It will have a form to Add/Edit/Update/Delete data from server through centeral engine and a button to request server datetime information. **Client Exe:** We need also an exe which we will be able to install at Windows XP. It will also perform all of the functions of above described aspx page. With above solution we will be able to test the exact functionality which we are requiring. We will have an engine to work on server, we will have an aspx page which we will be able to host independently anywhere and an exe to install any PC. Aspx page and exe will communicate with our centeral engine to manipulate data on our server with user authentication and execute our functions. 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). ## Platform Windows XP, Internet Explorer