Microsoft Primary Interoperability Assemblies 2005 8.0 Download
In most cases, you should add references to the PIAs that are installed by Visual Studio under the %ProgramFiles(x86)%\Microsoft Visual Studio\Shared\Visual Studio Tools for Office\PIA\ directory. These versions of the assemblies appear on the Framework tab of the Reference Manager dialog box. For more information, see How to: Target Office applications through primary interop assemblies.
microsoft primary interoperability assemblies 2005 8.0 download
When you install and register the Office PIAs in the global assembly cache (either with Office or by installing the redistributable package for the PIAs), the binding redirect assemblies are also installed only in the global assembly cache. These assemblies ensure that the correct version of the primary interop assemblies is loaded at run time.
Before following the steps Pranav suggested, please use Cl.exe command line to compile the Office component checker sample for the primary interop assemblies redistributable packages. For this office component checker sample (ComponentCheck.cpp), you could download a sample at the start of the MSDN page: -us/library/bb332051(office.12).aspx. Please see the topic with "Preparing the Office Component Check", and it introduce the steps to compile component checker. I post these steps as below.
Your microsoft.visualstudio.shell.interop.8.0.dll file could be missing due to accidental deletion, uninstalled as a shared file of another program (shared with Microsoft Visual Studio 2010 Ultimate), or deleted by a malware infection. Furthermore, microsoft.visualstudio.shell.interop.8.0.dll file corruption could be caused from a power outage when loading Microsoft Visual Studio 2010 Ultimate, system crash while loading microsoft.visualstudio.shell.interop.8.0.dll, bad sectors on your storage media (usually your primary hard drive), or quite commonly, a malware infection. Thus, it's critical to make sure your anti-virus is kept up-to-date and scanning regularly.
If none of the previous three troubleshooting steps have resolved your issue, you can try a more aggressive approach (Note: Not recommended for amateur PC users) by downloading and replacing your appropriate microsoft.visualstudio.shell.interop.8.0.dll file version. We maintain a comprehensive database of 100% malware-free microsoft.visualstudio.shell.interop.8.0.dll files for every applicable version of Microsoft Visual Studio 2010 Ultimate. Please follow the steps below to download and properly replace you file:
CAUTION : We strongly advise against downloading and copying microsoft.visualstudio.shell.interop.8.0.dll to your appropriate Windows system directory. Microsoft typically does not release Microsoft Visual Studio 2010 Ultimate DLL files for download because they are bundled together inside of a software installer. The installer's task is to ensure that all correct verifications have been made before installing and placing microsoft.visualstudio.shell.interop.8.0.dll and all other DLL files for Microsoft Visual Studio 2010 Ultimate. An incorrectly installed DLL file may create system instability and could cause your program or operating system to stop functioning altogether. Proceed with caution.
*************************** Read Me First ***************************Version 188.8.131.52April 29, 2006Introducing the Agilent IVI-COM Driver for the 34405A Digital Multimeters-----------------------------------------------------------------------The instrument driver provides access to the functionality of theAgilent 34405A DMM through a COM server which also complieswith the IVI specifications. This driver works in any development environment whichsupports COM programming including Microsoft Visual Basic, MicrosoftVisual C++, Microsoft .NET, Agilent VEE Pro, National Instruments LabView,National Instruments LabWindows, and others.Supported Instruments---------------------34405AInstallation-------------System Requirements: The driver installation will check for thefollowing requirements. If not found, the installer will eitherabort, warn, or install the required component as appropriate.Supported Operating Systems:Windows NT 4.0 (SP6 or later)Windows 2000Windows XPShared ComponentsBefore this driver can be installed, your computer must alreadyhave several components already installed. The easiest way toto install these other components is by running the Ivi SharedComponents installation package available from the IVI Foundationas noted below. It installs all the items mentioned below.IVI Shared Components version 184.108.40.206 or later.The driver installer requires these components. They must beinstalled before the driver installer can install the driver.The IVI Shared Components installer is available from: To install, open or run the file: IviSharedComponents.msiIf the driver installer exhibits problems with installing the IVIShared Components, find the program IviSharedComponents.msi andRun the program. It is able to install many of the required systemcomponents, including Windows Installer 2.0.Windows InstallerVersion 2.0 or later. The IVISharedComponents.exe program willinstall version 2.0 of the Windows installer.It is also available from:For Win98/Me: =32831For WinNt4/2000/XP: =32832Microsoft XML 4.0The Configuration Server, an IVI Shared Component, uses Microsoft'sXML 4.0 parser. The IVI Shared Components will install the XML 4.0parser. You can download the parser and its associated SDK from: Enter "xml 4.0" as keywords.Microsoft HTML Help Viewer (Win98, WinNT) Version 1.32 or laterThe driver will install without the help viewer, but you will notbe able to use the help file for the driver. You can download thehelp viewer from: Enter "html help workshop" as keywordsMS Windows ScriptTypically, wscript.exe is installed as part of the operating systemor with Internet Explorer. If you see an error about wscript.exe,you need to install the Windows Script.Download from: Enter "windows script" as keywords. Use the one appropriate foryour Operating System.VISA-COMAny compliant implementation is acceptable. Typically, VISA-COM isinstalled with VISA and other I/O library modules.If you are using Agilent Technologies' VISA-COM, useversion 220.127.116.11 or later. The latest version of Agilent's IOLibraries includes the required version of VISA-COM.!!!IMPORTANT!!!!If you are using NI VISA version 3.3 or earlier, you may need to manually register the Basic Formatted I/Ocomponent. This file is called BasFrmIO.dll and is located in C:\VXIPnP\VisaCom directory. If you installedVISA to an alternate location, then the component will be located in the VisaCom subdirectory of that directory.I/OIf you are using Agilent Technologies' IO Libraries, use versionM.01.01.04 or later. You can download the latest version from: If you are using National Instruments I/O libraries, use NI-VISAversion 3.0.1 or later and NI-488.2 version 2.2 or later.Sending commands directly to the instrument (bypassing the driver)via Direct IO using the System.IO interface will not work with AgilentIO Libraries prior to Agilent IO Libraries Suite 14.0.Additional Setup----------------.NET FrameworkThe .NET Framework itself is not required by this driver. If youplan to use the driver with .NET, Service Pack 2 is required.Download from: The .NET Framework requires an interop assembly for a COMserver. A Primary Interop Assembly, along with an XML file forIntelliSense is installed with the driver. The driver's PIA, alongwith IVI PIAs are installed, by default, in::\Program Files\IVI\Bin\Primary Interop AssembliesThe PIA is also installed into the Global Assembly Cache (GAC) ifyou have the .NET framework installed.If you install the .NET framework later, you can use the file::\Program Files\IVI\Drivers\Agilent34410\DotNet.batto put the driver's PIA into the GAC and properly register it.Start Menu Shortcuts--------------------A shortcut to the driver help file is added to the Start Menu,Programs, IVI, Agilent34405 group. It contains "GettingStarted" information on using the driver in a variety of programmingenvironments as well as documentation on IVI and instrument specificmethods and properties.You will also see shortcuts to the Readme file and any programmingexamples for this driver.Help Files------------The help file (Agilent34405.chm) is located in the directory::\Program Files\IVI\Drivers\Agilent34405MSI Installer-------------The installation package for the driver is distributed as an MSI 2.0file. You can install the driver by double-clicking on the file.This operation actually runs:msiexec /i Agilent34405.msiYou can run msiexec from a command prompt and utilize its manycommand line options. There are no public properties which can beset from the command line.Uninstall---------This driver can be uninstalled like any other software from theControl Panel using "Add or Remove Programs".To uninstall the IVI Shared Components you must use the IVI CleanupUtility available from the IVI Foundation at: Note: All IVI-COM drivers require the IVI Shared Components tofunction. To completely remove IVI components from your computer,uninstall all drivers then run the IVI Cleanup Utility. This utilitydoes not remove any IVI drivers.Using a New Version of the Driver---------------------------------New versions of this Agilent IVI-COM driver may have a newProgId.If you use the version dependent ProgId in CoCreateInstance,you will need to modify and recompile your code to use thenew ProgID once you upgrade to the next version of the driver.Doing a side-by-side installation of the driver to use multipleversions of the driver is not supported. If you need to go backto an older version of the driver, you need to uninstall the laterversion and install the older version.If you use the version independent ProgId in CoCreateInstance,you will not need to modify and recompile your code. The newversion of the driver has been tested to be backwards compatiblewith previous versions.To access the new functionality in a new version of the driveryou will need to use the latest numbered IAgilent[n]interface rather than the IAgilent interface. TheIAgilent[n]. property will return a pointerto the new IAgilent[n] interface. TheIAgilentN490x[n] interface contains the methods andproperties for the new functionality. The new interfaces wereintroduced rather than modifying the existing interfaces forbackwards compatibility. The interfaces that were previouslyshipped have not been changed.Known Issues------------!!!IMPORTANT!!!!If you are using NI VISA version 3.3 or earlier, you may need to manually register the Basic Formatted I/Ocomponent. This file is called BasFrmIO.dll and is located in C:\VXIPnP\VisaCom directory. If you installedVISA to an alternate location, then the component will be located in the VisaCom subdirectory of that directory.NOTE: For VEE revisions VEE 7.51 or earlier, the IVI-COM driver button under theIO -> Instrument Manager does not automatically work with this driver. Youmust manually select this driver by doing the following steps:1. Launch Vee 7.512. Open Instrument Manager.3. Click Find Instrument under the Auto Discovery tab.4. Select the 34405 in the list that comes up.5. The IVI-COM driver button is greyed out.6. Click on Properties(Under Instruments tab)-->Click on Advanced button in thewindow that comes up.7. Select the last tab on the window that comes up (IVI-COM Driver).8. Select the Agilent34405 driver from the drop down list.9. Click on OK & Come to the main window . The IVI-COM driver button should nowbe active.Revision History----------------Version Date Notes------- ------------ -----1.0.8.00 Mar 03, 2006 Added .NET policy file1.0.7.00 Dec 01, 2005 Miscellaneous bug fixes1.0.6.00 Nov 03, 2005 Miscellaneous bug fixes1.0.4.00 Oct 18, 2005 Updated simulation data file1.0.3.00 Oct 13, 2005 Miscellaneous bug fixes1.0.2.00 Oct 5, 2005 Miscellaneous bug fixes1.0.1.00 Sep 16, 2005 Lots of added functionality1.0.0.00 May 27, 2005 Initial releaseIVI Shared Component Revisions------------------------------18.104.22.168 IviConfigServer.dll22.214.171.124 IviConfigServerCAPI.dll126.96.36.199 IviCShared.dll188.8.131.52 IviCSharedSupport.dll184.108.40.206 IviDCPwrTypeLib.dll220.127.116.11 IviDmmTypeLib.dll18.104.22.168 IviDriverTypeLib.dll22.214.171.124 IviEventServer.exe126.96.36.199 IviEventServerDLL.dll188.8.131.52 IviEventServerDLLps.dll184.108.40.206 IviEventServerps.dll220.127.116.11 IviFgenTypeLib.dll18.104.22.168 IviFloat.dll22.214.171.124 IviPwrMeterTypeLib.dll126.96.36.199 IviRfSigGenTypeLib.dll188.8.131.52 IviScopeTypeLib.dll184.108.40.206 IviSessionFactory.dll220.127.116.11 IviSharedComponentVersion.dll18.104.22.168 IviSpecAnTypeLib.dll22.214.171.124 IviSwtchTypeLib.dllIVI Compliance--------------(The following information is required by IVI 3.1 section 5.21.)IVI-COM Ivi Dmm Instrument DriverIVI Instrument Class: IVI-4.2_DMM_v3.0Group Capabilities:Supported: UnsupportedIviDmmBase IviDmmACMeasurementIviDmmFrequencyMeasurementIviDmmTemperatureMeasurementIviDmmThermocouple IviDmmResistanceTemperatureDeviceIviDmmThermistorIviDmmMultiPointIviDmmTriggerSlopeIviDmmSoftwareTriggerIviDmmDeviceInfoIviDmmAutoRangeValueIviDmmAutoZeroIviDmmPowerLineFrequencyOptional Features: This driver does not support InterchangeabilityChecking, State Caching, or Coercion Recording.Driver Identification:(These three strings are values of properties in the IIviIdentityinterface.)Vendor: Agilent Technologies.Description: IVI-COM Driver for Agilent Technologies 34405 Digital Multimeter.Revision: 1.0Component Identifier: Agilent34405.Agilent34405(The component identifier can be used to create an instance of the COMserver.)Hardware: This driver supports instruments manufactured by AgilentTechnologies. The supported model numbers are:34405AThis driver supports communicating with the instrumentusing USB.Software: See the section on installation in this document forinformation on what other software is required by this driver.More Information----------------For more information about this driver and other instrument driversand software available from Agilent Technologies visit: A list of contact information is available from: Microsoft, Windows, MS Windows, and Windows NT are U.S.registered trademarks of Microsoft Corporation. Copyright Agilent Technologies, Inc. 2005-2006