Sounds reasonable. I guess there are not a lot of options on this issue and hard coding the relative paths probably isn't that big a deal. Even with the relative paths stored in tables or web.config, if the user moves the folders it would hose the application anyway. Glad you have arrived at a workable resolution. I have much to learn on this platform ... :-)

Bill

>Bill,
>
>>>On the other issue addressed in this thread, could you place any relative/absolute path related data in your web.config file and limit access to that file with permissions to protect the data, read this data and use it to find/load your controls?<
>
>Yes, we do this already for one set of "template" controls, but if the Web side of things get as complex as the Windows side of the app, then it's possible that the controls could be placed in a wide variety of sub-directories. I don't want to have a huge web.config file that constantly needs tweaking as the app grows. Too many deployment issues for that to be a viable way of handling it (this is *not* an in-house app, it's "shrink-wrapped").
>
>So, anyway, if you've read the rest of the thread, you'll see I've decided to go ahead and just code the relative paths & file name, it shouldn't change anyway.
>
>Thanks for your reply,
>~~Bonnie
>
>
>
>>Hi Bonnie,
>>
>>I'm sorry then, I don't know why the control would not be visible, but then I have not added cotnrols programmatically so I'm not familiar with the issues ( just getting started with the .NET stuff :-) ).
>>
>>On the other issue addressed in this thread, could you place any relative/absolute path related data in your web.config file and limit access to that file with permissions to protect the data, read this data and use it to find/load your controls?
>>
>>Bill
>>