Splitting to subprojects

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • jb

    #1

    Splitting to subprojects


    Am using the 'Web Application Project' model for an asp.net web app.

    Sections of this now need to be reusable. Is it possible to split into
    sub projects? What happens with /bin directory if so - are there bins in
    each subproject? What happens with sessions?

    Thanks

    JB
  • carion1

    #2
    Re: Splitting to subprojects

    Add a new class library project to your solution and drag the objects
    you want seperated from your current project into the new project.
    Add a reference to the new project and its soup. When the solution is
    compiled it will automagically place a copy of the dll into the bin
    directory of the web project.

    Derek

    On Apr 17, 6:26 am, jb <b...@b.comwrot e:
    Am using the 'Web Application Project' model for an asp.net web app.
    >
    Sections of this now need to be reusable. Is it possible to split into
    sub projects? What happens with /bin directory if so - are there bins in
    each subproject? What happens with sessions?
    >
    Thanks
    >
    JB

    Comment

    • John Saunders [MVP]

      #3
      Re: Splitting to subprojects

      "carion1" <ddavis76@gmail .comwrote in message
      news:1176818591 .770106.84490@o 5g2000hsb.googl egroups.com...
      Add a new class library project to your solution and drag the objects
      you want seperated from your current project into the new project.
      Add a reference to the new project and its soup. When the solution is
      compiled it will automagically place a copy of the dll into the bin
      directory of the web project.
      Don't forget to change the namespace for the types you move, otherwise
      you'll have the same namespace in two assemblies, and you may later get
      confused about which parts belong where.
      --

      John Saunders [MVP]


      Comment

      • jb

        #4
        Re: Splitting to subprojects


        John Saunders [MVP] wrote:
        "carion1" <ddavis76@gmail .comwrote in message
        news:1176818591 .770106.84490@o 5g2000hsb.googl egroups.com...
        >Add a new class library project to your solution and drag the objects
        >you want seperated from your current project into the new project.
        >Add a reference to the new project and its soup. When the solution is
        >compiled it will automagically place a copy of the dll into the bin
        >directory of the web project.
        >
        Don't forget to change the namespace for the types you move, otherwise
        you'll have the same namespace in two assemblies, and you may later get
        confused about which parts belong where.
        I am aware of using class libraries and already do so extensively - also
        custom controls etc.

        I am talking about splitting a site up into reusable parts using the
        'Web Application Project' model; the aspx/ascx pages etc.

        Thanks

        JB

        Comment

        Working...