analysis/validation of a Word document file, comparison to older versions, pdf generation

Context: the actual website running in ASP with SQL SERVER database. authors submit documents to prepare publication.(Office Word format, max 500 pages.) the goal is to validate these documents and prepare publication. Project: PART 1: in input we have a simple doc file which can be zipped or not. if the file is zipped, it must be unzipped, tested if file is ok. the author that will submit the .DOC files will have to follow specific rules and .DOT templates files. so the first important operation to realize with the document is to validate with a .DOT file that will be on the server. if the model is respected, we continue, else we stop the process and put a flag with the detail of the problem. for this part, i imagine that some componants are existing and can be usefull. and i also know that it can be completly by dev code. so if i need to buy a small componant to make the project devlopment faster or much better, just tell me. but if you can dev all by your self its ok also. PART 2: documents submitted can have several versions. each time a new version is submitted (part1 is re-used), i want a repport to be created that will explain the differences between the new and the previous version of this [login to view URL] more time, some existging componants exists, especially for office documents comparison. as i told previously, if i can buy a componant to install on server, if its important to improve the speed of development or the quality . the repport will have to show the part of the document that have changed from the previous version (comparison of the blocs positions...) PART3 PDF generation, is not the hardest part i think. it will be a transformation of the doc file in PDF (still using the rules of the DOT file for templating, and insertion of 4 pages. ## 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). ## Platform actual server: server NT4 / Microsoft-IIS/4.0 i did not choose one solution, because i think there is always lots of different solution for one project like that. this project may be done in ASP, or C# or others techno like perl or else maybe, the team/ person that will be choosen will have to choose the more reliable technology/development language and the easyest of course... TECHNO / LANGUAGE so i think its better to use microsoft technologies on a microsoft server. its possible to install .NET framework on the actual server, but i dont know if it will make problem with old ASP website. we are thinking about change the server and migrate the full website. this way it could be possible to use .NET technologies ABOUT THE CODE code must be commented or documented, all used variables and comments must be in english.