creating a dotnetnuke package with easy to install sql database -
i new dotnetnuke , asp.net altogether. need create module package easy install on different dnn site. problem sql tables , other database objects need added manually. them added automatically when package deployed. said new , step step explanation helpful.
thanks,
jelena
this handled sqldataprovider files.
note, when create dotnetnuke compiled module project in vs2010 (or vs2008), end 3 such files, 2 of of concern here (i think)
- 01.00.00.sqldataprovider executed upon module installation
- uninstall.sqldataprovider run upon uninstallation
note in dnn manifest file, there entries pointing these sqqdataprovider files:
<file> <name>01.00.00.sqldataprovider</name> </file> <file> <name>uninstall.sqldataprovider</name> </file>
also note, in manifest file, version number corresponds prefix on installer sql file:
<version>01.00.00</version>
finally, package dnn module .zip file. exact structure evades me, dnncreative , book referenced below have plenty of info.
once have deployable .zip file, install other module might buy off snowcovered.
my suggestion following
- watch recent dnncreative training videos on custom module development. explain process in great detail.
- read mitchel seller's book: http://www.amazon.com/professional-dotnetnuke-programming-mitchel-sellers/dp/0470171162 -- explains fun tweaks sql scripts / manifest support multiple versions of module
i used both resources , found them useful
Comments
Post a Comment