B
Brian Patrick
Our company is making the switch from ASP to ASP.net, but we've noticed a
significant problem.
With ASP, developers could check out individual pages, make changes and
check those pages back in without affecting other developers.
With ASP.net, developers can check out individual pages, but if they need to
change the "code behind", this requires the 1 project dll to be re-compiled.
So for example, developer #1 changes the code behind of page 1, and
recompiles the project. Now, developer #2, changes the code behind of page
2, and recompiles the project. As you can see, the changes that developer
#1 has made are now lost.
There must be a proper way to do have multi-developer developement with an
ASP.net project. Does anyone have any insight to this problem?
Thanks!
significant problem.
With ASP, developers could check out individual pages, make changes and
check those pages back in without affecting other developers.
With ASP.net, developers can check out individual pages, but if they need to
change the "code behind", this requires the 1 project dll to be re-compiled.
So for example, developer #1 changes the code behind of page 1, and
recompiles the project. Now, developer #2, changes the code behind of page
2, and recompiles the project. As you can see, the changes that developer
#1 has made are now lost.
There must be a proper way to do have multi-developer developement with an
ASP.net project. Does anyone have any insight to this problem?
Thanks!