about developing c# application

[KelvinWongYW]

Hi All,

my company have plan to re-develop the orginal system and my team have
3 people

so we will develop each function seperately with its own winform

but i would like to know how to integrate the function at the last
step with main program that contain a menu

here i have few suggestion on that:

1. combine all the winforms together in the main program but i think
it would quite time consuming and increase error rate.

2. for each winform function, build an dll and then call it at the
main program, but it is only a imagination. because i dont know wether
i can call the winform out directly using dll.

Anyway, If there are developers that have experience on develop it ,
please give me some sugestion.

i will keep on surfing for solution

thanks

 

[Andrew Faust]

Use a source control system. There are tons of them such as subversion,
cvs, source safe, team foundation server and dozens if not hundreds more.
They all have advantages and disadvantages, however, a quick googling will
get you a good comparison of the most popular ones.

In a nutshell, a source control system will provide a central database to
store the project. This database will contain the master copy of the
project. Your three developers will check out a local copy of the project
to their own machines. On a periodic basis they can check in their changes
to the repository. The other 2 developers can easily update their local
copy from the central repository to get the 3rd developer's additions. This
keeps everyone up to date pretty effortlessly. However, other than just
allowing easy code sharing it has some other features that make it crucial
to any developer. Even if it's just a single developer working on a small
project.

A typical source control system will track every single update to the
source. It will then let you view or roll back to previous versions. If you
start working down one path and then 3 days later decide it was a mistake,
you can easily tell the system to revert the project back to what it was
like 3 days ago.

 

[Guest]

Andrew,

Your reply is very good, but...

The poster had put the same post up a few days ago, and that was my
suggestion. They do not have any revision control system. I suggested short
of that, then the group is left with sharing dlls to be integrated, or each
having a copy of a solution with four projects. I don't know why he reposted
the original, but per his last post on the original thread, he was confused

Use a source control system. There are tons of them such as subversion,
cvs, source safe, team foundation server and dozens if not hundreds more.
They all have advantages and disadvantages, however, a quick googling will
get you a good comparison of the most popular ones.

In a nutshell, a source control system will provide a central database to
store the project. This database will contain the master copy of the
project. Your three developers will check out a local copy of the project
to their own machines. On a periodic basis they can check in their changes
to the repository. The other 2 developers can easily update their local
copy from the central repository to get the 3rd developer's additions. This
keeps everyone up to date pretty effortlessly. However, other than just
allowing easy code sharing it has some other features that make it crucial
to any developer. Even if it's just a single developer working on a small
project.

A typical source control system will track every single update to the
source. It will then let you view or roll back to previous versions. If you
start working down one path and then 3 days later decide it was a mistake,
you can easily tell the system to revert the project back to what it was
like 3 days ago.



--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com

Hi All,

my company have plan to re-develop the orginal system and my team have
3 people

so we will develop each function seperately with its own winform

but i would like to know how to integrate the function at the last
step with main program that contain a menu

here i have few suggestion on that:

1. combine all the winforms together in the main program but i think
it would quite time consuming and increase error rate.

2. for each winform function, build an dll and then call it at the
main program, but it is only a imagination. because i dont know wether
i can call the winform out directly using dll.

Anyway, If there are developers that have experience on develop it ,
please give me some sugestion.

i will keep on surfing for solution

thanks

 

[Andrew Faust]

That's frustrating. Maybe with multiple people telling him the same thing,
he'll start to realize that he's actually being given good advice.

--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com

Andrew,

Your reply is very good, but...

The poster had put the same post up a few days ago, and that was my
suggestion. They do not have any revision control system. I suggested
short
of that, then the group is left with sharing dlls to be integrated, or
each
having a copy of a solution with four projects. I don't know why he
reposted
the original, but per his last post on the original thread, he was
confused

Use a source control system. There are tons of them such as subversion,
cvs, source safe, team foundation server and dozens if not hundreds
more.
They all have advantages and disadvantages, however, a quick googling
will
get you a good comparison of the most popular ones.

In a nutshell, a source control system will provide a central database
to
store the project. This database will contain the master copy of the
project. Your three developers will check out a local copy of the
project
to their own machines. On a periodic basis they can check in their
changes
to the repository. The other 2 developers can easily update their local
copy from the central repository to get the 3rd developer's additions.
This
keeps everyone up to date pretty effortlessly. However, other than just
allowing easy code sharing it has some other features that make it
crucial
to any developer. Even if it's just a single developer working on a
small
project.

A typical source control system will track every single update to the
source. It will then let you view or roll back to previous versions. If
you
start working down one path and then 3 days later decide it was a
mistake,
you can easily tell the system to revert the project back to what it was
like 3 days ago.



--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com

Hi All,

my company have plan to re-develop the orginal system and my team have
3 people

so we will develop each function seperately with its own winform

but i would like to know how to integrate the function at the last
step with main program that contain a menu

here i have few suggestion on that:

1. combine all the winforms together in the main program but i think
it would quite time consuming and increase error rate.

2. for each winform function, build an dll and then call it at the
main program, but it is only a imagination. because i dont know wether
i can call the winform out directly using dll.

Anyway, If there are developers that have experience on develop it ,
please give me some sugestion.

i will keep on surfing for solution

thanks

 

[Lew]

That's frustrating. Maybe with multiple people telling him the same
thing, he'll start to realize that he's actually being given good advice.

"They do not have any revision control system" is easily curable, and
therefore no excuse. Virtually any other way to handle the situation will fail.

 

[Andrew Faust]

"They do not have any revision control system" is easily curable, and

therefore no excuse. Virtually any other way to handle the situation
will fail.

In his case where he had previously been told about version control, I
agree. However, I've talked to developers (usually independent developers)
who legitimately didn't know such a thing exists. Then when you teach them
about it they tend to consider it more trouble than it's worth, until they
have a catastrophic loss.