Upgrade to WIRE ver. 4

Upgrade Prerequisites

1. Ensure that you have a backup of your existing VS.NET project.  You may need to reference existing configuration files during the upgrade process, so make sure you have a copy of the original state of your project to work with.
2. Upgrade your WIRE Project in VS.NET to .NET Framework 3.5
3. Ensure that WIRE Application still works as expected after upgrade.

Upgrade Process

This upgrade assumes that you are upgrading a project with the same structure as our starter project WIRE_GUI.

Extract Upgrade Zip File

1. Move all config files to root project directory
   
   • Copy all config files that are in the "bin" folder to the root of the WIRE_GUI directory.
2. Extract the WIRE_ver4.0.zip archive into the root WIRE_GUI directory of your existing project. (This will overwrite your WIRE.dll.config and WIRE_GUI.dll.config files, so make sure you have a backup!)
3. Delete the PrintPage.ascx file from the rood WIRE_GUI directory of your existing project.

Update Visual Studio Project

1. Open the project in Visual Studio
2. If you have references to to assemblies in the "bin" folder
   • Remove all references to assemblies in the "bin" folder
   • Move any dependent assemblies to the "lib" folder (make sure assemblies are removed from "bin")
3. Reference the following assemblies in the "lib" folder
   • AjaxPro.2.dll
   • AssemblySettings.dll
   • BAMacros.dll
   • BrandonCollections.dll
   • DataDictionary.dll
   • Ionic.Zip.dll
   • RequestReduce.dll
   • WIRE.dll
   • Wire.XmlProfilePersister.dll
   • WireControls.dll
   • WireLicense.dll
   • Wire.Common.dll
4. Delete all dlls from bin folder
5. Include config files in project
   • Include the WIRE.dll.config, WIRE_GUI.dll.config, DataDictionary.dll.config and Wire.XMLProfilePersister.dll.config files into the VS.NET project (right-click on files in VS.NET and choose "Include In Project").
   • Select all four configuration files in VS.NET and edit the Properties for these files (press F4) to match the following:
     
6. Include the following files/folders on the VS.NET project (right-click on file in VS.NET and choose "Include in Project")
   
   • Download.aspx
   • UserControls directory
   • Styles directory
     • jquery-ui.css
     • wire.css
   • Javascript directory
     • clientMenuScript.js
     • ClientScripts.js
     • CloseSideWindow.js
     • jquery-ui.min.js
     • jquery.js
     • jquery.plugins.js
     • jquery.popupwindow.js
     • lookupBtn.js
     • Stylesheets.js
     • vv_search.js
     • Wire.js
   • Images directory
     • AutoZoomOff_disabled.gif
     • AutoZoomOn_disabled.gif
     • Classic.gif
     • ClassicMode.png
     • Enhanced.gif
     • EnhancedMode.png
     • loading-animated-dots.gif
     • menu_over.png
     • Standard.gif
     • StandardMode.png
     • vv-close-button.png
   • Images/Button
     • navbutton.gif
     • navbutton2.gif
   • Images/Tabs directory
     • Rename.png
   • Images/Toolbar directory
     • refresh.gif
     • refresh_disabled.gif
     • toolbarbg.gif
     • toolbarbtn_separator.png

Configure WIRE

1. Update WIRE configuration files
   
   • Copy connections section from your original WIRE_GUI.dll.config file into the updated WIRE_GUI.dll.config file in the root of the WIRE_GUI directory
   • Check both WIRE_GUI.dll.config and WIRE.dll.config files to ensure no existing configurations changed.
   • Setup new path for User Profiles
     
     • Ensure that Wire.XMLProfilePersister.dll.config has correct path to Profile directory on web server.
     • Ensure that the user that the application pool runs under has the appropriate rights to write to the configured Profile directory 

2. In the web.config file, find any references to the AjaxPro.AjaxHandlerFactory type, and change to the AjaxPro.2 version as seen below...
   
   from: type="AjaxPro.AjaxHandlerFactory, AjaxPro" 

   to: type="AjaxPro.AjaxHandlerFactory, AjaxPro.2"

Test You WIRE Application

Build WIRE Application and run.  If compile errors are encountered, see "Troubleshooting Upgrade" below...

Troubleshooting Upgrade

"Type ??? is not defined" or "??? is not declared"

If the Type that is not defined is Callback, DisplayModes, EventType, HostTypes or ScreenFilter then Add the following Import to the top of the file reporting the exception

Imports WIRE.Common

Property 'DisplayMode' is 'ReadOnly'

This usually is caused by referencing the DisplayMode property on the HostSession object.  This is a breaking change in between WIRE 3 and 4, and should be changed to "HostSession.DisplayModeMax".