I was just wondering if you guys have considered putting all your forms in a seperate project in a windows app, outside of the main .exe. Today I had a developer from another division want to display one of our app forms from within their application. Can you think of any downsides to this? I guess when I think of reuse, I think from the BL down to the DL, not the UI.

Why not? A resource is a resource. Though, I have to say, when you have to reuse windows forms, it's better to create them as user controls, and stick them on a form when you need them.

Otis wrote:

Why not? A resource is a resource. Though, I have to say, when you have to reuse windows forms, it's better to create them as user controls, and stick them on a form when you need them.

Yes, I agee. Our application is full of user controls and custom controls, however, they are re-used within our application, not across applications. What is the benefit of re-using usercontrols, rather than forms across apps?

Thanks!

MarcoP wrote:

Otis wrote:

Why not? A resource is a resource. Though, I have to say, when you have to reuse windows forms, it's better to create them as user controls, and stick them on a form when you need them.

Yes, I agee. Our application is full of user controls and custom controls, however, they are re-used within our application, not across applications. What is the benefit of re-using usercontrols, rather than forms across apps?

A control can be placed on a form, a form can't be added to a form So with a form, you can't use it in a tab control (unless the form is an mdi container) or in other user controls.