Microsoft.office.core assembly

Collectives on Stack Overflow. Learn more. NET core 3. Asked 2 years, 3 months ago. Active 2 months ago. Viewed 32k times. I am trying to use the recently-released. WriteLine app. Version ; app. The system cannot find the file specified. Word This package may not be fully compatible with your project. Word' is compatible with all the specified frameworks in project implying 'compatible' but not 'fully compatible' Is there a way to do this or must I use.

NET Framework instead of Core? I am using Windows 10,. Improve this question. Peter Hull. Peter Hull Peter Hull 6, 4 4 gold badges 37 37 silver badges 42 42 bronze badges.

Possible duplicate of core 2. You get that warning every time you try to use a. NET Old assembly from. NET Core. Explore Why Office? Android ASP. Ask a question.

Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Word for Developers. Sign in to vote. Anyone have any suggestions for this very basic problem? Monday, August 30, AM. Hi Amy I confirm that this is an issue with Office I think perhaps a service pack for VS should do something about this? Marked as answer by ckapilla Tuesday, August 31, AM. Monday, August 30, PM. I'd like to help out with a few points, if I can. This posting is provided "AS IS" with no warranties, and confers no rights.

I very much suspect the latter. If that's the case, then you should continue your researches in the appropriate newsgroup venue.

In this forum, only projects based on the VSTO templates are supported. I reference the interop but not the native one in my project, but I realize that by virtue of its being in the GAC, the native one is always visible. How do I hide it from the compiler or tell the compiler to ignore it?

If you've got your head set on this course, then probably the best place to get an answer to this question is the Framework. Interop newsgroup. Dev Center. Explore Why Office? Android ASP. Ask a question. Quick access. Search related threads. Remove From My Forums. However, following the procedures I used above, it worked just fine: using System; using System.

Generic; using System. If you do post some code, you should make it the smallest example possible that I can cut-and-paste so I can see the problem for myself. A large listing that doesn't compile is often not much use. Core never appear in the list of references. Using Office setup, removed then reinstalled the. Net Programming support for all the components of Office, the problem remains unchanged. I also made sure that I've downloaded the SP and updates for Office Perhaps this is my problem?

The section of code where I need the Microsoft. Core reference: Excel. AddTextbox MsoTextOrientation. Thanks, Michael. I was able to get it to work like this: Excel. Core dll. Something is keeping it from properly adding the right proxies to your reference list. Here's something else to try: 1. Remove the Excel, Microsoft. Close down Visual Studio to make sure it isn't holding any file locks. Are you using Visual Studio ?

There was a problem with this on some machines that was similar to this, which was incredibly difficult to fix. Look in the directories of your project, looking for interop assemblies. They are named Interop.

Delete the Interop. Maybe reboot after that, but I'm not sure that's necessary.