Hi all,



I'm hoping that some of you clever chaps could offer me some advice on code
reuse.



You see, whenever I make applications, I typically only find very limited
scope for code reuse. I also only find limited use for inheritance. For
example, the various types of users that my system might have to deal with.



I'm wondering if anyone could give me some tips on how to identify areas of
my design that could be reusable, where I can use inheritance and where to
use interfaces. I've read all the books that talk about why these things are
important but very few of them show you how to do it in the real world.



If anyone could point me to some online resources on this then that would be
great. I could also do with a couple of books on how to spot reusable
aspects of my designs and so on.



Any help would be great



Thanks all



Simon

Hi Simon,

I think it is better to ask this question in a language group like
microsoft.public.dotnet.languages.vb
microsoft.public.dotnet.languages.csharp

Than you get probably an answer fit on the language you use.

Cor

Oh Ok,

The reason why I asked here is because its a subject that seems to cross
language boundaries.

I'll put it in C Sharp as well though

Simon

"Simon" <sh856531@microsofts_free_email_service.com> wrote in message
news:(E-Mail Removed)...
> Oh Ok,
>
> The reason why I asked here is because its a subject that seems to cross
> language boundaries.
>
> I'll put it in C Sharp as well though
>
> Simon
>
>
As a reminder, if you want your message to go to a *limited* number of
groups, it's better to cross-post (put multiple groups in the Newsgroups
field) rather than multi-post (put separate identical messages in different
groups).
FWIW, I found your post in the academic group.
Cross-posting allows a reply in any group to be seen in all addressed
groups, and saves you the trouble of monitoring multiple posts for answers.

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.

I think its all about how you design your applications. Like what i am doing
in my applications is creating packages for different modules and using it
in my applications. For example I have created packages for security,
exception handling, utility (for sending emails and common tasks) etc which
i can reuse with little change or no change based on my application's
requiements.

I think before you start your application design you have to think about
reusability and generic object creation which can be reutilized in other
projects. I believe mostly support objects can be re-utilized among
different projects.

Regards,

Sarfraz



"Simon" <sh856531@microsofts_free_email_service.com> wrote in message
news:(E-Mail Removed)...
> Hi all,
>
>
>
> I'm hoping that some of you clever chaps could offer me some advice on
code
> reuse.
>
>
>
> You see, whenever I make applications, I typically only find very limited
> scope for code reuse. I also only find limited use for inheritance. For
> example, the various types of users that my system might have to deal
with.
>
>
>
> I'm wondering if anyone could give me some tips on how to identify areas
of
> my design that could be reusable, where I can use inheritance and where to
> use interfaces. I've read all the books that talk about why these things
are
> important but very few of them show you how to do it in the real world.
>
>
>
> If anyone could point me to some online resources on this then that would
be
> great. I could also do with a couple of books on how to spot reusable
> aspects of my designs and so on.
>
>
>
> Any help would be great
>
>
>
> Thanks all
>
>
>
> Simon
>
>
>