Hi all,

just to add my 2 cents there, I wrote a post a couple of months ago, which I think relates to the same background issues developped in that thread.

Would you guys consider having a look ?

Cheers

---

Jesse CTO - Aricie

Well, the new membership implementation did not break the API, it did break some underlying functionality. Those modules broke becuase they did not use the API as it should be, those are hacks, wich qualify as a core modification. So it is expected they wouldn't run on later versions.

The fact that there aren't any patches to make em work on the latest versions suggests alot on the quality of those developers. I can only say: "I hope you bought them with the source included"


Ditching .NET1.1 and going fully to generics instead of arraylists WILL introduce breaking changes. To the same magnitude as 2.1.2 => 3.0.13. That's why I hope they introduce them in DNN5, wich should be the next major release (fingers crossed). It's for the greater good of the platform. The code will run much beter if it can use all of .NET2.0 new features. Now the code has to be held back because of 3.x.


This all doesn't mean 3.x will go away, there's still lots of DNN1 and DNN2 sites, snowcovered is still selling modules for them. You can keep using 3.2.2 for the next 15 years if you like. But halting the development of the platform as an incentive for lazy developers to fix a module is something I can not understand or support.

---

Edit your Skin.xml and Container.xml files with:
Yannick's SXE