This project is read-only.

Latest Release Notes for Auto-Input Protection (AIP)

Please read this document carefully before installing AIP.
Version: 2.0 Beta

Installation Instructions

The AIP installer will install the AIP library, ready-to-use, and the complete source code, which consists of a Visual Studio 2008 solution and projects, including all required content and code files.

To install Auto-Input Protection (AIP):
  1. Download the installer.
  2. Close all running instances of Visual Studio 2005 and 2008 on your computer.
  3. Run the installer.
    1. Important: The installer must run with administrative privileges. (Vista users see below for specific instructions).
  4. If the installer detects that you have Visual Studio 2005 Standard or 2008 Standard installed then it will offer to have the AIP web control installed in each so that it appears in the toolbox automatically. To have the installer add the AIP web control to the Visual Studio 2005 or 2008 toolbox, check the box next to each on the Control Registration step.
    1. Automated control registration does not work for Visual Studio Express Editions.
    2. Important: See Visual Studio 2005 Control Registration Issues below for information about a bug before installing AIP. (This issue does not seem to effect Visual Studio 2008.)
  5. If you've opted to have the installer add the AIP web control to a toolbox automatically, then the next wizard steps will ask you to enter the location of the Visual Studio custom controls folder, once for each version of Visual Studio.
    1. The default path (My Documents\Visual Studio YYYY\Controls) will be fine in most cases, unless you've configured Visual Studio to use a different folder.
    2. The path that is specified in the wizard is the root controls folder. Don't specify a folder for a custom tab because one will automatically be created by the installer: DaveSexton.Web.Controls.
    3. If the folder does not exist it will be created by the installer.
  6. Complete the wizard to begin installation.
    1. See Delayed Installation Warning below for information about a long delay that may occur during setup.
Note: Visual Studio (both 2005 and 2008) may briefly open and close during the installation, or uninstallation. This behavior is to be expected if you've used the control registration feature of the installer. After the temporary instances have closed, and the installer has completed, you may open another instance of Visual Studio for use. This behavior occurs as a result of the AIP Installer running the Tools.InstallCommunityControls command to install the AIP web controls into the Visual Studio toolbox.

Instructions for Vista Users
With UAC enabled, follow these steps to start the installation instead of double-clicking the installer file:
  1. Locate Start > All Programs > Accessories > Command Prompt
  2. Right-mouse click and select Run as administrator.
  3. Change the current directory to the location of the AIP Installer file. For example, enter the following: cd c:\users\dave\desktop
  4. Run the installer from the command prompt: msiexec /i name-of-installer.msi

Delayed Installation Warning

It is normal to experience a long delay during installation. The installer is merging AIP's documentation with Visual Studio's documentation, which can take quite a while. Please be patient.

The same goes for uninstallation.

See Integrated Help in Visual Studio below for more information.

Visual Studio 2005 Control Registration Issues

The installer provides the option to have the AIP web control added to your Visual Studio 2005 toolbox; however, there are some known issues with the Visual Studio command used by the AIP installer that may prevent the control from being installed. Regardless, the library itself will be installed on your system so you can manually include the controls in your toolbox if you want.

Problem 1
If you have installed Sql Server 2005 (any version including CTPs) after installing Visual Studio 2005 then you may have to perform some manual patching before using this installer, but only if you plan on having it install the AIP web control into Visual Studio 2005 for you.

Follow these instructions before running the AIP installer:

Failure to install Toolbox controls via ContentInstaller or Tools.InstallCommunityControls

Problem 2
If you still receive an error after making the appropriate registry changes and executing devenv /setup , or if you haven't installed Sql Server 2005 but you are getting an error anyway such as a Package Load Failure, then you may have to make a different registry modification.

You can try to delete invalid values under the following registry key and attempt the installation again:


Each value in the key above corresponds to a custom toolbox tab in Visual Studio. Visual Studio seems to require that the list only contain tabs that correspond to existing folders in the My Documents\Visual Studio 2005\Controls directory. Values that do not correspond to an existing folder must be removed.

More Information
The solutions above were discovered in the following thread and were tested on Windows Vista Business Edition for reliability, but please be aware that your own system configurations may affect whether these solutions are viable options for you:

Error Executing VSI File with Toolbox Controls

Auto-Input Protection Help

Preliminary documentation has been compiled for this release using DocProject and Sandcastle.

There are two different types of compiled help available, but both share the exact same content.

Standalone Compiled Help (.chm)

This is an optional download that is separate from the AIP installer. It is a compiled help file that can be opened on any Windows system by double-clicking it, with or without Visual Studio installed.

Integrated Help in Visual Studio

The installer will merge AIP help into Visual Studio 2005 and 2008 automatically.

To access AIP help while inside of Visual Studio you can open Document Explorer by pressing the F1 key and Auto-Input Protection will appear in the table of contents.
How to manually add the AIP help to Visual Studio
After installing AIP, if you don't see Auto-Input Protection in Document Explorer's table of contents, then try selecting (no filter). If it still doesn't appear then you have to merge AIP help yourself.

