B
BK
We've got a fairly large scale development process under way in .NET
2003. We are about a month away from go-live for phase 1, second phase
is rather short and all work should be completed in the next 2 months.
Looking back on problems encountered, we want to learn from this
project. FWIW, we are nearly on time with the original time line (only
off by about a month), and we actually added more functionality than
the original specs called for.
In this application, we have several projects we created for simple,
reusable functionality (such as a dll that handles BLOB attachements, a
dll to handle user preferences, a dll to handle system messaging, etc.)
These projects are a mixture of VB and C#, with the output for all
being a dll that the application's exe calls. It has worked really
well for us and we expect that most of these dll's will be reused in
upcoming projects.
That being said, we did have some problems. We did this project mostly
with 2 developers. We did the project WITHOUT a source control program
(that was interesting) because management hasn't bouught in to source
control yet. (That has finally changed and we are testing SourceSafe).
The dlls were included in the main project as dll's rather than as a
project. I did this because I wanted to keep the solution pared down
but I'm not sure that was the best way to do it. Any thoughts? Any
comments on referencing a dll vs referencing a project in the solution?
Going forward we plan to use source control. We are testing Visual
SourceSafe, anyone want to add their 2 cents either for or against
this? Any suggestions on other products we may want to consider? We
will be converting to .NET 2005 soon, but the cost of Team Edition and
a dedicated Team Foundation Server is too pricey. It was suggested we
look at CVS and/or Subversion. I'm a little familiar with CVS and
wasn't that impressed with it. Anyone with experience with either of
them?
Sorry for the length of the post, but I wanted to provide as much
information as possible and I hope to start a healthy dialog with
anyone interested in sharing their experiences.
Thanks,
Will I Am
2003. We are about a month away from go-live for phase 1, second phase
is rather short and all work should be completed in the next 2 months.
Looking back on problems encountered, we want to learn from this
project. FWIW, we are nearly on time with the original time line (only
off by about a month), and we actually added more functionality than
the original specs called for.
In this application, we have several projects we created for simple,
reusable functionality (such as a dll that handles BLOB attachements, a
dll to handle user preferences, a dll to handle system messaging, etc.)
These projects are a mixture of VB and C#, with the output for all
being a dll that the application's exe calls. It has worked really
well for us and we expect that most of these dll's will be reused in
upcoming projects.
That being said, we did have some problems. We did this project mostly
with 2 developers. We did the project WITHOUT a source control program
(that was interesting) because management hasn't bouught in to source
control yet. (That has finally changed and we are testing SourceSafe).
The dlls were included in the main project as dll's rather than as a
project. I did this because I wanted to keep the solution pared down
but I'm not sure that was the best way to do it. Any thoughts? Any
comments on referencing a dll vs referencing a project in the solution?
Going forward we plan to use source control. We are testing Visual
SourceSafe, anyone want to add their 2 cents either for or against
this? Any suggestions on other products we may want to consider? We
will be converting to .NET 2005 soon, but the cost of Team Edition and
a dedicated Team Foundation Server is too pricey. It was suggested we
look at CVS and/or Subversion. I'm a little familiar with CVS and
wasn't that impressed with it. Anyone with experience with either of
them?
Sorry for the length of the post, but I wanted to provide as much
information as possible and I hope to start a healthy dialog with
anyone interested in sharing their experiences.
Thanks,
Will I Am