I did figure out that the vb files could be attached to the ascx files by changing the ascx's reference to the code from codebehind to codefile. But... just doing this causes a whole other world of errors.

I guess all the development I've been doing has been using WSP. I didn't even realize WAP could be used with asp.net sites any more.

So am I to assume that the core modules are probably all still VS2003 modules? I'm really dreading going back to VS2003 to make the mods I need. Is there an easy way to be able to work on them in VS2005 without having to re-write them?

The features I'm ultimately looking for is to add the following to the Events module:
1. template email that can be selected from a list of them for each event 
2. the ability to schedule multiple reminder emails, for example 3 days before, 2 days before, and the day before the event
3. the email reminders need to include a driving directions link (mapquest, google maps, etc) that pulls the address from the users registration and the event address for source and destination
4. and whatever other crazy ideas my client thinks up

I'm natuarally assuming the easiest way to get these features and whatever else is probably to modify the existing events module.

Makes sense now... I think. I assume most 3rd party modules would be WAPs that compile to dll's so we can't mess with the code without buying the source, eh?

How do I update a WAP module?

Do I need to do something special to it or change some option in VS2005 to be able to work with it?