I'm a new comer to dotnetnuke and asp.internet altogether. I have to produce a module package that's simple to install on the different DNN site. However , SQL tables along with other database objects have to be added by hand. I'd like these to be added in instantly once the package is used. When I stated I'm a new comer to all of this along with a step-by-step explanation could be very useful.
This really is handled by SqlDataProvider files.
Note, that after you produce a DotNetNuke Put together Module project in VS2010 (or VS2008), you finish track of three such files, a couple of that are of interest here (I believe)
- 01.00.00.SqlDataProvider is performed upon Module Installation
- Un-install.SqlDataProvider operates upon Uninstallation
Note inside your DNN Manifest file, you will find records pointing to those SqqDataProvider files:
<file> <name>01.00.00.SqlDataProvider</name> </file> <file> <name>Uninstall.SqlDataProvider</name> </file>
Also note, within the manifest file, the version number matches the prefix around the installer SQL file:
Finally, you'll package your DNN Module right into a .zip file. The precise structure evades me, but DNNCreative and also the book recommended below have ample info.
After you have the deployable .zip file, you put in it as with every other module you may buy off SnowCovered.
My Suggestion would be to perform the following
- Watch some recent DNNCreative video tutorials on custom module development. They explain this method in great detail.
- Read Mitchel Seller's book: http://www.amazon.com/Professional-DotNetNuke-Programming-Mitchel-Sellers/dp/0470171162 -- It describes all of the fun tweaks towards the SQL scripts / manifest to aid multiple versions of the module
I made use of both assets and located them very helpful