StrataFrame Forum » StrataFrame Application Framework - V1 » Business Objects and Data Access (How do I?) » Setting up class inheritance layers for StrataFrame classes

Setting up class inheritance layers for StrataFrame classes

AlexSosa — Wed, 26 Sep 2007 09:23:20 GMT

When using VFP I've made it a practice to use two layers of inheritance for a purchased classes. An intermediate, shared among several projects and one specific to a project. The purchased classes are never changed, so updates are easy.

While there are issues that must be addressed with compund objects, the practice has proven effective and I'd like to continue it with Strataframe. What is the best way to go about it? If someone can offer actual examples I would appreciate them very much.

TIA,

Alex

RE: Setting up class inheritance layers for StrataFrame classes

StrataFrame Team — Wed, 26 Sep 2007 09:23:20 GMT

Aye, the templates are simply starting points that give you a few objects already dropped on the form for you to use. You can create your own templates and place them in %My Documents\Visual Studio 2005\Templates\ItemTemplates\. You can find lots of articles detailing how to create and modify templates by searching google for Visual Studio 2005 templates. So, yes, you would create a company-wide solution that would contain the projects that define the first level of inheritance, and then you create application-specific projects that define the second level of inheritance.

RE: Setting up class inheritance layers for StrataFrame classes

AlexSosa — Tue, 25 Sep 2007 14:24:40 GMT

Hi Ben,

Is that all there is? (Ignorance is NOT bliss).

If I understand correctly, the two layers of inheritance you suggested can be implemented like this: Create a Solution that produces a couple of DLLs with the first level of inheritance. Then, in the Application Solution include a couple of projects that define the second level of inheritance (DLLs) which are in turn the ones used by the apllication itself.

While we are talking about this, I am not sure if the "Templates" that one uses to create items to add to a project, for example "SF Maintenence Form", are classes that you can later modify and cause all modifications to be inherited by items based on the "template" (as it would be the case with VFP classes), or real templates that are simply copied and become starting points for you to modify. Can you clarify this point, please?

Thank you very much,

Alex

[quote]I am not sure what you are asking for here. Are you referring to the inherited business layer and UI controls? If so, this would be what you would create on your side:

[codesnippet]Public Class MyInheritedTextBox
Inherits MicroFour.StrataFrame.UI.WIndows.Forms.Textbox

End Class[/codesnippet][/quote]

RE: Setting up class inheritance layers for StrataFrame classes

Trent L. Taylor — Mon, 24 Sep 2007 21:04:04 GMT

[quote]Is it too much to ask you to share the source of those (unchaged) inheriting DLLs?[/quote]

I am not sure what you are asking for here. Are you referring to the inherited business layer and UI controls? If so, this would be what you would create on your side:

[codesnippet]Public Class MyInheritedTextBox
Inherits MicroFour.StrataFrame.UI.WIndows.Forms.Textbox

End Class[/codesnippet]

RE: Setting up class inheritance layers for StrataFrame classes

AlexSosa — Mon, 24 Sep 2007 15:24:13 GMT

Thank you, Ben, sounds reasonable.

From what you say you only subclass the Business and UI DLLs. Is it too much to ask you to share the source of those (unchaged) inheriting DLLs? At this stage I still suffer form "lack of ignorance" about ,NET :)

That would be much appreciated.

Alex

[quote][b]Ben Chase (09/24/2007)[/b][hr]Your best bet would be to create a core DLL that inherits the 3rd party classes. Then, create a project-specific DLL that inherits them again. There's not much more to it than that. :) We do the same thing. Every project has its own Business and UI DLL that contain the inherited classes.[/quote]

RE: Setting up class inheritance layers for StrataFrame classes

StrataFrame Team — Mon, 24 Sep 2007 09:01:22 GMT

Your best bet would be to create a core DLL that inherits the 3rd party classes. Then, create a project-specific DLL that inherits them again. There's not much more to it than that. :) We do the same thing. Every project has its own Business and UI DLL that contain the inherited classes.