Added CheckMediaDirectoryHash and CheckProfileHash options to genRSS. A profile can now have the following options:
CheckMediaDirectoryHash uses a hash of the directory structure instead of LastWriteTime to determine whether the media files have changed and to republish the RSS. This can be better because checking LastWriteTime won't detect changes if only a file was deleted. If CheckMediaDirectoryHash is set to yes then each time the script is called, it will compute the MD5 hash value of the MediaDirectory using MD5CryptoServiceProvider and save it into the RSS. When it is called again, it will pull the hash from the RSS and compare the values. The hash will be saved in as a child of the element outside of the element of the RSS. If CheckMediaDirectoryHash is no or is not set, genRSS compares the file with the latest LastWriteTimeUtc to the time the RSS was last generated () to know whether to update republish the RSS.
CheckProfileHash updates the RSS file if there are changes to the podcast profile. Normally, genRSS will only update the RSS file when there is a new episode. If CheckProfileHash is set to yes then the next time the script is called, it will put the MD5 hash value of the profile into the RSS using Get-FileHash. When it is called again, it will pull the hash from the RSS and compare the values. If they are different, then it knows that the profile was updated and the RSS needs to be regenerated and republished. The hash will be put into as a child of the element outside of the element in the RSS.
Added
CheckMediaDirectoryHashandCheckProfileHashoptions to genRSS. A profile can now have the following options:CheckMediaDirectoryHashuses a hash of the directory structure instead of LastWriteTime to determine whether the media files have changed and to republish the RSS. This can be better because checking LastWriteTime won't detect changes if only a file was deleted. IfCheckMediaDirectoryHashis set toyesthen each time the script is called, it will compute the MD5 hash value of the MediaDirectory using MD5CryptoServiceProvider and save it into the RSS. When it is called again, it will pull the hash from the RSS and compare the values. The hash will be saved inCheckMediaDirectoryHashisnoor is not set, genRSS compares the file with the latest LastWriteTimeUtc to the time the RSS was last generated (CheckProfileHashupdates the RSS file if there are changes to the podcast profile. Normally, genRSS will only update the RSS file when there is a new episode. IfCheckProfileHashis set toyesthen the next time the script is called, it will put the MD5 hash value of the profile into the RSS using Get-FileHash. When it is called again, it will pull the hash from the RSS and compare the values. If they are different, then it knows that the profile was updated and the RSS needs to be regenerated and republished. The hash will be put into