We are planning a greater .NET Application-System (WindowsForms) with
Visual Studio 2005.

One of my problem is, how to design the objects, that they can be
reused.

E.g. I have a form (with derived textboxes) that should be used in
several Projects.

I tried to copy the form to the other project - with no success.
Adding as a linked component didn´t work, too.

Do I have to work with UserControls and dlls? How about updates.

Who has experience in such things.

Thanks for help
aaapaul

On 18/10/2007 in message
<(E-Mail Removed)> aaapaul wrote:

>I tried to copy the form to the other project - with no success.
>Adding as a linked component didn´t work, too.

Either of those approaches *should* work, linking is probably better since
you only have to modify/update the form once.

Is it the main form in each app? If so you should delete the 'Form1' that
VS automatically adds and set your form as the startup form.
--
Jeff Gaines

Thanks Jeff, but I don´t understand your answer.

Let me give you more details.

In VB6 ist was possible to use the same form in several projects:

sample
c:\vb6\p1\
c:\vb6\p2\
c:\vb6\common

I had a frmUni in c:\vb6\common and I could use it in p1 and p2 - I
simple added it to the projects.

Isnt´t this possible in .NET any more?

Outer solutions?

Thanks

"aaapaul" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
We are planning a greater .NET Application-System (WindowsForms) with
Visual Studio 2005.

One of my problem is, how to design the objects, that they can be
reused.

E.g. I have a form (with derived textboxes) that should be used in
several Projects.

I tried to copy the form to the other project - with no success.
Adding as a linked component didn´t work, too.

Do I have to work with UserControls and dlls? How about updates.

Who has experience in such things.

Thanks for help
aaapaul


Are the forms to be reused in projects within the same solution, or are they
in different solutions?
If the projects are in a common solution copying is simple and
semi-automatic (select the <formname>.vb to copy and the support files are
automatically copied as well), and adding a link to another project is also
straight forward (right-click on project in solution explorer->Add
reference...).
If you have separate solutions that's a different matter.

Thanks.

The problem appears only when I am using a derived control on the box.

I have a solution with
project 1
and
project 2

In project1 there is a form1 that I want to use in project2

So I added in project2 a reference to form1 from project1.

This works.

But when I place a derived textbox (ltext1) on form1.

The error "project1.ltext1 is not defined" appears.

Any idea?

Thanks.

If you're serious about it, then I'd recommend
http://www.amazon.com/Developing-App...ion/1590592883

He gives you a good understanding of what you're actually doing and provides
some code.
Most is germane to 1.1, but the concepts apply to whatever version/language
you use.


Read the reviews on the amazon site.





"aaapaul" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
We are planning a greater .NET Application-System (WindowsForms) with
Visual Studio 2005.

One of my problem is, how to design the objects, that they can be
reused.

E.g. I have a form (with derived textboxes) that should be used in
several Projects.

I tried to copy the form to the other project - with no success.
Adding as a linked component didn´t work, too.

Do I have to work with UserControls and dlls? How about updates.

Who has experience in such things.

Thanks for help
aaapaul

"aaapaul" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks.
>
> The problem appears only when I am using a derived control on the box.
>
> I have a solution with
> project 1
> and
> project 2
>
> In project1 there is a form1 that I want to use in project2
>
> So I added in project2 a reference to form1 from project1.
>
> This works.
>
> But when I place a derived textbox (ltext1) on form1.
>
> The error "project1.ltext1 is not defined" appears.
>
> Any idea?
>
> Thanks.
>

Where, exactly, is your subclass of TextBox? In project1, perhaps?
What happens if you add a reference to your subclass to project 2?

The Subclass of the Textbox is in Project1 as a reference of Project3
(ltext.vb).

I added the Reference (ltext.vb) to Project2 too, with no success.

Error in Project2: Project1.LText is not defined.

Thanks.

See, if you are using the same form in two different projects this may work
- take project2
- add a reference to project1
- add a class in project2 that inherits from project1.form1

this will make the reuse of the entire code you have in project1.form1
possible

regards
Sujith



"sloan" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> If you're serious about it, then I'd recommend
> http://www.amazon.com/Developing-App...ion/1590592883
>
> He gives you a good understanding of what you're actually doing and
> provides some code.
> Most is germane to 1.1, but the concepts apply to whatever
> version/language you use.
>
>
> Read the reviews on the amazon site.
>
>
>
>
>
> "aaapaul" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> We are planning a greater .NET Application-System (WindowsForms) with
> Visual Studio 2005.
>
> One of my problem is, how to design the objects, that they can be
> reused.
>
> E.g. I have a form (with derived textboxes) that should be used in
> several Projects.
>
> I tried to copy the form to the other project - with no success.
> Adding as a linked component didn´t work, too.
>
> Do I have to work with UserControls and dlls? How about updates.
>
> Who has experience in such things.
>
> Thanks for help
> aaapaul
>
>

Thanks Sujith!

I did it like you described it.

I have now project1 and project2 in one solution.
I added in project2 a reference to application1 and I said

Dim x As New Project1.Form1()
x.ShowDialog()

This works.

But now I have 2 exe and cant start one exe without the other.

I only wanted to complie the form1 of Project1 in Project 2.

Its seems, thats this behavior is not so good like in VB6