Would you mind posting an update to the module status?

I know this can be annoying, I am in a precarious timing situation with a major update to our city webpage.
The functionality you are building would hit a couple important situations for us.

1st a need for a very dynamic repository module.  The second would be for a Template driven content module

We need to move existing content for our downtown page that I think could work very nicely with the functionality you are building.

Thanks

Hey Phil,
As always, thanks for the interest, it's always a 'bump' in my energy level to hear people are looking forward to the new module.

So, here's the scoop... I'm running into some tough technology decisions.  On the one hand, I want to be able to take advantage of all the latest toolkits and technologies like .Net 3.5, Linq, AjaxControlToolkit, WCF, etc. and there's some cool new stuff in DotNetNuke 5.0 (Cambrian).  So the issue is .. do I target a moving train and require DNN 5.0 as the mininum version supported? and even tougher, do I use Linq and some of the other .Net 3.5 goodies.  The highly dynamic nature of the module lends itself really, really well towards Linq, but DNN 5.0 initially will remain .Net 2.0, and there are some integration issues with Linq and WCF that still need to be worked out ( I believe there's a Linq issue if you are using an ObjectQualifier  in your DNN installation ) as well as some expected installation issues if I target a platform greater than DNN itself.

It's not an impossible task, I am currently running verison 4.0 of the Repository module on my own site, http://www.gooddogs.com/dotnetnuke, which is running DNN 4.8. I just had to upgrade my site to .Net 3.5, then add the web.config sections for Linq. So it is possible. But I need to balance the advantages of developing using the newer technologies vs. the installation, configuration and support issues if I step too far ahead of the core platform.

Hey Steve,

I ran into something very similar when I was trying to decide whether to go with DNN 2.x or wait for DNN 3 for our City Intranet.
I decided to go with 3 and paid quite dearly.  The very long delays and breakage of modules earned me bad reviews at work.
I have since weighed the these decisions very carefully but truthfully I am always working with these types of decisions.

In your case I would look at it like this.  
If you could have a current version working that would demonstrate well the direction you are going, and would allow it's own eocosystem to start growing then I would move aggressively in that direction. 

The reason I say this is because the alternative is really matched up with DNN 5.1 or possibly later.  You have added enough variables to the mix that it will be quite a bit of time before all those stars align.

Even if you keep the module in permanent Beta during these initial stages as Microsoft did with their AJAX implementation you will have many people like me willing to get on board.
This will accelerate your move to the next level.

The Events group recently started placing their Betas out there and I think the feedback and excitement helped.

This may sound self serving but it is my honest opinion.

My final questions are: 
  Are you doing all this development yourself?
  I have a particular need that I think your template engine would fulfill.  Would you consider a sponsored application?