how to make a second copy of a form

[TM]

I have a form that I would like to use, with a few small code and control
text changes, and was wondering if there was any way that I could somehow
save another cop of the form so I can just import it code and all.

Thanks

--
Tony

[Tom Leylan]

"TM" <no********@nothing.com> wrote...

I have a form that I would like to use, with a few small code and control
text changes, and was wondering if there was any way that I could somehow
save another cop of the form so I can just import it code and all.

So far all I have been doing is renaming the form and then using Save As...
the original will still be on the drive. Then you just add an existing
form, select the first one and it's back.

Tom

[Armin Zingler]

"TM" <no********@nothing.com> schrieb

I have a form that I would like to use, with a few small code and
control text changes, and was wondering if there was any way that I
could somehow save another cop of the form so I can just import it
code and all.

Solution explorer: Select file, Ctrl+C, Ctrl+V
or Drag&Drop holding down the Ctrl key

Maybe it's even better to create two Forms and move the common code to a
common base Form.
--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[Luke Vogel]

"Armin Zingler" <az*******@freenet.de> wrote in message
news:e6****************@TK2MSFTNGP09.phx.gbl...

"TM" <no********@nothing.com> schrieb

I have a form that I would like to use, with a few small code and
control text changes, and was wondering if there was any way that I
could somehow save another cop of the form so I can just import it
code and all.
Solution explorer: Select file, Ctrl+C, Ctrl+V
or Drag&Drop holding down the Ctrl key

Maybe it's even better to create two Forms and move the common code to

a common base Form.

I might be missing something here, but wouldn't it be simpler to inherit
the base form and apply changes rather than duplicate the code in
another file?

Luke.

[Armin Zingler]

"Luke Vogel" <pr**********@netscape.net> schrieb

"Armin Zingler" <az*******@freenet.de> wrote in message
news:e6****************@TK2MSFTNGP09.phx.gbl...

"TM" <no********@nothing.com> schrieb

I have a form that I would like to use, with a few small code
and control text changes, and was wondering if there was any way
that I could somehow save another cop of the form so I can just
import it code and all.

Solution explorer: Select file, Ctrl+C, Ctrl+V
or Drag&Drop holding down the Ctrl key

Maybe it's even better to create two Forms and move the common code
to

a

common base Form.

I might be missing something here, but wouldn't it be simpler to
inherit the base form and apply changes rather than duplicate the
code in another file?

If you want two Forms to inherit from one base form, you need even three
files (not necessarily but if you want to use the designer) - without having
duplicate code.
--
Armin

[One Handed Man [ OHM ]]

Not really possible in VB.NET, I assume you are conversant with other
langauges which use templates like C++

Regards - OHM

TM wrote:

I have a form that I would like to use, with a few small code and
control text changes, and was wondering if there was any way that I
could somehow save another cop of the form so I can just import it
code and all.

Thanks

Best Regards - OHMBest Regards - OHM On**********@BTInternet.Com

[Herfried K. Wagner [MVP]]

* "TM" <no********@nothing.com> scripsit:

I have a form that I would like to use, with a few small code and control
text changes, and was wondering if there was any way that I could somehow
save another cop of the form so I can just import it code and all.

Develop a common base form and inherit the 2 forms from this form.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Cor]

Herfried,

I think Armin Zingler did give the right answer.

Develop a common base form and inherit the 2 forms from this form.

This could be the intention but not the question.

I think with your answer should also be a sentence as

"Do you know how to do that?

You know only positive ment to keep our quality high.

:-)

Cor

[Herfried K. Wagner [MVP]]

* "Cor" <no*@non.com> scripsit:

I think Armin Zingler did give the right answer.

Develop a common base form and inherit the 2 forms from this form.

This could be the intention but not the question.

Yep. I know that. But I think it's the preferred way. I would not
create "copies" of one source file and make little modifications.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Jay B. Harlow [MVP - Outlook]]

Tony,
I would recommend the same as Luke & Herfried.

Define a base form with the common functionality then inherit each
specialized version from this common base.

A good place to learn about Inheritance is:
http://msdn.microsoft.com/library/de...ithObjects.asp

For samples of Visual Inheritance, which is used with forms:
http://msdn.microsoft.com/library/de...nheritance.asp

