1. Microsoft.visualstudio.ole.interop Version 7.1 2
2. Microsoft.visualstudio.ole.interop Version 7.1 Download
3. Microsoft.visualstudio.ole.interop Version 7.1 7

I am getting the above error message when I attempt to run a VB console app that I wrote in Visual Studio. There does not seem to be ANY reference to Microsoft.VisualStudio.OLE.Interop Version 7.1.40304.0 anywhere in any of the files I'm looking. My program runs fine on my development PC, but does not seem to run on any machine on which I attempt to deploy.

Microsoft.VisualStudio.OLE.Interop 7.10.6071. Package Manager.NET CLI; Paket CLI. Install-Package Microsoft.VisualStudio.OLE.Interop -Version 7.10.6071. Dotnet add package Microsoft.VisualStudio.OLE.Interop --version 7.10.6071. Paket add Microsoft.VisualStudio.OLE.Interop.

If this is not the correct place for this message, kindly correct me gently. I've spent 20 minutes looking at every option in the Forum Categories and the forums listed underneath each one and cannot seem to find a place for this message that's any more appropriate than this one.

Thanks in advance, Scott. Robin, Why the deployment need that dll reference, although there's no office interop in OP's project as OP said? I also think there's some place applied this dll reference, but OP has not checked out. @ScottDarth, I suggest you to check the references in your project, maybe you have not apply that dll but the project added this reference before.

We don't know why you the deployment need this dll reference, but if you need the installer work, then I think the only way is allow the request, install this dll reference(you can reference my first post to install this dll reference) to the system. If there's any concern, please feel free to let us know. Best wishes, Mike MSFT MSDN Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. Hi ScottDarth, The Microsoft.VisualStudio.OLE.Interop is in the package, you can try to download it and install it in the computers. Or, you can use the following method: Add these lines to the PostBuild event textbox (replace with the path to your copy of gacutil.exe): ' gacutil.exe' -u '$(TargetName)' ' gacutil.exe' -i '$(TargetPath)' The first line (which uses the TargetName parameter) removes any existing version of your tool from the GAC. The second line (which uses the TargetPath parameter) installs the current version of your tool into the GAC.

If there's any concern, please feel free to let us know. Have a nice weekend! Mike MSFT MSDN Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. Mike, He says his application does not use the interop dll's, so there's something else going on here. If he doesn't use them, then he shouldn't install them just because there's something wrong with his deployment. It could be that he has some kind of secondary reference going on, and there's some distant memory I can't seem to pull out about the interops being included when they aren't required. I'll do some searching after he answers my question about the Application Files.

RobinDotNet Microsoft MVP, Client App Dev. Robin, Why the deployment need that dll reference, although there's no office interop in OP's project as OP said?

I also think there's some place applied this dll reference, but OP has not checked out. @ScottDarth, I suggest you to check the references in your project, maybe you have not apply that dll but the project added this reference before. We don't know why you the deployment need this dll reference, but if you need the installer work, then I think the only way is allow the request, install this dll reference(you can reference my first post to install this dll reference) to the system. If there's any concern, please feel free to let us know. Best wishes, Mike MSFT MSDN Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Microsoft.visualstudio.ole.interop Version 7.1 2

HOWTO: Reference a Visual Studio assembly in the GAC from an add-in Author: Carlos J. Quintero (Microsoft MVP) Applies to: Microsoft Visual Studio.NET 2002 Date: February 2007 Microsoft Visual Studio.NET 2003 Updated: October 2012 Microsoft Visual Studio 2005 Microsoft Visual Studio 2008 Microsoft Visual Studio 2010 Microsoft Visual Studio 2012 Introduction Visual Studio uses assemblies that, among others, are in one of these subfolders of C: Program Files:. Common7 IDE. Common7 IDE PublicAssemblies. Common7 IDE PrivateAssemblies But some assemblies are installed only in the Global Assembly Cache (GAC). The GAC is a special folder typically located at:.NET Framework 1.0, 1.1, 2.0, 3.0 and 3.5: C: Windows Assembly.NET Framework 4.0 and 4.5: C: Windows Microsoft.NET assembly The GAC stores different versions of shared assemblies used at run-time by.NET applications. The GAC is actually a set of folders, but when you use the Windows Explorer to browse the first of the GACs (C: Windows Assembly), a shell extension shows a unified view (assembly name, version, culture, public key token and arquitecture) of all installed assemblies.

Microsoft.visualstudio.ole.interop Version 7.1 Download

The othe GAC folder (C: Windows Microsoft.NET assembly) doesn't have such shell extension. Sometimes your add-in project needs to reference an assembly that is only in the GAC or installing the VSIP / Visual Studio SDK, for example, the Microsoft.VisualStudio.OLE.Interop.dll assembly. More Information If you don't want to install the Visual Studio SDK stuff on your computer just to reference an assembly that is only in the GAC, since Visual Studio doesn't allow to add references to an assembly in the GAC (because the GAC is a deployment feature, not a development feature) you can follow this procedure to extract the assembly from the GAC that has the shell extension (C: Windows Assembly):.

Microsoft.visualstudio.ole.interop Version 7.1 7

Open a MS-DOS command window (click Start, Run. Type cmd and press enter). Use the SUBST command to map a drive letter to the GAC folder: SUBST G: C: Windows Assembly That maps the drive letter G: to the GAC folder. With the SUBST command you bypass the shell extension.

Use Windows Explorer to browse the G: folder. You will see the actual folders, with names like GAC, GAC32, GACMSIL and one subfolder for each assembly. Once you locate the assembly DLL that you are looking for, you can copy it outside the GAC, to the bin folder of your add-in project and add a reference to it. For example, the Microsoft.VisualStudio.OLE.Interop.dll is in the folder G: GAC Microsoft.VisualStudio.OLE.Interop 7.1.40304.0b03f5f7f11d50a3a. When done, you can undo the mapping the using: SUBST G: /D Most Visual Studio assemblies are not redistributable, which means that your setup should not include them. Rather, Visual Studio (which installs those assemblies in the GAC) should be a prerequisite on the target computer.

Copyright © 2000-2018 MZTools Software. All Rights Reserved.