>Hi,
>
>>I have been on it since yesterday afternoon. Basically, the design will be as Rick suggested by breaking down the oProcess functionality of the application object and tieing the application object to oProcess for any hit coming from the Web. So, basically, the application object will be created once. Then, at every page, I will create only the oProcess object which will tie the application object to it by the use of oProcess.oApp.
>>
>>So, the framework has been adjusted and completed. I need to adjust both applications now. The first one is always done. But, I had to adjust about 4000 lines - thanks for replace all. :)
>
>I see Rick's powers of persuasion were greater than mine <g>
>
>I haven't used VB.NET since 2.0 came out - is there refactoring support? (It can make things a lot simpler and less error prone than just using find & replac

VB comes with a limimted version of Refactor! which looks nicer, is nicer in some ways (especially the local refactor!) but doesn't do a great job on global refactorings (it only does a Safe Rename). I use Refactor! with C# in addition to the built in Refactoring and I'm glad I have it because some of the built in refactoring is so damn slow.

I was about to send a message to Michel regarding refactoring too but I think you can't refactor composition like this. You can rename easily but in this case he's changing an object reference to an object with a sub object which you can't refactor.