Beta

Beta Planning

Changes:

1. Create XML configuration in AppData folder
2. Store database in Documents folder (or customized location)
3. Add Module Manifest file
4. Install to Program Files (x86) directory

Configuration will include:

• [Service factory] type
  • Location of database file
• Root location of audio files (single directory or multiple?)

Module Manifest will include:

• Required assembly references
• Helper functions (exported)
• [Beta API changes] to PS API

Install to Program Files directory:

• In order to simplify deployment and provide a GUI application, I am going to install the module to its own program files directory
• A shortcut will load the module into its own PowerShell command prompt

I do not plan to include help documentation. The PS syntax auto-generated by PowerShell v2 is sufficient for users familiar with PowerShell and I am not targeting others yet. Also, I need to take a look at generating the help documentation files.

I have decided to tackle adding a bit more abstraction to the underlying code than previously considered. Including the configuration of a type of [Service factory] gives me the ability to move in the future from a local database to a cloud-based service and does not significantly change the amount of work involved. The result will be something much more flexible, opening this up to more than just a Windows PowerShell client. I think that would be cool. Hey, I would like to run this on my Ubuntu machine was well.