C#.net - document attachment to SQL server DB

We are building a web application in c#.net using Visual Studio 2010 and are using SQL server 2005 for the database. This task is to write some C#.net code for one of the functions of the application - the task is attaching pdf documents and tiff images as binary files to a SQL server table. The c#.net code required is to allow a user to "attach" document(s) to the web app: * the user will be "attaching" the document to a particular dollar amount inside a grid within an aspx page of the web app and each amount has a unique id * at the click of a button, the user navigates to a UNC (folder level) path for a file location (the path is obtained by concatenating several fields of an existing SQL server table - note that only the file path is kept in the existing SQL server 2005 table, with the document itself being stored in network storage) - a windows explorer type interface to select the file including navigation to the user's own drives (ie my documents, my computer etc) would be an advantage to your bid * the user then selects a file(s) which will mainly be a pdf document but might also be a word/excel file or a tiff image - all users have the end applications required to open all documents * while this task only requires single file upload, if you can write multiple file (ctrl-click or equiv) functionality that would be an advantage to your bid * the document itself (not just the file link) is COPIED from the UNC path/STORED as a varbinary(MAX) file in a table in the SQL 2005 DB - we are fully aware of the arguments for/against storing files inside SQL server, but it is reqd in this case and network storage is not an issue * upon selecting the file(s) from within the folder, the user is prompted to provide a mandatory reference number (<= 8 char alphanumeric) - the ref number is used as a hyperlink button to retrieve and view the document as required - the ref # is not required to be unique as it will be combined with other fields to create a primary key * delete/rename document functionality is required, whereby the SQL server binary document can be renamed or deleted by the user - the original file within the network would not be deleted and remain intact You will have extensive experience with C#.net, should have visual studio installed (at least express version) and be able to publish URLs of your progress to allow us to see your results. The end deliverable is the code itself. Existing SQL server existing table schema and sample data can be provided to assist with column names etc for your coding. Good English and best practice coding and commenting within C#.net required. Upon successful completion there may be further tasks to complete.