Results 1 to 5 of 5

Thread: "Resource Sharing" Architecture

  1. #1

    Thread Starter
    Fanatic Member
    Join Date
    Sep 2004
    Location
    Jakarta, Indonesia
    Posts
    818

    "Resource Sharing" Architecture

    hi all, need some suggestions

    right now when i try to build some program i used .dll that contains global method that being used in whole application, when it need to change than i just need to rebuild the .dll then rebuild the program that used that .dll

    it got no problem at all because i'm a single fighter

    but this situation doesn't work well when i involved into Developer Team
    when "sharing resource" change, it need to be redeploy

    my first thought are using Web Service to do simillar

    any insight how to resolve something like this?

    thx,
    erick

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL,
    Kill Database Processes

  2. #2
    Fanatic Member x-ice's Avatar
    Join Date
    Mar 2004
    Location
    UK
    Posts
    671

    Re: "Resource Sharing" Architecture

    Quote Originally Posted by erickwidya View Post
    hi all, need some suggestions

    right now when i try to build some program i used .dll that contains global method that being used in whole application, when it need to change than i just need to rebuild the .dll then rebuild the program that used that .dll

    it got no problem at all because i'm a single fighter

    but this situation doesn't work well when i involved into Developer Team
    when "sharing resource" change, it need to be redeploy

    my first thought are using Web Service to do simillar

    any insight how to resolve something like this?

    thx,
    erick
    I think a combination of version control and continuous integration will allow you to achieve what you're after.

    Here are some recommendations:

    Version control: http://tortoisesvn.net/
    Continuous Integration (build server): http://www.jetbrains.com/teamcity/

  3. #3

    Thread Starter
    Fanatic Member
    Join Date
    Sep 2004
    Location
    Jakarta, Indonesia
    Posts
    818

    Re: "Resource Sharing" Architecture

    thx x-ice for the info

    i believe Turtoise and Team City are meant for phase "when the application were build" before it distributed

    what i mean is after the application distributed, when the dependency/reference or some echancment changes, i don't need to rebuild the application

    the application just "use" the newly references without question

    hope u understand what i mean

    thx,
    erick

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL,
    Kill Database Processes

  4. #4
    Randalf the Red honeybee's Avatar
    Join Date
    Jun 2000
    Location
    off others' brains
    Posts
    4,345

    Re: "Resource Sharing" Architecture

    erickwidya, if you are creating a strongly named assembly, what you aim is not possible, because a strongly named assembly will include the version number. However if it's a normal assembly which is not strongly named, what you want to achieve should not be a problem.

    .
    I am not a complete idiot. Some parts are still missing.
    Check out the rtf-help tutorial
    General VB Faq Thread
    Change is the only constant thing. I have not changed my signature in a long while and now it has started to stink!
    Get more power for your floppy disks. ; View honeybee's Elite Club:
    Use meaningfull thread titles. And add "[Resolved]" in the thread title when you have got a satisfactory response.
    And if that response was mine, please think about giving me a rep. I like to collect them!

  5. #5

    Thread Starter
    Fanatic Member
    Join Date
    Sep 2004
    Location
    Jakarta, Indonesia
    Posts
    818

    Re: "Resource Sharing" Architecture

    thx honeybee for the response

    i will keep this in mind..

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL,
    Kill Database Processes

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width