Code Sharing Question

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • A-PK

    #1

    Code Sharing Question

    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]

    #2
    Re: Code Sharing Question

    A-PK <piercekerk@hot mail.com> wrote:[color=blue]
    > 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.[/color]

    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 - <skeet@pobox.co m>
    Pobox has been discontinued as a separate service, and all existing customers moved to the Fastmail platform.

    If replying to the group, please do not mail me too

    Comment

    • Chris Smith

      #3
      Re: Code Sharing Question

      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]" <skeet@pobox.co m> wrote in message
      news:MPG.1a7064 db3a0c6581989e3 6@msnews.micros oft.com...[color=blue]
      > A-PK <piercekerk@hot mail.com> wrote:[color=green]
      > > Hi, currently I am working on a project with several programmers.
      > >
      > > my problem is how could I separate one project into several small module[/color][/color]
      and[color=blue][color=green]
      > > 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[/color][/color]
      different[color=blue][color=green]
      > > modules. later on, how could I combine two modules into one project.[/color]
      >
      > 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 - <skeet@pobox.co m>
      > http://www.pobox.com/~skeet
      > If replying to the group, please do not mail me too[/color]


      Comment

      • Mike

        #4
        Re: Code Sharing Question

        There is a good example on

        Hours of .Net and Sql Server videos for $20

        Comment

        • A-PK

          #5
          Re: Code Sharing Question

          > But, depending on how large your app is, the project could be split into[color=blue]
          > components.[/color]

          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" <user@email.com > wrote in message
          news:u5n$5$12DH A.3216@TK2MSFTN GP11.phx.gbl...[color=blue]
          > 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[/color]
          you[color=blue]
          > 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[/color]
          used[color=blue]
          > in other apps, just by adding a reference to the assembly.
          >
          > "Jon Skeet [C# MVP]" <skeet@pobox.co m> wrote in message
          > news:MPG.1a7064 db3a0c6581989e3 6@msnews.micros oft.com...[color=green]
          > > A-PK <piercekerk@hot mail.com> wrote:[color=darkred]
          > > > Hi, currently I am working on a project with several programmers.
          > > >
          > > > my problem is how could I separate one project into several small[/color][/color][/color]
          module[color=blue]
          > and[color=green][color=darkred]
          > > > assign to my programmers. after all the coding is done, then just add[/color][/color][/color]
          in[color=blue][color=green][color=darkred]
          > > > 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[/color][/color]
          > different[color=green][color=darkred]
          > > > modules. later on, how could I combine two modules into one project.[/color]
          > >
          > > 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 - <skeet@pobox.co m>
          > > http://www.pobox.com/~skeet
          > > If replying to the group, please do not mail me too[/color]
          >
          >[/color]


          Comment

          Working...