I used to use Makisu to restore WAP provisioning a while back. It just created a XML file for easy import. Perhaps it would be worth looking into for your update.
In any case, I support you in continuing the development here. WM is loosing all of our good devs to other platforms. We need to hold onto the ones we can.
I wouldn't say i was good! EXCT2 is a learning project more than anything but i am the sort of person that starts a project like this because it is hard and i want become the best i can at something. This project has meant that I've had to ask for help from many places. There are a couple of people in the RD forum that are possibly a little annoyed with me and a certain MSDN community support person that has spent more time than is fair helping me out but in the end it will be worth it for everyone.
With regards to the projects status. I've spend the last 10 days working on the XML creation code. I've had a few problems most notably with MS' decision to dynamically name the exchange partner registry keys on a per device basis. This is almost solved thanks to a, frankly, brilliant idea from me and Ultrashot's coding example, i just need to understand his solution and implement it. The other problem was creating the XML file itself without consuming massive amounts of RAM. This is pretty much solved for now in the development version but i have concerns that it may come back to haunt me later in the project as i combine the OMA provisioning development/P.O.C (Proof Of Concept) application with EXCT2.
The registry key side of things will need more work because although it works, the P.O.C version of this side of EXCT2 uses 2 blocks of RAM and that's too much, so i will need to figure out a better way of coding the registry reading to .reg code but this will come with a better under standing of the XML writing code as i have taken a far better approach with that because i understand now that having (at worst) 20+ variables per sub function is very inefficient. You can get way with that sort of thing as a noob coding for the PC but it just doesn't fly on a mobile device. You'll crash the whole OS before you even loaded anything useful.
Also with the XML side almost finished and my UI skills sucking really hard I'm looking for beta testers and graphic designers. Credits will be given and if you really try hard enough i may be tempted to do more for you but no promises. The graphic designer/s will have it hard because i want it to look exactly like it was shipped with all versions of the energy rom (so matching DJC's theme and NRGZ's theme exactly for example) and i would like a bunch of banners made up.
Finally, i am looking for feature suggestions. There are rules to this though. First up if it's in EXCT1 final I'm not interested coz that base is covered. Second, if it's a weird third party app that not many people use, again I'm not interested. Third, if you have a request that isn't one of the above i would appreciates a .reg file with the paths or an example OMA XML file i can work from, in the latter case both the .reg and XML is probably best because the registry paths can be hard to dig out.
On a side note, i know i have lost most of the original user base (all 1500+ downloads) to other platforms but i really want this to be successful so expect an portal announcement when the time is right and expect a call to port this to android and WP7 (if that is even possible. Android may require a complete rewrite to C++). i already have interest from friends for an android port so this is possibly likely in the future.
Anyway, enough of me and thank you cajun for the interest. I don;t want to sound cheesey but you have just spurred me on a little