ExcelDNA in VS2019 not showing core files

42 views
Skip to first unread message

Leigh Tilley

unread,
Mar 19, 2020, 1:22:17 PM3/19/20
to Excel-DNA
Hi

I've recreated my VS2017 ExcelDNA project in VS2019 on another machine.

It builds and then I noticed it is not an xll and also that two key files are missing in the project tree.

packages.config and the .dna file.

Presumably these are key to the build and creation. How do I get them into the 2019 setup.

Apologies if I have missed build and setup issues for VS2019. 

Thanks

Leigh

Govert van Drimmelen

unread,
Mar 19, 2020, 1:28:21 PM3/19/20
to exce...@googlegroups.com

Hi Leigh,

 

If you created a new project, check that it targets “.NET Framework” and not “.NET Standard”.

There are different project templates.

You need to end up with an old-style project file, and not a ew SDK-style project file.

 

For Excel-DNA you also need to use the old “packages.config” style Nuget references.

This is an option in Visual Studio to set the default, but to change a project is harder.

 

A screenshot of a cell phone

Description automatically generated

 

-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 on the web visit https://groups.google.com/d/msgid/exceldna/1fc21e41-a1f4-4d30-aaa1-a38063e56721%40googlegroups.com.

image001.png

Leigh Tilley

unread,
Mar 20, 2020, 7:19:08 AM3/20/20
to Excel-DNA
Hi Govert

Thanks for the prompt reply! :)

Yeah VS2019 looks v flexible but where I was busy I did it quickly and it did confuse me at first! Initially I had a C++ project (not done C++ since uni!!) and then VBA and now clearly .NET Standard! :)

I will create a new one in the way you mentioned!

Thanks alot.

Leigh

On Thursday, 19 March 2020 17:28:21 UTC, Govert van Drimmelen wrote:

Hi Leigh,

 

If you created a new project, check that it targets “.NET Framework” and not “.NET Standard”.

There are different project templates.

You need to end up with an old-style project file, and not a ew SDK-style project file.

 

For Excel-DNA you also need to use the old “packages.config” style Nuget references.

This is an option in Visual Studio to set the default, but to change a project is harder.

 

A screenshot of a cell phone

Description automatically generated

 

-Govert

 

 

 

From: exce...@googlegroups.com <exce...@googlegroups.com> On Behalf Of Leigh Tilley
Sent: 19 March 2020 19:22
To: Excel-DNA <exce...@googlegroups.com>
Subject: [ExcelDna] ExcelDNA in VS2019 not showing core files

 

Hi

 

I've recreated my VS2017 ExcelDNA project in VS2019 on another machine.

 

It builds and then I noticed it is not an xll and also that two key files are missing in the project tree.

 

packages.config and the .dna file.

 

Presumably these are key to the build and creation. How do I get them into the 2019 setup.

 

Apologies if I have missed build and setup issues for VS2019. 

 

Thanks

 

Leigh

--
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 exce...@googlegroups.com.

Leigh Tilley

unread,
Mar 20, 2020, 8:25:03 AM3/20/20
to Excel-DNA
Hey

All good; new project in parallel created and all code copied over.

Compiles.

I set a launch / debug config and it launched Excel 365 64bit.

It doesn't like the IntellisenseServer Addin start. It broke on exception / uninstall.

and then showed this:

Capture.PNG

Leigh Tilley

unread,
Mar 20, 2020, 8:27:35 AM3/20/20
to Excel-DNA
Here's my IntellisenseServer class, works in VS2017 / Excel 32 setup:

int.PNG

Govert van Drimmelen

unread,
Mar 20, 2020, 8:49:40 AM3/20/20
to exce...@googlegroups.com

I’m guessing the exception you see when loading IntelliSense is the “LoaderLock” Managed Debugger Assistant.

