Steve Taylor wrote
Fuji,
Thanks for clarifying those points. I started again with the source edition of DNN just to be sure before getting your answer.
I'm now finally up and running with the 04.00.01 RC1 Events module in DNN 4.8.2 - however, there were still a couple of frustrating issues to resolve before success came my way.
1. The DotNetNuke.Events.SqlDataProvider project lacked a couple of references - it could not find DotNetNuke.dll or Microsoft.ApplicationBlocks.Data.dll - the first is present in Library\bin and in Website\bin and I wasn't sure which to use (does it matter?) - so I linked the project to the one in Library\bin. As for the MS assembly, I found that in Website\bin.
2. The DotNetNuke.Events project was also unable to resolve references to DotNetNuke.dll which I linked in from Library\bin
3. Less seriously, there are still a few more broken links which dont seem to be show-stoppers, but I'll list these here FYI:
In project DotNetNuke.Events - DNN_Events.dnn is missing - I think this is an import definition file which you can create anyway from the host login - is that so?
In project DotNetNuke.Events.SqlDataProvider - Uninstall.SqlDataProvider is missing
4. In your blog you mention changing DotNetNuke.Events references in the web project from bin to Project, but there were none to change. I initially found this confusing but assume that it is because I did not install the old events module whilst installing DNN?? I added the new DotNetNuke.Events project references in and all seemed to be well.
I can now add events to a page in DNN using the module and it seems to run without error.
I am glad to hear that you get that far.
1. Ersnt Peter packaged the module for distribution. The references path on your PC may not be the same as his and thus it shows error. For me, I usually link DotNetNuke and ApplicatinBlocs to Library\bin and Library\Components\DataAccessBlock respectively
2. See answers above
3. Missing files - best to be addressed by Ernst Peter.
4. If the ref is not there, you can add them. Your analysis is correct.
Background: the Events team lead Ernst Peter does all the builds. After each build, the DNN Events team members do internal test. If bugs are found, we fix and check the code back into the source control Vault. Ernst Peter then builds a new package and releases for internal testing. Ernst Peter uses NAnt tool to automate the on-going builds. The Source package contains references to support NAnt buiild and if you do not use NAnt, you can ignore the missing files or manually fix the references. No pain no gain...