You may have to follow these instructions multiple times, once for each version of Visual Studio in which you'd like to have AIP help.
  1. Right-mouse click one of the following Help Collection Manager links and choose to open it in another browser window or tab.
    1. Visual Studio 2005 | Visual Studio 2005 Express Editions | Visual Studio 2008 and 2008 Express Editions
    2. Important: If nothing happens when you click a link, open Document Explorer or a new browser window yourself and then paste in the appropriate URI:
      1. ms-help://MS.VSCC.v80/dv_vscccommon/local/CollectionManager.htm for Visual Studio 2005 or
      2. ms-help://MS.VSExpressCC.v80/dv_vsexpcc/local/CollectionManagerExpress.htm for Visual Studio 2005 Express Editions or
      3. ms-help://MS.VSCC.v90/dv_vscccommon/local/CollectionManager.htm for Visual Studio 2008 and 2008 Express Editions.
    3. Make sure that you Allow Blocked Content in your browser since an ActiveX Control is required that your browser may deem unsafe. After allowing blocked content the page should function normally.
    4. If you get a Page cannot be displayed error after clicking one of the links above then you probably haven't installed the required version of Visual Studio.
  2. In the Help Collection Manager, locate Auto-Input Protection in the list of help collections and check it.
  3. Click the Update VSCC button to apply your changes.
  4. If a dialog appears read and follow its instructions carefully. You may have to restart Visual Studio for the changes to take effect.
  5. During the update the browser might not be responsive for a short period of time. Please be patient.
You should now see Auto-Input Protection in the table of contents in Document Explorer for each of the versions of Visual Studio to which it was added. If you do not, restarting the computer may help.

Source Code

Follow these steps to use the Visual Studio 2008 solution that is provided by the installer. (For Visual Studio 2005 users, skip these steps and see below.)
  1. Browse to the AIP installation folder in Windows Explorer (commonly, C:\Program Files\Dave Sexton\AIP).
  2. Copy the entire contents of the Source directory to another location; for instance, My Documents\Visual Studio 2008\Projects\DaveSexton.AutoInputProtection\.
  3. Double-click the DaveSexton.AutoInputProtection.sln file to open the solution in Visual Studio.
  4. If warned about missing source control information, click OK.
    1. When prompted, select Permanently remove source control association bindings.
  5. In Solution Explorer delete the file named, davesexton.pfx that appears in the Properties folder of the DaveSexton.AutoInputProtection project. The file does not exist.
  6. Open the Project Properties window for DaveSexton.AutoInputProtection by double-clicking the Properties folder in Solution Explorer or right-mouse click the project node and select Properties.
  7. Select the Signing tab.
  8. Select <New...> from the drop-down list to use your own signature.
    1. You may want to do the same for the DaveSexton.AutoInputProtection.Install.Actions project if you're planning to rebuild the installer.
  9. Save all of your changes and try to build the DaveSexton.AutoInputProtection project. There should be no errors, warnings or messages in the Error List.

How to open the solution in Visual Studio 2005

The solution and all of its projects were developed in Visual Studio 2008. To use them in Visual Studio 2005 you have to make some manual changes first.

Note: Do not open the solution in Visual Studio yet.
  1. Browse to the AIP installation folder in Windows Explorer (commonly, C:\Program Files\Dave Sexton\AIP).
  2. Copy the entire contents of the Source directory to another location; for instance, My Documents\Visual Studio 2005\Projects\DaveSexton.AutoInputProtection\.
  3. Open the DavesSexton.AutoInputProtection.sln file in notepad.
  4. Change the 10 in the first line to a 9.
  5. Change the VS2008 in the second line to VS2005.
  6. Save the changes and close notepad.
  7. Open the AIP Tests web application project (Testing\AIP\AIP Tests.csproj) in notepad.
  8. Locate <ProductVersion>9.0.21022</ProductVersion> in the first PropertyGroup and change it to <ProductVersion>8.0.50727</ProductVersion>.
  9. Locate the first ItemGroup and remove all Reference elements that have <RequiredTargetFramework>3.5</RequiredTargetFramework> as children.
  10. Locate <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\WebApplications\Microsoft.WebApplication.targets" /> near the bottom of the file and change the v9.0 to v8.0.
  11. Save the changes and close notepad.
  12. Go back to the installation folder and double-click the solution file to open it in Visual Studio 2005.
    1. Note: You may get warnings that there are unsupported project types. None of these projects are critical, however they may be required to build the installer or test the control. If the AIP Tests web application project is not loaded then install VS 2005 Service Pack 1 (SP1) and try again.
    2. Note: Do not attempt to build yet.
  13. When the solution opens, right-mouse click the DaveSexton.AutoInputProtection project in Solution Explorer and select Properties.
  14. Go to the Signing tab.
  15. Under Choose a strong name key file: select <New...>.
  16. Enter the name of a key file and press OK.
    1. You can uncheck Protect my key file with a password or create a password.
  17. Expand the DaveSexton.AutoInputProtection project node in Solution Explorer and then expand its Properties folder.
  18. Delete the davesexton.pfx file since it does not exist.
    1. Note: You can do the same for the DaveSexton.AutoInputProtection.Install.Actions project if you'd like to rebuild the installer.
  19. Go to the Build menu and select Build Solution.
  20. The build will fail and you will get errors since AIP was written in C# 3.0, not C# 2.0.
  21. Fix all of the errors and try building the solution again until it succeeds.
    1. Note: Since AIP targets the .NET Framework 2.0, the errors will most likely be syntactical, such as the use of object and collection initializers, extension methods, and shorthand property definitions, which are all not part of C# 2.0. For this reason there will most likely be a large number of errors that apply to only a few particular cases. Fixing one problem should fix many of the errors that are listed.

Last edited Apr 2, 2008 at 8:54 PM by davedev, version 2


No comments yet.