Steve Taylor wrote Am almost up and running now with the help of your blog - very clear. By the way, I love the zoomed images - are these generated by another DNN module? 1. Minor typo in your blog: When you say Add project DotNetNuke.Events.SqlDataProvider to solution: line 4 should read: Select "DotNetNuke.Events.SqlDataProvider.vbproj" 2. Roger Selwyn in his reply above suggested that I need not install the Source edition of DNN, just the Install. Hence, I did not have access to the Library code and was not able to follow your instructions to make the DotNetNuke.Events project reference DotNetNuke.Library instead of Bin - is this likely to cause me a problem? Will I need the source edition of DNN after all? 3. In your instructions to replace bin references to project references for Events module code you did not change the reference to DotNetNuke.Modules.Events.SqlDataProvider to DotNetNuke.Events.SqlDataProvider in the project - was this intentional, or an oversight? (the zoomable image shows the other events code references set to project but SqlDataProvider left as bin). Thanks a lot, Steve

Zoom image feature - a result of Windows Live Writer, Snagit and MetaPost.  MetaPost is an excellent DNN module that enables offline blog/web publishing.  It's a must have tool for me. 

Responses:

1.  Correct the typo of SqlDataProvider

2.  It is personal reference.  For me, I need to see DNN CORE source code to understand and resuse existing code.  You can get by with reference to bin\dll.

3.  Oversight on my part.  Added the SqlDataProvider to the instructions.

I am glad you pointed out the shortcoming in my blog.  It would certainly help the next person.  Don't forget to come back in the forum and share with the community your DNN Events endeavor.

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...