Develop a Custom Editor Extension for Visual Studio 2010

Create a custom Visual Studio 2010 Editor. It will be a "Single View" editor each editor will edit one "document". The editor is a simple file editor for editing SQL based files in a grid format. The editor itself is based on the code in the attached zip archive. Specifically, the attached zip archive is a testing harness for the editor itself. The final test I will be doing before payment is to start with a clean / fresh workstation with ONLY Visual Studio 2010 Professional SP-1 installed and then double click the install package. I should then be able to start Visual Studio and double click a [login to view URL] file and the custom editor allows me to fully edit the file as described above. ## Deliverables Task: Create a custom Visual Studio 2010 Editor. It will be a "Single View" editor each editor will edit one "document". In addition, the application design should follow MVC patterns for interaction. Generally, this article: <[login to view URL]> provides for a good background on the concepts, except the technology should be updated to Visual Studio 2010. This page: <[login to view URL]> contains the general process that should be followed now. Specifically, using MEF should be followed. In addition, the editor is already built with WPF and should remaing using WPF. I do NOT want someone to simply click the "Create new VS package template" and then update the template (Although this is okay as a starting point). The code should be VERY lean, reusable and all lines of code should be very relevant for this specific implementation. Final payments are specifically linked to code cleanliness, relevance and reusability. The editor is a simple file editor for editing SQL based files in a grid format. The grid allows the editing of the sample data defined in the SQL files and the logic for the editing (adding/saving) is already completed. This project is specifically about writing a wrapper for the functionality to allow the Custom Editor to run inside Visual Studio. There is a sample .sql file included in the root of the archive that can be used to verify if the system is working. The editor itself is based on the code in the attached zip archive. Specifically, the attached zip archive is a testing harness for the editor itself. In the archive provided, the entire [login to view URL] and FileListView projects should be removed when building the VS Custom Editor. Design Items: 1) The Custom Editor should open automatically within Visual Studio when a file in the solution that has the extension "*.[login to view URL]" is double clicked (or opened). 2) This action is simulated in the supplied testing harness in the [login to view URL] command. The existing Workspaces will be removed from the testing harness and the SqlMergeScriptViewModel should be the beginning of the Custom Editor. 3) Specifically, the Visual Studio "normal" editor commands should be wired up. This includes Opening and Saving the "*.[login to view URL]" files from a solution. If the project is in version control and the file is in version control, then editing the file through the custom editor should trigger a checkout of the file just like editing a C# file. 4) Additional editor commands like Select All, Copy, Paste, Cut, Redo and Undo should all behave as normal inside of the Custom Editor window. 5) The IsDirty indicator should work as expected in the title bar of the document. 6) Multiple documents should be allowed to be opened in the Visual Studio editor area just like editing multiple C# files at the same time. 7) The RDT (Running Document Table) should be updated accordingly as documents are opened or closed. 8) The Visual Studio solution view should allow showing a custom icon specifically for this file type. 9) Any unhandled exceptions should be logged to the Windows Event Viewer and the user notified with a popup. 10) An installation package project needs to be part of the delivery. The project needs to do everything necessary to allow a developer to "double click" the install package and register the custom editor in their Visual Studio 2010 environment. Specifically, the final test I will be doing before payment is to start with a clean / fresh workstation with ONLY Visual Studio 2010 Professional SP-1 installed and then double click the install package. I should then be able to start Visual Studio and double click a [login to view URL] file and the custom editor allows me to fully edit the file as described above. Project Notes: 1) The extension should be called "Vibrant SQL Data Manager" 2) The existing [login to view URL] project should be retained and should not need to change. 3) The existing [login to view URL] project should be retained and will be where the main code will live for the funcionality of the Custom Editor. 4) A new project called [login to view URL] should be added that contains the code needed to make this a Custom Editor. 5) The existing [login to view URL] project and FileListView projects can be removed in the Custom Editor implementation - they are just for this testing harness project. 6) The code needs to be in C#, .NET 4.0.