Sergey Vlasov

I've fixed dscom not building when targeting .NET Framework: https://github.com/Excel-DNA/ExcelDna/pull/614 Requires `true` in a project file.

I've added DsComTlbExportAssemblyPaths initialization from our build: https://github.com/Excel-DNA/ExcelDna/pull/615 With this change, there is no need to add it to a project file.

Maybe we should mark the whole ExcelDna.Registration package as Obsolete instead of marking individual methods once I complete the migration?

If we plan to pack the .chm file into the .xll file that will be implemented in ExcelDna.AddIn, I think copy .chm file to publish directory should also be implemented...

As I understand, System.Reflection.Metadata comes with .NET Core and VS MSBuild. I’m (unfortunately?) can’t reproduce the problem from the discussion on my machine(s). Tried VS 2022 17.1.6 and VS 2019...

I've retested it with VS 2019 on my main workstation and on a clean VM with the project attached and still can't reproduce the problem. Wondering what may cause it......

Implemented in https://github.com/Excel-DNA/ExcelDna/pull/581 https://github.com/Excel-DNA/ExcelDnaDoc/pull/47