Question about source control

[ºa¤Ö]

We are developing ASP.NET web application and using Visual source safe (VSS)
to control our source code
We developed a user control and it will been used by different project.

I know there have a function like sharing in VSS, which means you can link
the file in different project and once you updated that file in either
project, that file in other projects, which used that file, will been
updated automatically, too.

On the other hand, we can depoly the user control in DLL format and placed
in a centralized folder, then reference to that folder to use that user
control. If there have any update on the user control, we can just focus on
the source and re-deploy it in DLL after updated. However, VSS like also
have same function...

My question is, which way will be better? deploy the user control in DLL
format or use VSS to control the source code? It sees if we are using VSS to
control the source code, then deploy the user control in DLL format is
useless, right? I am very confused on it.

Assumed the user control is used internally and will not release to 3rd
party.

Thanks

 

[Andrew Faust]

Personally I prefer to use Dlls for code that is shared amongst multiple
projects. This way you can minimize breaks in the build based on changes to
the shared code. Should someone be working on some major overhauls, you can
work on your section while referencing the existing libraries and update to
the new stuff when they are done.

I'd also recommend you switch to another source control system than VSS. I
started looking at other systems as soon as I read Microsoft's VSS Best
Practices
(http://msdn2.microsoft.com/en-us/library/bb509342(vs.80).aspx#vssbest_general)
In it they recommend running processes weekly to detect and correct
problems with the database structure. If Microsoft says you need to check
that often, it's probably not a system you should trust your code to.

 

[??]

Hi Andrew,

But if someone, who update the user control, haven't checkin the file to the
VSS, it will not affect other developers until they download that files from
the VSS because they are still using existing files (local copy) to work on
their section

Right?

So any other comment, I also prefer to use Dlls, but when compare with VSS,
I cannot find a strong reason to support me to convert the user control in
DLL...

Thanks

Personally I prefer to use Dlls for code that is shared amongst multiple
projects. This way you can minimize breaks in the build based on changes
to the shared code. Should someone be working on some major overhauls, you
can work on your section while referencing the existing libraries and
update to the new stuff when they are done.

I'd also recommend you switch to another source control system than VSS. I
started looking at other systems as soon as I read Microsoft's VSS Best
Practices
(http://msdn2.microsoft.com/en-us/library/bb509342(vs.80).aspx#vssbest_general)
In it they recommend running processes weekly to detect and correct
problems with the database structure. If Microsoft says you need to check
that often, it's probably not a system you should trust your code to.

--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com

Weare developing ASP.NET web application and using Visual source safe
(VSS) to control our source code
We developed a user control and it will been used by different project.

I know there have a function like sharing in VSS, which means you can
link the file in different project and once you updated that file in
either project, that file in other projects, which used that file, will
been updated automatically, too.

On the other hand, we can depoly the user control in DLL format and
placed in a centralized folder, then reference to that folder to use that
user control. If there have any update on the user control, we can just
focus on the source and re-deploy it in DLL after updated. However, VSS
like also have same function...

My question is, which way will be better? deploy the user control in DLL
format or use VSS to control the source code? It sees if we are using VSS
to control the source code, then deploy the user control in DLL format is
useless, right? I am very confused on it.

Assumed the user control is used internally and will not release to 3rd
party.

Thanks

 

[Andrew Faust]

That's true. However, if you are going to keep files checked out for long
periods of time you negate a lot of the benefits (roll backs, backup
copies, etc) of source control.

However, if you really don't want to split them off to separate dlls and
instead want to share the files here's a page describing how to do it.
http://support.microsoft.com/kb/132922

--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com

Hi Andrew,

But if someone, who update the user control, haven't checkin the file to
the VSS, it will not affect other developers until they download that
files from the VSS because they are still using existing files (local
copy) to work on their section

Right?

So any other comment, I also prefer to use Dlls, but when compare with
VSS, I cannot find a strong reason to support me to convert the user
control in DLL...

Thanks

Personally I prefer to use Dlls for code that is shared amongst multiple
projects. This way you can minimize breaks in the build based on changes
to the shared code. Should someone be working on some major overhauls,
you can work on your section while referencing the existing libraries
and update to the new stuff when they are done.

I'd also recommend you switch to another source control system than VSS.
I started looking at other systems as soon as I read Microsoft's VSS
Best Practices
(http://msdn2.microsoft.com/en-us/library/bb509342(vs.80).aspx#vssbest_general)
In it they recommend running processes weekly to detect and correct
problems with the database structure. If Microsoft says you need to
check that often, it's probably not a system you should trust your code
to.

--
Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com

Weare developing ASP.NET web application and using Visual source safe
(VSS) to control our source code
We developed a user control and it will been used by different project.

I know there have a function like sharing in VSS, which means you can
link the file in different project and once you updated that file in
either project, that file in other projects, which used that file, will
been updated automatically, too.

On the other hand, we can depoly the user control in DLL format and
placed in a centralized folder, then reference to that folder to use
that user control. If there have any update on the user control, we can
just focus on the source and re-deploy it in DLL after updated.
However, VSS like also have same function...

My question is, which way will be better? deploy the user control in
DLL format or use VSS to control the source code? It sees if we are
using VSS to control the source code, then deploy the user control in
DLL format is useless, right? I am very confused on it.

Assumed the user control is used internally and will not release to 3rd
party.

Thanks