[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 154
  • Last Modified:

Multiple Developers working on one ASP.Net project, insulation suggestions

We have multiple developers working on one asp.net project here at our place. It's starting to get old though, trying to compile only to stare at errors raised from another page that's in the process of being written by someone else.

Do you all have any suggestions as to how we can insulate each other from works in progress? I'm guessing we would want to create multiple projects within a single solution, is there a one process that's recommended over another? Any words of advice?

Thanks for your help,

bd
0
brooklynDev
Asked:
brooklynDev
  • 4
  • 3
  • 2
1 Solution
 
raterusCommented:
You should be using SourceSafe or some other version control system to manage your development.  It's like a library, you check out a file when you modify it, and when you are done, you check it back in.  No two developers should work on a file at the same time, the system will notify you if you are.
0
 
brooklynDevAuthor Commented:
SourceSafe is a hassle though, I'd rather avoid it and do regular backups. If an open file is updated outside of the IDE visual studio let's you know anyway.

What I want to avoid is attempting to compile my classes and receiving errors because another class another developer is working on is a work in progress.
0
 
raterusCommented:
So, you want to avoid syntax errors they may currently have in their code?  I don't really know what to tell you other than to grin and bear it with sourcesafe, it's meant for these sort of things.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
brooklynDevAuthor Commented:
What I'd like to do is compile a part of the app, insulated from the rest of the app, that way when I debug/test my source while not asking the IDE to compile other parts of the app other devs are working on.
0
 
raterusCommented:
As far as I know, there is no way to tell VS to compile only certain pieces of a project, without removing the resource from the project before compiling.  The only way I can imagine what you want to work, without sourcesafe, is for each developer to compile their work, and only their work into .dll.  The developer would put their most recent working version in a directory your project links to, importing their .dll as a reference.  Since you'd always be using a "working" build, you shouldn't run into problems, unless they put up a version which was really broke.
0
 
vladimir_kalashnikovCommented:
just wait for vs 2005, and asp.net 2.0 where you can compile and build on a page by page basis. :)

(i know this is no help)
0
 
brooklynDevAuthor Commented:
Microsoft has a lengthy article on exactly this topic, which can be found here:

http://www.microsoft.com/downloads/details.aspx?familyid=94fdb8c8-5a87-4545-af75-6053f32c7eca&displaylang=en

although vlad is right, vs 2005 will make things a lot easier, I hope they actually release it in 2005.

bd
0
 
vladimir_kalashnikovCommented:
i have been to one of microsoft's 'deep dives' that was about vs 2005 and asp.net 2.0 and was shown how it works, also, it is in the beta, so i would hope that it makes it into the final product.
0
 
raterusCommented:
I don't think a 50/50 split would be appropriate here.  vladimir has suggested future fixes, but as he mentioned himself, they will offer no help right now to the author!
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now