As a follow up, you replied in email that you did have both code and design views open at the same time.
In the future, avoid that like the plague. Just work on one, then save, and work on the other. From what I'm seeing in your code file you sent, I'm thinking that since you had a code error, some sort of interaction with the VS.NET designer happened and it wasn't able to complete code generation so all the code that adds child controls to their parents is gone.
Most of your controls appear to be in place codewise. You can see by looking at InitializeComponent where VS.NET choked during code generation. Note that the first 10 or so controls didn't end up getting all their code generated while all the controls after that worked ok. The first 10 or so you'll have to set up again, but for the others, you're just missing the line to add them to their parent wizard page.
For the Wizard control, add these two lines:
For the two wizard pages, you're going to have to reconstruct the Controls.AddRange call that is normally there. That will be a little time consuming because you'll have to figure out what child controls were on each page. However it appears like the location and size and other properties of the child controls are in tact. So it's just a matter of adding back in the Controls.AddRange calls.
We have seen this sort of issue even when developing applications that don't use any third-party controls like ours. It's one of the things that you learn about after it's too late unfortunately. A lot of times when VS.NET code generation fails, it does it quietly and you don't find out until you try to run your app.
We've run in into it a lot when using UserControls and placing them on Forms. Sometimes the code for the UserControl in InitializeComponent just disappears for no reason.
Hope this helps!