Intellisense AutoOpen Error
László Sleisz
Initialization [Error] DnaLibrary AutoOpen Invoke Error : FileNotFoundException - A(z) „ExcelDna.IntelliSense, Version=1.1.0.0, Culture=neutral, PublicKeyToken=f225e9659857edbe” fájl vagy szerelvény, illetve annak egyik függősége nem tölthető be. A rendszer nem találja a megadott fájlt.
I use:
- VS 2022 with C#
- Excel 2016
- .Net Framework 4.6.2
- ExcelDna.AddIn 1.8.0
- ExcelDna.Integration 1.8.0
- ExcelDna.IntelliSense 1.8.0
InteliSense.cs:
using ExcelDna.Integration;
using ExcelDna.IntelliSense;
public class IntelliSenseAddIn : IExcelAddIn
{
public IntelliSenseAddIn()
{
}
public void AutoOpen()
{
IntelliSenseServer.Install();
}
public void AutoClose()
{
IntelliSenseServer.Uninstall();
}
}
.cs
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net4.6.2-windows</TargetFramework>
<LangVersion>8.0</LangVersion>
<Nullable>enable</Nullable>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="ExcelDna.Addin" Version="1.8.0" />
<PackageReference Include="ExcelDna.Integration" Version="1.8.0" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="ExcelDna.IntelliSense" Version="1.8.0" />
</ItemGroup>
<ItemGroup>
<Reference Include="ExcelDna.IntelliSense">
<HintPath>bin\Debug\net4.6.2-windows\ExcelDna.IntelliSense.dll</HintPath>
</Reference>
</ItemGroup>
</Project>
Thanks
Govert van Drimmelen
<!-- Semicolon separated references list to include in .dna. -->
<!-- Default value: empty -->
<ExcelAddInInclude></ExcelAddInInclude>
You can specify additional .dll libraries to pack by adding an ‘ExcelAddInInclude’ property in your project file, with a ‘;’-separated list of assemblies to pack.
Or you can set it up so that all .dll files in the output directory are packed into the publish\-packed .xlls.
To do this you add an extra target in your project file to build the ‘ExcelAddInInclude’ property automatically
<Target Name="PackedReferences" AfterTargets="AfterBuild" BeforeTargets="ExcelDnaBuild">
<ItemGroup>
<References Include="$(OutDir)*.dll" Exclude="$(OutDir)$(TargetFileName)"/>
</ItemGroup>
<PropertyGroup>
<ExcelAddInInclude>@(References)</ExcelAddInInclude>
</PropertyGroup>
</Target>
László Sleisz
László Sleisz
<PropertyGroup>
<TargetFramework>net4.6.2-windows</TargetFramework>
<LangVersion>8.0</LangVersion>
<Nullable>enable</Nullable>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="ExcelDna.Addin" Version="1.8.0" />
<PackageReference Include="ExcelDna.Integration" Version="1.8.0" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="ExcelDna.IntelliSense" Version="1.8.0" />
</ItemGroup>
<ItemGroup>
<Reference Include="ExcelDna.IntelliSense">
<HintPath>bin\Debug\net4.6.2-windows\ExcelDna.IntelliSense.dll</HintPath>
</Reference>
<HintPath>C:\Program Files (x86)\METAS\Metas.UncLib\Metas.UncLib.Core.dll</HintPath>
</Reference>
<Reference Include="Metas.UncLib.LinProp">
<HintPath>C:\Program Files (x86)\METAS\Metas.UncLib\Metas.UncLib.LinProp.dll</HintPath>
</Reference>
</ItemGroup>
<Target Name="PackedReferences" AfterTargets="AfterBuild" BeforeTargets="ExcelDnaBuild">
<ItemGroup>
<References Include="$(OutDir)*.dll" Exclude="$(OutDir)$(TargetFileName)"/>
</ItemGroup>
<PropertyGroup>
<ExcelAddInInclude>@(References)</ExcelAddInInclude>
</PropertyGroup>
</Target>
Govert van Drimmelen
Yes, I think they would be packed – you can see full details of the packing in the build output.
If you don’t want some of the .dll files in the output directory to be packed, then you either need to change the ‘PackedReferences’ target specification somehow, or just explicitly list all the libraries that you do want to pack in an <ExcelAddInInclude> list, without having the extra Target etc.
I also suggest you change the invalid TargetFramework moniker from
<TargetFramework>net4.6.2-windows</TargetFramework>
to something like
<TargetFramework>net472</TargetFramework>
See Target frameworks in SDK-style projects - .NET | Microsoft Learn
Some of the Excel-DNA libraries already require .NET Framework 4.7.2 or later, and that’s the oldest version still supported by Microsoft.
So I’d suggest targeting 4.7.2 instead of 4.6.2. The “-windows” platform suffix is only used for .NET core versions (.NET 6.0+).
-Govert
--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/exceldna/22b9233c-c496-449e-bef4-fc4c96d61346n%40googlegroups.com.
László Sleisz
Govert van Drimmelen
If you don’t pack the extra assemblies, you will have to copy them next to the -packed.xll for it to work.
Are there errors when you use METAS UncLib under .NET Framework 4.7.2?
On Windows the .NET Framework version gets updated automatically, and has very high compatibility.
You also cannot have .NET Framework 4.6.2 installed alongside a newer .NET Framework 4.x version.
I ask because the next Excel-DNA version will only support .NET Framework 4.7.2+ and I would like to know if there are real issues with this.
To view this discussion visit https://groups.google.com/d/msgid/exceldna/b1871381-ae29-4653-b0da-899c58b17b9an%40googlegroups.com.
László Sleisz
1>MSBUILD : PackExcelAddIn error DNA-818471385: Exception: System.IO.FileLoadException: Could not load file or assembly 'NationalInstruments.UI.Styles3D, Version=19.0.40.49152, Culture=neutral, PublicKeyToken=dc6ad606294fc298' or one of its dependencies. Attempt to load an unverifiable executable with fixups (IAT with more than 2 sections or a TLS section.) (Exception from HRESULT: 0x80131019)
1>MSBUILD : PackExcelAddIn error DNA-818471385: File name: 'NationalInstruments.UI.Styles3D, Version=19.0.40.49152, Culture=neutral, PublicKeyToken=dc6ad606294fc298' ---> System.IO.FileLoadException: Attempt to load an unverifiable executable with fixups (IAT with more than 2 sections or a TLS section.) (Exception from HRESULT: 0x80131019)
1>MSBUILD : PackExcelAddIn error DNA-818471385: at System.Reflection.RuntimeAssembly.nLoadImage(Byte[] rawAssembly, Byte[] rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark, Boolean fIntrospection, Boolean fSkipIntegrityCheck, SecurityContextSource securityContextSource)
1>MSBUILD : PackExcelAddIn error DNA-818471385: at System.Reflection.Assembly.Load(Byte[] rawAssembly)
1>MSBUILD : PackExcelAddIn error DNA-818471385: at ResourceHelper.ResourceUpdater.AddAssembly(String path, String source, Boolean compress, Boolean multithreading, Boolean includePdb)
1>MSBUILD : PackExcelAddIn error DNA-818471385:
1>MSBUILD : PackExcelAddIn error DNA-818471385:
1>PackExcelAddIn: ~~> Assembly path NationalInstruments.UI.WindowsForms.dll resolved to bin\Debug\net472\NationalInstruments.UI.WindowsForms.dll.
1>PackExcelAddIn: -> Updating resource: Type: DNA, Name: __MAIN__, Length: 2301
1>PackExcelAddIn: -> Updating resource: Type: ASSEMBLY_LZMA, Name: METAS.VNA.DATA, Length: 204968
1>PackExcelAddIn: -> Updating resource: Type: ASSEMBLY_LZMA, Name: NATIONALINSTRUMENTS.UI.WINDOWSFORMS, Length: 98699
1>PackExcelAddIn: -> Updating resource: Type: ASSEMBLY_LZMA, Name: NATIONALINSTRUMENTS.COMMON, Length: 219904
1>PackExcelAddIn: -> Updating resource: Type: ASSEMBLY_LZMA, Name: MICROSOFT.OFFICE.INTEROP.EXCEL, Length: 229816
1>PackExcelAddIn: -> Updating resource: Type: ASSEMBLY_LZMA, Name: NATIONALINSTRUMENTS.UI, Length: 406690
1>PackExcelAddIn: -> Updating resource: Type: ASSEMBLY_LZMA, Name: METAS.GUICONTROLS, Length: 461007
1>PackExcelAddIn: Completed Packing bin\Debug\net472\publish\SparameterCorrection-AddIn64-packed.xll.
1>Done building project "SparameterCorrection.csproj".
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========
========== Rebuild completed at 11:24 and took 17,597 seconds ==========
Govert van Drimmelen
Okay, yes, it is definitely possible to exclude the NationalInstruments*.dll files from being packed.
You can achieve this by modifying the Exclude attribute within the ItemGroup definition for References. The Exclude attribute can accept multiple patterns, separated by semicolons (;).
Here's how you can modify your Target:
Explanation:
- Include="$(OutDir)*.dll": This still initially selects all .dll files in your output directory ($(OutDir)).
- Exclude="$(OutDir)$(TargetFileName);$(OutDir)NationalInstruments*.dll": This now tells MSBuild to remove items from the included set that match either of these patterns:
- $(OutDir)$(TargetFileName): Your main project's output DLL (as before).
- $(OutDir)NationalInstruments*.dll: Any DLL in the output directory whose name starts with "NationalInstruments".
The @(References) item list passed to the ExcelAddInInclude property will now contain all DLLs from the output directory except your main project DLL and any National Instruments DLLs.