-
Jun 21st, 2012, 10:50 PM
#1
Thread Starter
Fanatic Member
"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
-
Jul 10th, 2012, 04:57 AM
#2
Fanatic Member
Re: "Resource Sharing" Architecture
Originally Posted by erickwidya
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/
-
Jul 10th, 2012, 05:07 AM
#3
Thread Starter
Fanatic Member
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
-
Jul 10th, 2012, 05:49 AM
#4
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.
.
-
Jul 12th, 2012, 01:48 AM
#5
Thread Starter
Fanatic Member
Re: "Resource Sharing" Architecture
thx honeybee for the response
i will keep this in mind..
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|