Code Sharing Question

[A-PK]

Hi, currently I am working on a project with several programmers.

my problem is how could I separate one project into several small module and
assign to my programmers. after all the coding is done, then just add in
those modules, and combine all modules into one conplete project

Let's say the project is "sales order application".
how could I separate this project into two modules
1 module - with the feature of add/edit/delete sales order

2 module - with the feature of view and analsys the sales.

so now I create one project named Sales Application.
how could I assign my two programmers writing on this project with different
modules. later on, how could I combine two modules into one project.

pls guide me. or perhaps can provide useful link or reference site for me.
thank you

[Jon Skeet [C# MVP]]

A-PK <pi********@hotmail.com> wrote:

Hi, currently I am working on a project with several programmers.

my problem is how could I separate one project into several small module and
assign to my programmers. after all the coding is done, then just add in
those modules, and combine all modules into one conplete project

Let's say the project is "sales order application".
how could I separate this project into two modules
1 module - with the feature of add/edit/delete sales order

2 module - with the feature of view and analsys the sales.

so now I create one project named Sales Application.
how could I assign my two programmers writing on this project with different
modules. later on, how could I combine two modules into one project.

Any reason they can't just both work on the same project at the same
time without separating it into modules? If each of them knows what
they should be working on, I can't see why it should be a problem.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Chris Smith]

I agree with Jon on this. each developer would work on a separate class in
the project. They could even work on the same class at the same time if you
don't allow them to edit the same functions/methods at the same time. (To
much manual merging for me)

But, depending on how large your app is, the project could be split into
components.

Project 1 a order components that can save and open an order
Project 2 a winform/webform app that can view and edit the order.

Also think about code reuse. If you had an order component, it could be used
in other apps, just by adding a reference to the assembly.

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

A-PK <pi********@hotmail.com> wrote:

Hi, currently I am working on a project with several programmers.

my problem is how could I separate one project into several small module and assign to my programmers. after all the coding is done, then just add in
those modules, and combine all modules into one conplete project

Let's say the project is "sales order application".
how could I separate this project into two modules
1 module - with the feature of add/edit/delete sales order

2 module - with the feature of view and analsys the sales.

so now I create one project named Sales Application.
how could I assign my two programmers writing on this project with different modules. later on, how could I combine two modules into one project.

Any reason they can't just both work on the same project at the same
time without separating it into modules? If each of them knows what
they should be working on, I can't see why it should be a problem.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Mike]

There is a good example on
www.TechnicalVideos.net
Hours of .Net and Sql Server videos for $20

[A-PK]

> But, depending on how large your app is, the project could be split into

components.
Hi, Chirs you mention about split into components. Could you mind sharing a
bit this idea to me a bit.
actually i am new to VS. or pls guide me where I am get any reference on
that.

if anyone else also knew, pls info me

thank a lot

"Chris Smith" <us**@email.com> wrote in message
news:u5**************@TK2MSFTNGP11.phx.gbl... I agree with Jon on this. each developer would work on a separate class in
the project. They could even work on the same class at the same time if you don't allow them to edit the same functions/methods at the same time. (To
much manual merging for me)

But, depending on how large your app is, the project could be split into
components.

Project 1 a order components that can save and open an order
Project 2 a winform/webform app that can view and edit the order.

Also think about code reuse. If you had an order component, it could be used in other apps, just by adding a reference to the assembly.

"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...

A-PK <pi********@hotmail.com> wrote:

Hi, currently I am working on a project with several programmers.

my problem is how could I separate one project into several small module

and

assign to my programmers. after all the coding is done, then just add

in those modules, and combine all modules into one conplete project

Let's say the project is "sales order application".
how could I separate this project into two modules
1 module - with the feature of add/edit/delete sales order

2 module - with the feature of view and analsys the sales.

so now I create one project named Sales Application.
how could I assign my two programmers writing on this project with

different modules. later on, how could I combine two modules into one project.

Any reason they can't just both work on the same project at the same
time without separating it into modules? If each of them knows what
they should be working on, I can't see why it should be a problem.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too