You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to Excel-DNA/ExcelDna#188 and Excel-DNA/ExcelDna#193, ExcelDnaDoc relies on PowerShell scripts to install/uninstall which are not supported in projects using PackageReference.
ExcelDnaDoc's install.ps1 basically does two things:
Replicates everything that ExcelDna.AddIn's install.ps1 does, and adds a reference to ExcelDna.Documentation.dll in the .dna file for it to be packed.
Adds a post-build event to run ExcelDnaDoc.exe and generate the CHM
For (1), I suggest we remove all the PowerShell scripts, and document that when using ExcelDnaDoc's attributes, the developer needs to manually add the Reference entry to the .dna file.
For (2), I suggest we bundle an MSBuild script into the NuGet package, and make it part of the build as described in Excel-DNA/ExcelDna#32
The text was updated successfully, but these errors were encountered:
Similar to Excel-DNA/ExcelDna#188 and Excel-DNA/ExcelDna#193, ExcelDnaDoc relies on PowerShell scripts to install/uninstall which are not supported in projects using PackageReference.
ExcelDnaDoc's
install.ps1
basically does two things:install.ps1
does, and adds a reference toExcelDna.Documentation.dll
in the .dna file for it to be packed.For (1), I suggest we remove all the PowerShell scripts, and document that when using ExcelDnaDoc's attributes, the developer needs to manually add the
Reference
entry to the.dna
file.For (2), I suggest we bundle an MSBuild script into the NuGet package, and make it part of the build as described in Excel-DNA/ExcelDna#32
The text was updated successfully, but these errors were encountered: