I'm creating multiple modules for use in DNN 6.1.5. The modules reside in a single project. I used the Christoc templates to develop the modules, and msbuild tasks (required by the templates) to package them. My .DNN file contains two <package> entries within <packages> - one for each module. Everything works great except for one thing - the resources.zip file is not being generated correctly.
Within each package, I have the following entry for the resource file:
<component type="ResourceFile">
<resourceFiles>
<basePath>DesktopModules/CompanyFolder</basePath>
<resourceFile>
<name>Resources.zip</name>
</resourceFile>
</resourceFiles>
</component>
After the msbuild task completes, I have a resources.zip file that contains files for ALL modules, not the specific module I was targeting. This makes sense, since I was referencing the same file name in each module. (Duh moment...)
So I thought I should give each resource file a unique file name in the .dnn file (based on the module). In other words, for the payroll component, I would call it PayrollResources.zip. For the phone directory component, I would call it PhoneDirectoryResources.zip. I'm hoping this will work. However, I don't know how to automate the generation of these files. The msbuild task appears to be hard-coded to use a file name of resources.zip. It doesn't care what file name is specified in the .dnn file.
So my questions are... 1) Am I on the right track in regards to zipping the resources and 2) is there an easy way to automate the generation of unique resource.zip file names as part of the build / packaging process? (I assume the msbuild script would need to be tweaked, but this is not an area that I'm very familiar with. Any assistance in this area would be greatly appreciated.)