DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
How can I get PowerShell HelpWriter to recognize the file has changed? I understand I can start a new help file and have it import the existing settings. However I'm using version control on the help file like a good developer and that process feels wildly unnecessary and bothersome.
Is this possible or did I just create a new feature request?
Running PowerShell HelpWriter 1.0.10
Thank you for posting, josh a.
Did you remember to include the following?
- 1. Product, version and build (e.g. Product: PowerShell Help Writer 2015, Version & Build: 1.0.9. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
2. Specify if you are running a 32 or 64 bit version
3. Specify your operating system and if it is 32 or 64 bit.
4. Attach a screenshot if your issue can be seen on the screen
5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.
If not, please take a moment to edit your original post or reply to this one.
*** Make sure you do not post any licensing information ***
How would you like HelpWriter to respond when the code changes? For example, if a parameter is removed, should it delete your description, or just mark the parameter as deleted?
What if an attribute is changed, like ValueFromPipeline? You'd want to know (or be reminded), because you might want to change your examples.
1. Notification in tree navigation of items that have changed
- Green icon and/or text if it is a new item (cmdlet, parameter, parameter set)
- Yellow/Orange icon and/or text if it is a cmdlet that has changes
- Red icon and/or text if it no longer exists in the module.
2. Having a separate view of all the changes identified would be helpful. This could be an output of the rescan process.
3. There should be an automatic scan whenever the help file is loaded.
4. There should be a button to support a manual scan.
5. Should have an option to point the file to compare with a different module. i.e. what happens if I change the module on the system but the help writer isn't loading that new module for some reason.
6. Attribute changes would also be helpful to see.
I'll add another reply to the thread if I think of anything else along these lines.
Please keep the ideas coming. This is a 1.0, so we're counting on you to help us direct future releases.
SAPIEN Technologies, Inc.
Who is online
Users browsing this forum: No registered users and 1 guest