Steve Fabian wrote
I know at least one person has voiced an opinion that if the repository 4.0 module required DNN 5.0 and .Net 3.5 it would be a disaster for him, however it's difficult to support the type of functionality I'm building in .Net 1.1 and/or 2.0, and the effort to support 2 code bases would be overwhelming.
I am also considering at this point, releasing 4.0 as a brand new module, NOT an upgrade. Which means that you will be able to run Repository modules version 3.01.15 and 4.0.0 side by side on the same DNN site. I would certainly provide an 'import' or 'conversion' process for moving your 3.X modules over to 4.0, but I do not want to leave the 3.X users in a lurch if DNN 5.0/.Net 3.5 is not an option for them.
haha, that will be me. Anyway, after a lot of consideration. I will migrate my DNN production site to a new server that support .NET 3.5, once DNN 5.0 is ready to run on production site.
After all, you can't just being pull back by Obsolete users like me. :) We have to catch up the technology, although it cost a lot...
Secondly, I would agree too if it will release as a new module. For the "import / conversion from 3.+" it seems not so useful for me if 4.0 has whole new functions that 3.+ don't have. However, being able to import / export as xml or csv will be great. (Can work as RSS feed too maybe?)
Once again, Thank you so much Steve!
George.