Ok, I am an experienced C# developer and I am learning DNN and VB.Net as I build my first custom modules. I built my first custom module and with a few learning experiences, everything works ok. But now I am adding  a second custom module to my development environment and as you folks all know all modules have a DataProvider.vb class. Now both of my custom modules seem to be having problems with it's DataProvider class. They are both in their own unique namespaces, but they both now have the blue squiggly lines under their name in their respective classes and both are stating that "DataProvider is ambiguous in the namespace 'The.Respective.Class.Namespace'". So how do you fix this in VB.net? What am I doing wrong? I thought each compiled module project had to have a DataProvider class that was inherited from the DNN DataProvider. Can someone please help with how to fix this problem.

Steve Graddy

I've found using the dynamic compilation model of ASP.Net 2.0 and DNN 4.x, that is almost a necessity to use fully qualified names for nearly all references. This has been especially true with respect to some of my own base and helper classes with namespace of WESNet.DNN causing ambiguous references with particular module classes having a namespace of WESNet.DNN.Modules.ModuleName.  Unfortunately, the conflicts do not always show themselves during development, but wait until the module is packaged and installed on a test site to first cause problems.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner