about developing a group c# application

[KelvinWongYW]

Dear All

my company is going to re-develop the system with C# and this team
have 3 people

and each person are going to develop each function with its own
winform

and finally there are a main winform that contain a menu button to
access those functons

my question is how can i integrate these winforms together with the
main program

i have think of combine all the codes into the main program but it is
time consuming and much error will occur

the second one is that generate a dll and then import them to the main
program so that it can call the winform directly from the dll. but i
dont know whether it is feasible. i still having some research on that

i would like to ask any developer that have experiece to develop a
group c# application to give me some suggestion.

thanks very much

 

[Guest]

It's fairly common to have a setup as you describe. You will want a single
VS solution that contains four projects within it (3 dlls, 1 main app). Do
you have a revision control system to manage this? VS ties in nicely with
visual source safe and other revision control systems, so that each developer
has access to the other codes being developed.

 

[KelvinWongYW]

It's fairly common to have a setup as you describe. You will want a single
VS solution that contains four projects within it (3 dlls, 1 main app). Do
you have a revision control system to manage this? VS ties in nicely with
visual source safe and other revision control systems, so that each developer
has access to the other codes being developed.













- -

Thanks for the advise
but there is no source safe
so as u said, i can call a winform direct from the dll?
i mean that in the main app, i just need to call a function in order
to call the winform
is there any syntax or website for that

thanks

 

[KelvinWongYW]

Thanks for the advise
but there is no source safe
so as u said, i can call a winform direct from the dll?
i mean that in the main app, i just need to call a function in order
to call the winform
is there any syntax or website for that

thanks- -

- -

Or maybe any book that is suitable for study for group porgramming for
c#

 

[Guest]

This looks like a good reference to get you started:
http://msdn2.microsoft.com/en-us/library/ms998208.aspx

As to how your main will open the form in another dll, I presume your dlls
will have distinct namespaces. DLL1 may use namespace DLL1, so a form in it
name formEditObjectOne would be created with the full name
DLL1.formEditObjectOne after adding a reference to the external dll.

 

[KelvinWongYW]

This looks like a good reference to get you started:http://msdn2.microsoft.com/en-us/library/ms998208.aspx

As to how your main will open the form in another dll, I presume your dlls
will have distinct namespaces. DLL1 may use namespace DLL1, so a form in it
name formEditObjectOne would be created with the full name
DLL1.formEditObjectOne after adding a reference to the external dll.






- -

thanks you for your helpful idea
i will try and read the article

thanks

 

[KelvinWongYW]

thanks you for your helpful idea
i will try and read the article

thanks- -

- -

i have try on building the c# library with winform and call it in the
main app
and it is really work
but while i develop in the c# library, i want not debug directly as it
need me to have a execute project
is that is need to create a execute project to run it or have any
convinent way to test it
And i cant create the project as window application as there are no
dll create after i built it

thanks

 

[Guest]

If I understand your question, all four developers should be debugging the
same solution with four projects. The executable is marked as the startup
project and they debug their dll by running the main application. A drawback
to this is that all four people will identify problems with the main
application. You will need to make the developers resist the temptation to
change code outside of their project. This is why I recommended a revision
control system. It would manage each of the four developers making changes
to any of the four projects.

 

[KelvinWongYW]

If I understand your question, all four developers should be debugging the
same solution with four projects. The executable is marked as the startup
project and they debug their dll by running the main application. A drawback
to this is that all four people will identify problems with the main
application. You will need to make the developers resist the temptation to
change code outside of their project. This is why I recommended a revision
control system. It would manage each of the four developers making changes
to any of the four projects.







- -

i would like to ask but it is a silly question
is there any free revision control system there?

 

[Jon Skeet [C# MVP]]

i would like to ask but it is a silly question
is there any free revision control system there?

Yes - Subversion is free and (IMO) wonderful:

http://svn.tigris.org