http://msdn.microsoft.com/library/de...l/vs0201gs.asp

Hope this helps
Jay

"TM" <no********@nothing.com> wrote in message
news:uH**************@TK2MSFTNGP09.phx.gbl...

I have a form that I would like to use, with a few small code and control
text changes, and was wondering if there was any way that I could somehow
save another cop of the form so I can just import it code and all.

Thanks

--
Tony

[TM]

Very interesting. Much for thought.

Thank you all

--
Tony

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...

Tony,
I would recommend the same as Luke & Herfried.

Define a base form with the common functionality then inherit each
specialized version from this common base.

A good place to learn about Inheritance is:
http://msdn.microsoft.com/library/de...ithObjects.asp
For samples of Visual Inheritance, which is used with forms:
http://msdn.microsoft.com/library/de...nheritance.asp
http://msdn.microsoft.com/library/de...l/vs0201gs.asp
Hope this helps
Jay

"TM" <no********@nothing.com> wrote in message
news:uH**************@TK2MSFTNGP09.phx.gbl...

I have a form that I would like to use, with a few small code and control text changes, and was wondering if there was any way that I could somehow save another cop of the form so I can just import it code and all.

Thanks

--
Tony

[Luke Vogel]

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

* "Cor" <no*@non.com> scripsit:

I think Armin Zingler did give the right answer.

Develop a common base form and inherit the 2 forms from this form.

This could be the intention but not the question.

Yep. I know that. But I think it's the preferred way. I would not
create "copies" of one source file and make little modifications.

That's what I'd have thought. Seems to me that one of the big
advantages of VB.NET and Object Oriented Programming is that of
inheritance, and in this case, visual inheritance lends itself
beautifully to "a few small code and control text changes".

I'm only a newbie myself, but my study of the subject points to
Herfried's answer as the better solution.

Luke.

[Herfried K. Wagner [MVP]]

* "Luke Vogel" <pr**********@netscape.net> scripsit:

I think Armin Zingler did give the right answer.

Develop a common base form and inherit the 2 forms from this form.

This could be the intention but not the question.

Yep. I know that. But I think it's the preferred way. I would not
create "copies" of one source file and make little modifications.

That's what I'd have thought. Seems to me that one of the big
advantages of VB.NET and Object Oriented Programming is that of
inheritance, and in this case, visual inheritance lends itself
beautifully to "a few small code and control text changes".

I'm only a newbie myself, but my study of the subject points to
Herfried's answer as the better solution.

Everybody with < 5 years of experience with .NET (me too) is a "newbie".

;-)

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Cor]

Hi Jay B,

I disagree (in this case not in general), please see my comments at Luke.

I would recommend the same as Luke & Herfried. This is what I disagree

Define a base form with the common functionality then inherit each
specialized version from this common base.

This is what I agree

Cor

[Cor]

Hi Luke

I have a form that I would like to use, with a few small code and control
text changes, and was wondering if there was any way that I could somehow
save another cop of the form so I can just import it code and all.

I disagree with you and all others who stated it is that inheritance is the
right answer for this.

If it is about a form with 6 panels on it, on some a tabpage on some a
slider, in a docked panel, than a menu on it, a statusbar, a datagrid with
as in the microsoft samples dataaccess on it, that only needs some changes
for another project and only needs some slight changes, I would not think
one minute about inheriting that form.

When we are talking about making first a nice base form with nice colors we
want to use, a standard statusbar, the fonts etc, I think I agree with you.

Just a thought,

Cor

[One Handed Man [ OHM ]]

If you think about it Cor, using an inherited form makes perfect sense for
some applications. However, I do agree with you that there is a case for
some functionality to allow template forms.

In fact forms inheritance can in some instances be annoying. This can happen
when you want the basic design but need to change some details of the
private members, its more akward really than being able to simply choose a
new form from a tamplate.

Thats what I think anyway.

OHM#

Cor wrote:

Hi Luke

I have a form that I would like to use, with a few small code and
control text changes, and was wondering if there was any way that I
could somehow save another cop of the form so I can just import it
code and all.

I disagree with you and all others who stated it is that inheritance
is the right answer for this.

