Migrate Configurations From VC7 to VC6

Edited: Increased Min Bid I have a VC7 solution that I just went through and did a major clean up on it's configurations. It consists of 6 projects with 18 solution configurations. I also have a VC6 workspace, that has not yet been cleaned up. I need someone to look at the VC7 configurations and set up the VC6 configurations to match. There isn't really that much to do, but it's a lot of manual changes. There are some minor differences between the two solutions, such as output paths, and input libraries. We will provide you with a Remote Desktop Address to our environment which has VC7 and VC6 and a list of rules/differences. From there you'll need to log in, and get the VC6 solution to match and compile. We will be available on IM and shadowing on Remote Desktop so that we can help with any problems or answer any questions. ## 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 win2k +