-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Usage clarification #46
Comments
I don't know about /Documentation - I don't see it in my little test project. Generating the HelpTopic links automatically would be nice, but I'm not sure how easy it is. We need this information both at compile time, for the help file, and at runtime when registering the functions with Excel. So we need a way to remember the HelpTopic allocations that are made at compile time when the help file is built. One way would be to modify the output assembly during the ExcelDnaDoc build step, using something like Mono.Cecil to rewrite the attribute information. Another option might be to write this information to the .dna file somehow, and use at runtime. Anyway, it seems kind of tricky and needs some thought. How would you approach it? Is it worth the effort? |
To be honest I had no idea how to approach it. I naively thought that this could be done manipulating somehow that part of the code
Yesterday, meanwhile I did a quick fix on my side as part of my post-build event to add all missing HelpTopic ..... |
Hello @govert ,
I used to have 2 folders /Documentation and /HelpContent useful for Documentation but it seems they can now be removed (at least I haven't notice any side effects). Can you confirm?
Also is there an option to have by default all functions linked to the generated help instead of having manually to put HelpTopic = XXX on each function ? I imagine by default most people want the link to work, instead we could use something like HelpTopic=None if someone wants voluntarily to break the link? What do you think? I could give it a try if you think that is a good idea ...
PS: maybe, in the documentation you could add that Summary tag accept html code ....
The text was updated successfully, but these errors were encountered: