Use this forum to ask questions after your subscription maintenance expires or before you buy. Need information on licensing or pricing? Questions about a trial version? This is the right place for you. No scripting questions, please.
Forum rules 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.
This topic is 6 years and 10 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
My apologies, I wasn't trying to say there should be one. I was just making sure I have everything. It could have been you only sent the .psm1, so I wanted to make sure.
Also, I just want to confirm my understanding based on what you said earlier: If I modify a module without bumping its version number (which I guess is what would happen if I don't have a manifest), PowerShell Studio won't see the changes (new functions, etc.) unless I remove and re-add it through the cache editor?
Well, the versioning exists for that reason. If you modify the version as you update a module, you just need to rebuild the cache. It should pick it up automatically.
If it sees V0.0 and it already has that, it won't update it. So yes, you need to specifically import it again.
It is not really required to have a manifest for a module, but my personal opinion is that it should be
Having a valid version resource is a best practice for all types of modules across all types of programming languages.
This topic is 6 years and 10 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.