Incorrect COMReference entry when using Office interop
See original GitHub issueTo include Excel interop libraries in .NET Core app, I do the following: Dependencies -> Add Reference -> COM -> Microsoft Excel 14.0 Object Library
. When I do this, I get the following ItemGroup
:
<ItemGroup>
<COMReference Include="Microsoft.Office.Excel.dll">
<Guid>00020813-0000-0000-c000-000000000046</Guid>
<VersionMajor>1</VersionMajor>
<VersionMinor>7</VersionMinor>
<WrapperTool>tlbimp</WrapperTool>
<Lcid>0</Lcid>
<Isolated>false</Isolated>
</COMReference>
</ItemGroup>
However, I get the following runtime error:
Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly ‘office, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’. The system cannot find the file specified.
In order to work, I have created .NET Framework app, added COM reference there and copied its COMReference - and it works:
<ItemGroup>
<COMReference Include="Microsoft.Office.Interop.Excel">
<Guid>{00020813-0000-0000-C000-000000000046}</Guid>
<VersionMajor>1</VersionMajor>
<VersionMinor>7</VersionMinor>
<Lcid>0</Lcid>
<WrapperTool>primary</WrapperTool>
<Isolated>False</Isolated>
<EmbedInteropTypes>True</EmbedInteropTypes>
</COMReference>
</ItemGroup>
As noted here, in order to fix the situation, the project system needs to add <EmbedInteropTypes>True</EmbedInteropTypes>
.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:19 (5 by maintainers)
Top Results From Across the Web
c# - Can't get Microsoft.Office.Interop reference to work
Use NuGet Package Manager in VS2015. Right click references in your visual studio project; Select Manage NuGet Packages ...
Read more >Problem with Microsoft.Office.Interop.Excel
Hello,. I have simple code to open a excel. But I couldn't open it.. I googled about this interop problem and tried every...
Read more >How to access Office interop objects - C# guide
Learn about C# features that simplify access to Office API objects. Use the new features to write code that creates and displays an...
Read more >Imports Microsoft.Office.Interop flagged as warning, not ...
I was able to repro the problem with the same entries in the registry, Win32 pointing to a bad location and Win64 points...
Read more >Studio - Microsoft Office Interop Issues
Causes. Microsoft Office installation issues may result in incorrect COM Interop configurations in the Windows registry. For example, this may ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m hitting this, just as above, in Sept of 2020. @davkean
Seems like you can’t do Office Interop with Core unless you do the com reference manually?
Tooling does this (wrong:)
Correct:
Repro steps:
netcoreapp3.1
console applicationMicrosoft.Office.Interop.Excel.Chart
)<EmbedInteropTypes>True</EmbedInteropTypes>
netcoreapp3.1
net471