a nice question :)

Although you can go both ways (mine and Bertcord's), I think that in the end you will tune your solution and get exactly what I describe in my tutorial... so yes I would advise you to go with my proposition.

As for the future, 2 things are already in the making...

1. MSBuild Web Deployment project to handle deploying the outputs, alternativly zipping the module, building it as a release

2. Visual Studio templates - made in a smart way, which are configurable by a wizard that lets you choose exactly what you need for your solution.

 

now... if only a day had more than 24 hours...:(

 

---

Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources

and then Vladan core team nomination!    if it wasnt for these types of tools..  DNN would hold no value for me.

I would be interested in more info on the WAP approach to module development.

We have focussed on the dynamic approach (so far) for two reasons.

1. WAP requires Visual Studio - while the dynamic approach does not.
2. From a purely numbers point of view, we feel more developers would be impacted by tools that support the dynamic (WSP) approach.

However, in the long-term we would like to be able to provide tools for the whole community, and I don't see it as a huge undertaking to add the ability to port 3.x modules to 4.x (WAP) to the Upgrade Wizard.

You guys seem to have found a solution that does not require two different versions of the core.

---

Charles Nurse Chief Architect Evoq Content Team Lead, DNN Corp. Want to contribute to the Platform project? - See here

MVP (ASP.NET) and ASPInsiders Member