Microsoft.office.interop. owc11

I'm afraid we did not install or support OWC on our shared hosting environment. Ray , Nov 22, I can under stand that you do not support MS Office Web Comp on your server, but what I can't understand is why up to a few days ago was I able to deploy my site changes with no problem and be able to navigate to the default page through the URL? The OWC reference has been in the project since day one.

Has something change on your end in the past week? Did you make sure you uploaded all the required assemblies and components in your applications Bin folder? Ray , Nov 23, Michael , Nov 23, The only files I see in my Bin folder are Ajax related, and if I remember correctly these are the only files have ever been in this folder.

If I need to add some other dll files in the Bin that point directly to any needed OWC reference would not be a problem if I new which ones to add? Like I already stated that from the beginning of the project I have had a reference to the Microsoft Office Web Components I did not think that I needed to add anything to the bin folder to make this work, and that I have been able to navigate fine to my URL for months.

I'll take any suggestions on what I need to upload in the Bin to correct this issue. Thanks for your support Privacy policy. To use the features of a Microsoft Office application from an Office project, you must use the primary interop assembly PIA for the application. Interested in developing solutions that extend the Office experience across multiple platforms?

Check out the new Office Add-ins model. When you create a new Office project, Visual Studio adds references to the PIAs that are required to build the project. Separate primary interop assemblies to build and run projects. Use features of multiple Microsoft Office applications in a single project. Full list of primary interop assemblies for Microsoft Office applications.

For more information about primary interop assemblies, see Primary interop assemblies. Visual Studio uses different sets of the PIAs on the development computer.

These different sets of assemblies are in the following locations:. This set of the assemblies is used when you write code and build projects. 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.

Thanks for helping make community forums a great place. Click HERE to participate the survey. You need to have COM controls installed, not only an interop. Thank you for replying. Where i have to find the dll location in local machine.

The content you requested has been removed. Ask a question. Quick access. Search related threads. Remove From My Forums.