Govert van Drimmelen

Hi @Sergey-Vlasov - can you split the first commit (fixing the reloading error) from the further reloading support into separate pull requests? I think I want to keep changes to...

I'm not keen on this handling of the nethost because of the version issues.

Thanks Dave - OK, we'll pull the ExcelDnaDoc into the Excel-DNA organization and take it from there. It's a really cool extension!

@augustoproiete That's great - you should have write access to the fork now, to at least sync it up. @mndrake can advise on what structure he would prefer going forward.

@mndrake OK - I've deleted it and I think you should now have permissions under Excel-DNA.

Yes I see this warning. It is somewhat hidden by the errors that don't make sense for types that are not defined. I'm wondering if there is a better upgrade...

> errors that don't make sense I mean errors that are hard to understand given that the package was just updated, and the assembly reference is in place.

I don't think it is a big problem - I just wanted to document it. I ran into it with an old project that was just targeting .NET 4 historically...

I think it's simpler to keep a separate copy of the nethost files. There is a way to reference a C++ package to get them, but that seems more complicated....

Another issue that can do with help without affecting the existing stuff is the whole PackageReference story: https://github.com/Excel-DNA/ExcelDna/issues/363 I don't know exactly how that should work yet, but you might...