This warning relates to code in the IntelliSense server that monitors the Excel process for libraries loaded or unloaded. I believe the callback we run here is safe to execute under the OS Loader Lock, so this warning can be switched off in the debugger.

 

Could the error pop-up you see be from something else in your AutoOpen, or some other library of yours that is loaded at startup that is trying to talk to Excel?

 

-Govert

 

 

From: exce...@googlegroups.com <exce...@googlegroups.com> On Behalf Of Leigh Tilley
Sent: 20 March 2020 14:25
To: Excel-DNA <exce...@googlegroups.com>
Subject: Re: [ExcelDna] ExcelDNA in VS2019 not showing core files

 

Hey

 

All good; new project in parallel created and all code copied over.

 

Compiles.

 

I set a launch / debug config and it launched Excel 365 64bit.

 

It doesn't like the IntellisenseServer Addin start. It broke on exception / uninstall.

 

and then showed this:

 

To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/e863c66d-59ff-4752-82b8-6c7a68f94f36%40googlegroups.com.

image002.png

Leigh Tilley

unread,
Mar 20, 2020, 9:06:13 AM3/20/20
to Excel-DNA
Hey

Ah it is a new laptop with this being the first thing to be developed / copied over to it.

Microsoft Book 2 Windows 10 64bit with Excel 365 64bit.

I just added the location of the xll to the Trust Center safe places but this did not change it.

Despite the stock on breakpoint being disabled it shows the modal dialog in Excel and that's it.

I copied the error, above, and googled it which led me back to other threads on here but nothing clear as to what the others did to solve it.

Leigh Tilley

unread,
Mar 20, 2020, 9:10:29 AM3/20/20
to Excel-DNA
I tried changing the Project debug setting to the 32bit xll just to try but when I click start there's platform detection somewhere as the argument gets changed back to the 64bit one (which is obviously what we want anyway :) )

Govert van Drimmelen

unread,
Mar 20, 2020, 9:23:54 AM3/20/20
to exce...@googlegroups.com

We need to check whether the error pop-up is really related to the IntelliSense, and if it happens on that machine even with a simple project.

 

  1. Does the pop-up AutoOpen / TargetInvocationException error go away if you don’t run the IntelliSenseServer.Install() ?
  2. Does the pop-up AutoOpen / TargetInvocationException error also appear with a new, simple add-in where you make a new project, install the ExcelDna.AddIn and ExcelDna.IntelliSense packages from NuGet and add the IntelliSenseServer.Install() call and a simple UDF function?

To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/cbba4b15-cd51-4c62-a323-2e98f124734e%40googlegroups.com.

Leigh Tilley

unread,
Mar 20, 2020, 9:31:10 AM3/20/20
to Excel-DNA
Hey

OK install/uninstall commented out; now runs.

Simple one and also my custom Cube/ActivePivot methods are there and callable too.

Obviously need to get the IntelliSense server working though as it's nice to provide IT view/text!


int disabled.PNG

Govert van Drimmelen

unread,
Mar 20, 2020, 9:38:01 AM3/20/20
to exce...@googlegroups.com

Can you try with these specific pre-release version of ExcelDna.AddIn (v1.1.0-beta1) and of ExcelDna.IntelliSense (v1.3.0-beta1)?

 

-Govert

 

 

From: exce...@googlegroups.com <exce...@googlegroups.com> On Behalf Of Leigh Tilley
Sent: 20 March 2020 15:31
To: Excel-DNA <exce...@googlegroups.com>
Subject: Re: [ExcelDna] ExcelDNA in VS2019 not showing core files

 

Hey

 

OK install/uninstall commented out; now runs.

 

Simple one and also my custom Cube/ActivePivot methods are there and callable too.

 

Obviously need to get the IntelliSense server working though as it's nice to provide IT view/text!

 

 

To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/62162f40-f930-41d3-9d77-f49ed6ed0b96%40googlegroups.com.

image002.png
Reply all
Reply to author
Forward
0 new messages