|
|
|
Verastream Host Integrator 6.6 and .NET 1.1 Applications
Technical Note 40037
Last Reviewed 11-Sep-2008
Applies To
Verastream Host Integrator version 6.6
Summary
Technical Note 40037
Last Reviewed 11-Sep-2008
Applies To
Verastream Host Integrator version 6.6
Summary
Client applications that use Microsoft .NET Framework version 1.1 will not run after upgrading the Verastream Host Integrator .NET Connector API to version 6.6. This technical note provides solutions for this issue.
Symptoms
When attempting to run a web application that uses .NET version 1.1, you may see a server error that includes the following:
System.NullReferenceException: Object reference not set to an instance of an object.In Web Builder, if you attempt to re-build an existing web application that uses .NET version 1.1, the build process may fail with an error similar to the following:
C:\Program Files\VHI\lib\dotnet\WRQ.Verastream.HostIntegrator.dll : error BC31011: Unable to load referenced library 'C:\Program Files\VHI\lib\dotnet\WRQ.Verastream.HostIntegrator.dll': Version 2.0 is not a compatible version.vbc : error BC30142: Unable to generate a reference to file 'C:\Program Files\VHI\lib\dotnet\WRQ.Verastream.HostIntegrator.dll' (use TLBIMP utility to reference COM DLLs): Version 2.0 is not a compatible version.C:\Inetpub\wwwroot\<project name>\AidKeyPalette.ascx.vb(2) : error BC30466: Namespace or type 'HostIntegrator' for the Imports 'WRQ.Verastream.HostIntegrator' cannot be found.Explanation
Earlier versions of Verastream Host Integrator (VHI) supported Microsoft .NET 1.1 Framework 1.1 (and Microsoft Visual Studio 2003) as follows:
- In VHI versions 5.5 and 6.0, Web Builder supported creating .NET 1.1 projects.
- In VHI version 6.5, Web Builder supported re-building existing .NET 1.1 projects (if, prior to upgrading to version 6.5, you created user-defined project types by copying the .NET 1.1 project types).
- In VHI versions 5.5 through 6.5, the .NET Connector API supported running .NET 1.1 applications.
In VHI version 6.6, however, the .NET Connector is designed for .NET 2.0 applications. This .NET Connector is a managed, pure .NET implementation (no longer dependent on the COM Connector). If you have an application still using .NET 1.1, it will not work with the version 6.6 .NET Connector provided in the VHI version 6.6 Development Kit or Windows Server Kit.
Solutions
If you have existing client applications using Microsoft .NET Framework 1.1, choose one of the following solutions when upgrading to VHI version 6.6.
Option A: Use .NET 2.0
Developers using .NET are strongly encouraged to create new client applications using .NET Framework version 2.0 (and Microsoft Visual Studio 2005) or higher. Web Builder version 6.6 supports generating .NET 2.0 applications.
Option B: Do Not Upgrade Client Systems
This option is suggested only if you are unable to update your existing .NET 1.1 applications. The earlier (pre-6.6) VHI .NET and COM connectors can successfully connect to and run with version 6.6 session servers. You can upgrade the VHI server to version 6.6, but leave the client with older connectors, .NET Framework version 1.1, and your existing client application code.
Option C: Replace 6.6 Connector with Older Version
This alternative is the least preferable. If you must upgrade your client platform to VHI version 6.6, and continue using .NET 1.1 applications, use the following steps to downgrade the connector. Note: Because the older .NET Connector uses the COM Connector, it must also be downgraded as described below.
- From an existing VHI version 5.5, 6.0, or 6.5 installation, backup the following files:
\Program Files\VHI\bin\appconncom.dll
\Program Files\VHI\lib\dotnet\*
\Program Files\VHI\lib\dotnet\*
- When installing VHI version 6.6, choose a Custom installation and clear the options for the “COM Connector (VB)” and “Microsoft .NET Connector” components. (For other upgrading details, see Technical Note 40031.)
Note: If the version 6.6 .NET and COM Connector files are already installed, they must be manually unregistered (regsvr32 /u appconncom.dll), deleted from the .NET Assembly Cache, and removed from the VHI bin folder before proceeding.
- Copy the pre-6.6 connector files (from step 1 above) into the appropriate original folders.
- At the Command Prompt, run the following command (to manually register the pre-6.6 COM Connector):
regsvr32 \Program Files\VHI\bin\appconcom.dll- Add the pre-6.6 files to the Windows assembly cache:
- In Control Panel, Open Administrative Tools.
- Open Microsoft .NET Framework (1.1 or 2.0) Configuration.
- In the left pane, click Assembly Cache (or click "Manage Assembly Cache" in the right pane).
- Before proceeding, view the list of assemblies in the Assembly Cache and verify these version 6.6 files are not listed:
AppConn.Interop
WRQ.Verastream.HostIntegrator
WRQ.Verastream.HostIntegrator
- In the right pane, click "Add an Assembly to the Assembly Cache" (or right-click Assembly Cache and click Add).
- In the "Add an Assembly" browse dialog, go to C:\Program Files\VHI\lib\dotnet and select all DLL files that are present. Tip: Use Ctrl+click or Shift+click to select multiple files at once.
AppConn.Interop.dll
WRQ.Verastream.HostIntegrator.dll
policy.5.5.WRQ.Verastream.HostIntegrator.dll (present with version 6.5 or 6.0)
policy.6.0.WRQ.Verastream.HostIntegrator.dll (present with version 6.5)
WRQ.Verastream.HostIntegrator.dll
policy.5.5.WRQ.Verastream.HostIntegrator.dll (present with version 6.5 or 6.0)
policy.6.0.WRQ.Verastream.HostIntegrator.dll (present with version 6.5)
Click Open.
- View the list of assemblies in the Assembly Cache and verify that the added files are present.
Note: If you have already been running an existing web application that calls the VHI connector, certain DLL files remain loaded by IIS and locked. To make changes, you may need to restart your system, or terminate the aspnet_wp.exe process in Windows Task Manager.