If it is about a form with 6 panels on it, on some a tabpage on some a
slider, in a docked panel, than a menu on it, a statusbar, a datagrid
with as in the microsoft samples dataaccess on it, that only needs
some changes for another project and only needs some slight changes,
I would not think one minute about inheriting that form.

When we are talking about making first a nice base form with nice
colors we want to use, a standard statusbar, the fonts etc, I think I
agree with you.

Just a thought,

Cor

Regards - OHM# On**********@BTInternet.com

[Herfried K. Wagner [MVP]]

* "Cor" <no*@non.com> scripsit:

I have a form that I would like to use, with a few small code and control
text changes, and was wondering if there was any way that I could somehow
save another cop of the form so I can just import it code and all.

I disagree with you and all others who stated it is that inheritance is the
right answer for this.

If it is about a form with 6 panels on it, on some a tabpage on some a
slider, in a docked panel, than a menu on it, a statusbar, a datagrid with
as in the microsoft samples dataaccess on it, that only needs some changes
for another project and only needs some slight changes, I would not think
one minute about inheriting that form.

If it's in an other project and you don't wand to use a common class
library, that's the way to go.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Herfried K. Wagner [MVP]]

* "One Handed Man [ OHM ]" <te***************************@BTOpenworld.com> scripsit:

If you think about it Cor, using an inherited form makes perfect sense for
some applications. However, I do agree with you that there is a case for
some functionality to allow template forms.

In fact forms inheritance can in some instances be annoying. This can happen
when you want the basic design but need to change some details of the
private members, its more akward really than being able to simply choose a
new form from a tamplate.

That's why some people prefer to declare "private" variables as
'Protected' instead of 'Private'.

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[One Handed Man [ OHM# ]]

Yes, I know how it works. But its a conscious effort to ensure they are
protected. It just can make life a little more complicated. Where sometimes,
you just want to copy the design and not worry about it.

OHM#'
Herfried K. Wagner [MVP] wrote:

* "One Handed Man [ OHM ]"
<te***************************@BTOpenworld.com> scripsit:

If you think about it Cor, using an inherited form makes perfect
sense for some applications. However, I do agree with you that there
is a case for some functionality to allow template forms.

In fact forms inheritance can in some instances be annoying. This
can happen when you want the basic design but need to change some
details of the private members, its more akward really than being
able to simply choose a new form from a tamplate.

That's why some people prefer to declare "private" variables as
'Protected' instead of 'Private'.

Regards - OHM# On**********@BTInternet.com

[Jay B. Harlow [MVP - Outlook]]

Cor,

for another project Is the key word here! The OP never really stated if its the same project or
a different project.

Obviously if its a different project it may be easier just to copy the form
into the second project as you suggest.

However if its the same project then inheritance, most of the time, is the
better method. However in your tab page example, it may be that each tab
page may be its own control, and each distinct form would simply reference a
single extended tab page class...

Hope this helps
Jay

"Cor" <no*@non.com> wrote in message
news:ei**************@TK2MSFTNGP09.phx.gbl... Hi Luke

I have a form that I would like to use, with a few small code and controltext changes, and was wondering if there was any way that I could somehowsave another cop of the form so I can just import it code and all.

I disagree with you and all others who stated it is that inheritance is

the right answer for this.

If it is about a form with 6 panels on it, on some a tabpage on some a
slider, in a docked panel, than a menu on it, a statusbar, a datagrid with
as in the microsoft samples dataaccess on it, that only needs some changes for another project and only needs some slight changes, I would not think
one minute about inheriting that form.

When we are talking about making first a nice base form with nice colors we want to use, a standard statusbar, the fonts etc, I think I agree with you.
Just a thought,

Cor

[Cor]

Hi Jayb B,

For me were the keyword this.

I have a form that I would like to use, with a few small code and control
text changes, and was wondering if there was any way that I could somehow
save another cop of the form so I can just import it code and all.

This you don't ask for a simple form with 5 controls on it.

If it had been:
I have a form, with few code and controls, and I was wondering
if............., we had fully agreed.

But lets make this OT, to much words for somethings were is so few
difference in idea's, we agree that it is not "always" but bassicly the
best approach.

Cor