>How about Edit..Replace In Files: " Framework.App" -> " New Framework.App"?

If I do that, this will become a new object of the framework application available in each of those .vb files. Those, all the oApp properties won't be visible as this will become a totally new object.

Basically, the situation I am having is that before I was making a direct reference to Framework.App everywhere in all .vb files for whatever I needed. But, that was possible because of the Shared attributes on the properties and methods. The Shared attribute has been removed as it was causing too much problems, like one Web Service overwritting the Framework.App properties of another Web Service as soon as loaded. So, now, as there is no Shared attribute, in order to gain access to the framework application, I have to create an object of it.

So, this means, I need a way to make oApp available at the highest hierarchy as possible without having to pass that object to all methods I am calling.