Asp.net Application for Add Merge Validate Post Phase III Anaysis and Design Discussion and Code - Add New Vendor

Design and Analysis discussion and Code on Web Application for Vendor Add, Change, Merge, and Validate as illustrated in the Attached files. Each Use Case will be posted as a separate request. This request is only for the Add New Vendor function. Subsequest requests will be made for Change Vendor, Merge Vendor, Validate, and Post, Admin Functions. For comments on analysis and design enter your discussion in this document using Word track changes with any code, illustrations, diagrams or other material that you would like to use to discuss or illustrate the points. And attaché it to the RAC message for documentation of the project. There are many code solutionst that have been developed and included in the attached files. You can refer to the code or use it or write your own as long as your solution meets the requiremetns. The folders are referred to in the attached Word file "Vendor Master List Analysis Design Code" by showing an image of the solution and the folder that it is in. Unable to upload files, link is on [login to view URL] ## 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). Confidentiality. 1 No Use. Recipient agrees not to use the Confidential Information in any way, or to manufacture or test any product embodying Confidential Information, except for the purpose set forth above. 2 No Disclosure. Recipient agrees to use its best efforts to prevent and protect the Confidential Information, or any part thereof, from disclosure to any person other than Recipient's employees having a need for disclosure in connection with Recipient's authorized use of the Confidential Information. 3 Protection of Secrecy. Recipient agrees to take all steps reasonably necessary to protect the secrecy of the Confidential Information, and to prevent the Confidential Information from falling into the public domain or into the possession of unauthorized persons. 4 Scope. The scope of Confdentiality is deemed to be in all contracts present past and future with the Parties to this request. ## Platform Visual Studio 2005 SQL Server 2005 Ironspeed 5.2.21 ASP.net, C#, VB