Users upload contents of cd and/or dvd drive to my ftp server.

I would like users to download my windows7/vista vb.net or c# .net application that they install. It would make a disc image of what is in their cd/dvd drive Audio CDs are special because normally you would use a utility to make a .bin file of this Data CDs and DVDs can be used to create a .iso image file. Once the .bin (or audio cd image) and .iso (data cd or dvd image) is created on the hard drive, the software will upload to my ftp server. I've heard of DirectShow from microsoft [login to view URL] and the newer Media foundation [login to view URL] but I do not know if they are useful or not. We could use a good sdk (even if i have to purchase it). I would purchase it if you've had experience with it before. **Look at the deliverable section for more details!** The user will pick graphics either from a set of graphics we include, or use their own graphics. These also will be uploaded to the ftp server upon completion. This project is very similar to what [login to view URL] does.? ? While my program will be nicer looking, and not include all the details this kunaki program has, it would be a good idea to look it over before accepting the project. [login to view URL] ## Deliverables You should have experience with projects reading/writing from cd/dvd players.? It's important we use a good component to make an exact copy of the audio cd, data cd, or dvd.? I want data cds and dvds to make a .iso image file.? I want audio cds to make some kind of file (i'm not sure but I think .bin is fairly common).? ? The ftp upload process needs to be fast and robust.? If the client loses their connection, and/or reboots windows, or it hangs, it must be able to resume.? Some of these files will be up t 4.7GB and take as much as 20 hours to upload so the ability to resume is very important.? You must have some experience with uploading via ftp etc.? My server will support resume or whatever is standard in these situations. This client app mainly does the image creation for data cd, audio cd, and dvd. Then it uploads to my ftp server which in turn updates a website project that exists on my website. There is a web site component in all of this: The client app will ask (in a form) for the customers email and password. The client app will send this info (i'm assuming via http) to my web server (some page on my site like [login to view URL] at yyy.com&password=xxxyyy page). My web server will respond via http response (html) with some kind of whether the customer has an account or not and will include their account# such as 55010. Perhaps, if the customer does not have an account, we will direct them to my website to create one. Now that we know they have an account, we can look at the cd/dvd drives and auto detect what they have and help them choose whether it's a audio cd, data cd, or dvd. We ask the user to title the project. We ask the user if they want to package their project in a clear sleeve, cd case, or dvd case Based on that, We ask the user to choose a .jpg image files for the packaging. We ask the user to choose a .jpg file that will be printed on the disc surface. If they don't have these files, it's ok because the project that gets created will use default generic files, and the user can change them later on the website (outside of this process). the client application makes the project .iso or whatever image file we use for audio cds (.bin?). When all is done and ready, the client application prompts the user to continue At this point, the client application calls the website again (probably via http to a page like [login to view URL] at yyy.com&password=xxxyyy ). The server will respond with a unique account# such as 65010. This account # and company# are going to be used to create the directory structure on the ftp server. For example, the files would be uploaded to something like /uploads/Company55010/Project65010/Disc1/[login to view URL] (also, the .jpg images will go here too) The client application asks the server for the current ftp username/password (perhaps we can work a way to hide this -- i'm open to suggestions) i.e. http to a page like [login to view URL] at yyy.com&password=xxxyyy ). The server will respond with something like 'user: xxxyyy password: aaabbb I realize this is a mess because anyone with an account on our system could query this page. What can we do here? At this point, the client application will start the upload process, giving the user good feedback (time left, progress bar). The ftp process must be able to handle resume so if the user turns off the computer or reboots or loses internet connection, it can start again where it left off. The client application must be able to save the data at each step so they can easily go to any step (bread crumbs) and edit/change information. This way, users can modify the files if they need to make changes and upload them again. When finished, the client application will communicate to the web site somehow to indicate success or failure e.g. /[login to view URL] at yyy.com&password=xxxyyy&projectID=555010&result=success ). This will tell the website the project was uploaded and it will then adjust the online project so it can download or move those uploaded files. The client application will SAVE all this session data to a file so they can open the file again if they want to make changes to anything or upload it again. This data should be saved at every step in case they quit or turn off the computer. Therefore, the client application should have ability to create NEW file. There should be a way to list the files they've created so they can easily select them. ## Platform windows 7,vista,xp