Looking for:

Microsoft office 2010 primary interop assemblies redistributable not installing free download

Click here to Download


I also provided the direct link to the download page for each one of the prerequisites above. We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings. Privacy Statement. Required cookies are necessary for basic website functionality.

Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies. Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.

Some examples include: cookies used for remarketing, or interest-based advertising. Sign Up Log In. For example, if you have downloaded the. Or if you are familiar with MS DOS commands you can navigate to the download file location and run the same command. STEP 5. If you are extracting SFO 2. As you notice, there are no VSTO files. VSTO will be downloaded and installed if it is missing from your machine during the installation process prior to the SFO installation.

Also its best to use the. Unless its being pushed out and deployed by the IT team where they will need to push out the prerequisites first then push out SFO. During the install process make sure Outlook is closed and the end user is installing the SFO application. You need to make sure the. If not select it and click on okay and continue to install it STEP 7 For Office and users, you can use the opia.

The number in the file name indicates the bitness of Microsoft Windows. You wont be able to install the wrong bitness on your machine but you can always check the bitness of your Windows before running this file. Knowledge Article Number. Did this article solve your issue? Let us know so we can improve! Yes No. Sign up for a free trial.

Visual Studio installs these assemblies automatically. This set of the assemblies is used during some development tasks, such as when you run or debug projects. Visual Studio doesn’t install and register these assemblies; you need to do it yourself.

The PIAs are automatically added to a location in the file system, outside of the global assembly cache, while you install Visual Studio. When you create a new project, Visual Studio automatically adds references to these copies of the PIAs to your project.

Visual Studio uses these copies of the PIAs, instead of the assemblies in the global assembly cache, to resolve type references when you develop and build your project. When different versions of the PIAs are registered in the global assembly cache, you can face several development issues. The added copies of PIAs will help you to avoid such issues. For Visual Studio and later, these copies of the PIAs are installed to following shared locations on the development computer:.

To perform certain development tasks, the PIAs must be installed and registered in the global assembly cache on the development computer. Typically, the PIAs are installed automatically when you install Office on the development computer. For more information, see Configure a computer to develop Office solutions.

For more information, see Design and create Office solutions. Every Office project template in Visual Studio is designed to work with a single Microsoft Office application. To use features in multiple Microsoft Office applications, or to use features in an application or component that doesn’t have a project in Visual Studio, you must add a reference to the required PIAs.

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. If you’ve installed and registered the PIAs in the global assembly cache, these versions of the assemblies appear on the COM tab of the Reference Manager dialog box. Avoid adding references to these versions of the assemblies, because there are some development issues that can occur when you use them.

For example, if you’ve registered different versions of the PIAs in the global assembly cache, your project will automatically bind to the version of the assembly that was registered last, even if you specify a different version of the assembly on the COM tab of the Reference Manager dialog box.

Some assemblies are added to a project automatically when an assembly that references them is added. For example, references to the Office. The following table lists the primary interop assemblies that are available for Office , Office and Office 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. For example, when a solution that references a Office assembly runs on a computer that has the Office version of the same primary interop assembly, the binding redirect assembly instructs the.



Microsoft office 2010 primary interop assemblies redistributable not installing free download


What’s your detailed Office version, volume licensed version or click-to-run version? Best Regards, Winnie Liang Please remember to mark the replies as answers if they helped.

If you have feedback for TechNet Subscriber Support, contact tnsf microsoft. Click here to learn more. Visit the dedicated forum to share , explore and talk to experts about Microsoft Teams. Bradley, Have you fixed this somehow? I am going totally ballistic with Sage, Sage Support and O I have reinstalled office and it didn’t help at all, more over, I took Windows 10 , , and clean installs – same issue.

Before repairing Outlook, uninstalling Sage as Sage suggests or editing or installing anything, you must ensure that the path to your invoice, purchase order, sales layouts etc. If not, Outlook can’t find them and you will see an error message similar to this ” Please install Redistributable Primary interop assemblies to run this function. After a recent Sage Line 50 V26 upgrade we had to move our layouts and reports to the new folder which Sage creates during the upgrade.

We use Windows 10 Build and Office which has Outlook and the problem you mention above is exactly what we encountered. Sage suggests uninstalling Sage and Microsoft Office and reinstalling Office first followed by Sage, but by checking this first, you may save yourself considerable time.

I hope this helps someone. If you are attempting to attach an additional document to the e-Mail, say a set of Terms and Conditions, then the path or filename may have changed. Select the Email Attachments tab and check that the path of any attachments is correct and that you have access to them. Any amendment does not trigger a request to save the file – you must save the file manually to preserve any changes. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals.

Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Sign in to vote. I am trying resolve an issue with office We use sage and we cannot get the integration with sage 50 working with office. For further help with this, contact your IT administrator or refer to Microsoft support. Wednesday, May 23, PM. Hi Jon, What’s your detailed Office version, volume licensed version or click-to-run version?

Based on the error description, please try the following suggestion: Ensure that you have a version of the. NET Framework that is no older than 2. Install Microsoft Office and make sure that the. NET Programmability Support feature is selected for the applications you want to extend this feature is included in the default installation. Thursday, May 24, AM.

Monday, May 28, AM. Hi, I am checking the status of this issue. Do you have any update for it? Please feel free to post back if you need further help. If my reply is helpful to this question, please remember to mark it as answer to close the thread.

Your action would be helpful to other users who encounter the same issue and read this thread. Thanks for your understanding. Monday, June 4, AM. Hello I am having exactly the same issue with Sage using Office I have tried uninstalling and reinstalling Office but it hasn’t helped.

Do you have any up to date advice? Thanks Bradley. Monday, June 10, AM. I have number of computers where printing statements work, and the rest return exact this error. Tuesday, December 10, PM. Wednesday, June 10, PM. The issue is almost certainly a problem with a path definition inside the report.

Tuesday, August 4, AM.