|
 |
aspx thread: Visual SourceSafe.
Message #1 by "Mats Boberg" <mats.boberg@n...> on Fri, 24 Aug 2001 16:09:21 +0200
|
|
Hi,
We are trying to manage our .Net projects with Visual SourceSafe, but have
not quite figured out how to make it work with web projects. There seems to
be a conflict between the Frontpage Server Extensions and the version
control of VSS. Is there an easy solution to this problem, or do we need to
keep the projects separate (web projects managed by Frontpage Server
Extensions and class libraries in VSS)?
Best regards
Mats
Message #2 by Tim Heuer <TimH@i...> on Fri, 24 Aug 2001 08:33:22 -0700
|
|
Mats,
We too have had significant issues with the VSS integration with the web
projects. After talking with some at Microsoft, they suggested not using
FPSE access and using the file share access (that didn't work too well with
us). As far as some lessons learned in our current project (all these are
regarding using the integration within the IDE):
(1) VSS didn't work too well with team development re: web projects (main
project kept getting checked out by all users, even when VSS said nobody had
it checked out)
(2) licenses.licx file - if your developers actually use the "Design" mode
for the webforms, this file will haunt you...whenever the Designer mode in
webforms are used, this file needs modification and gets automatically
checked out by the author...but generally the author doesn't know it, so
when another person uses the designer, they can't modify anything, because
the file needs to be checked in...our workaround: don't use designer
(3) Checking our only the source files - bad idea...if needing to modify
only the source, check out the entire file (.aspx, .aspx.cs, .aspx.resx) -
it will make your life easier
(4) .resx files - these are for webforms and shouldn't be deleted...will
reak havoc
(5) Team Development in general: We had problems in a dev team of 6 working
on the same web project...when I "built" the application it would break
other peoples code. What we did was instruct all developers to use the
"src" attribute on their pages, and additionally debug locally, by attaching
to their own process and *not* the web server to not cause anyone else lock
ups.
We don't feel it's ready for primetime yet, but trust the folks at MS are
figuring out all the oddities.
Make sure you are using the VSS6c that VS.NET came with also.
Tim
-----Original Message-----
From: Mats Boberg [mailto:mats.boberg@n...]
Sent: Friday, August 24, 2001 7:09 AM
To: ASP+
Subject: [aspx] Visual SourceSafe.
Hi,
We are trying to manage our .Net projects with Visual SourceSafe, but have
not quite figured out how to make it work with web projects. There seems to
be a conflict between the Frontpage Server Extensions and the version
control of VSS. Is there an easy solution to this problem, or do we need to
keep the projects separate (web projects managed by Frontpage Server
Extensions and class libraries in VSS)?
Best regards
Mats
Message #3 by "Al LeMay" <alemay@d...> on Fri, 24 Aug 2001 08:59:58 -0700
|
|
To chime in here...
VSS integration is very "buggy" at best in .Net. We have a large
project in progress, and have decided to leave VSS for another product.
As noted FPSE is the actual best way to manage the project. It is
tricky, but it works. We leave the files checked out in VSS on the web
server. (Exclusive check outs only in VSS.) Then you just open the
project through the FPSE. The .SLN file is also checked into VSS, but
it is checked out locally in the Visual Studio Projects folder on the
developers system. As I say... it seems to work well, but may not be
the best way to go about it.
Switch to a better SCM tool and you will be happier, much.
Al LeMay
Virtuoso
Quality Assurance Manager
alemay@d...
http://www.virtuoso.com/
-----Original Message-----
From: Tim Heuer [mailto:TimH@i...]
Sent: Friday, August 24, 2001 8:33 AM
To: ASP+
Subject: [aspx] RE: Visual SourceSafe.
Mats,
We too have had significant issues with the VSS integration with the web
projects. After talking with some at Microsoft, they suggested not
using FPSE access and using the file share access (that didn't work too
well with us). As far as some lessons learned in our current project
(all these are regarding using the integration within the IDE):
(1) VSS didn't work too well with team development re: web projects
(main project kept getting checked out by all users, even when VSS said
nobody had it checked out)
(2) licenses.licx file - if your developers actually use the "Design"
mode for the webforms, this file will haunt you...whenever the Designer
mode in webforms are used, this file needs modification and gets
automatically checked out by the author...but generally the author
doesn't know it, so when another person uses the designer, they can't
modify anything, because the file needs to be checked in...our
workaround: don't use designer
(3) Checking our only the source files - bad idea...if needing to modify
only the source, check out the entire file (.aspx, .aspx.cs, .aspx.resx)
- it will make your life easier
(4) .resx files - these are for webforms and shouldn't be deleted...will
reak havoc
(5) Team Development in general: We had problems in a dev team of 6
working on the same web project...when I "built" the application it
would break other peoples code. What we did was instruct all developers
to use the "src" attribute on their pages, and additionally debug
locally, by attaching to their own process and *not* the web server to
not cause anyone else lock ups.
We don't feel it's ready for primetime yet, but trust the folks at MS
are figuring out all the oddities.
Make sure you are using the VSS6c that VS.NET came with also.
Tim
-----Original Message-----
From: Mats Boberg [mailto:mats.boberg@n...]
Sent: Friday, August 24, 2001 7:09 AM
To: ASP+
Subject: [aspx] Visual SourceSafe.
Hi,
We are trying to manage our .Net projects with Visual SourceSafe, but
have not quite figured out how to make it work with web projects. There
seems to be a conflict between the Frontpage Server Extensions and the
version control of VSS. Is there an easy solution to this problem, or do
we need to keep the projects separate (web projects managed by Frontpage
Server Extensions and class libraries in VSS)?
Best regards
Mats
Message #4 by Tim Heuer <TimH@i...> on Fri, 24 Aug 2001 09:15:47 -0700
|
|
Al,
What SCM system are you implementing and does it integrate into the IDE?
-----Original Message-----
From: Al LeMay [mailto:alemay@d...]
Sent: Friday, August 24, 2001 9:00 AM
To: ASP+
Subject: [aspx] RE: Visual SourceSafe.
To chime in here...
VSS integration is very "buggy" at best in .Net. We have a large project in
progress, and have decided to leave VSS for another product.
As noted FPSE is the actual best way to manage the project. It is tricky,
but it works. We leave the files checked out in VSS on the web server.
(Exclusive check outs only in VSS.) Then you just open the project through
the FPSE. The .SLN file is also checked into VSS, but it is checked out
locally in the Visual Studio Projects folder on the developers system. As I
say... it seems to work well, but may not be the best way to go about it.
Switch to a better SCM tool and you will be happier, much.
Al LeMay
Virtuoso
Quality Assurance Manager
alemay@d...
http://www.virtuoso.com/
-----Original Message-----
From: Tim Heuer [mailto:TimH@i...]
Sent: Friday, August 24, 2001 8:33 AM
To: ASP+
Subject: [aspx] RE: Visual SourceSafe.
Mats,
We too have had significant issues with the VSS integration with the web
projects. After talking with some at Microsoft, they suggested not using
FPSE access and using the file share access (that didn't work too well with
us). As far as some lessons learned in our current project (all these are
regarding using the integration within the IDE):
(1) VSS didn't work too well with team development re: web projects (main
project kept getting checked out by all users, even when VSS said nobody had
it checked out)
(2) licenses.licx file - if your developers actually use the "Design" mode
for the webforms, this file will haunt you...whenever the Designer mode in
webforms are used, this file needs modification and gets automatically
checked out by the author...but generally the author doesn't know it, so
when another person uses the designer, they can't modify anything, because
the file needs to be checked in...our
workaround: don't use designer
(3) Checking our only the source files - bad idea...if needing to modify
only the source, check out the entire file (.aspx, .aspx.cs, .aspx.resx)
- it will make your life easier
(4) .resx files - these are for webforms and shouldn't be deleted...will
reak havoc
(5) Team Development in general: We had problems in a dev team of 6 working
on the same web project...when I "built" the application it would break
other peoples code. What we did was instruct all developers to use the
"src" attribute on their pages, and additionally debug locally, by attaching
to their own process and *not* the web server to not cause anyone else lock
ups.
We don't feel it's ready for primetime yet, but trust the folks at MS are
figuring out all the oddities.
Make sure you are using the VSS6c that VS.NET came with also.
Tim
-----Original Message-----
From: Mats Boberg [mailto:mats.boberg@n...]
Sent: Friday, August 24, 2001 7:09 AM
To: ASP+
Subject: [aspx] Visual SourceSafe.
Hi,
We are trying to manage our .Net projects with Visual SourceSafe, but have
not quite figured out how to make it work with web projects. There seems to
be a conflict between the Frontpage Server Extensions and the version
control of VSS. Is there an easy solution to this problem, or do we need to
keep the projects separate (web projects managed by Frontpage Server
Extensions and class libraries in VSS)?
Best regards
Mats
Message #5 by "Al LeMay" <alemay@d...> on Fri, 24 Aug 2001 09:27:45 -0700
|
|
We have chosen StarBase's StarTeam. There is an integration component
for the client tool, but we are not using it, because some of the
developers are using other tools to write the source code. We leave it
up to them as to how much integration they want with the SCM server.
I can tell you that the product is closer to ClearCase than VSS. If you
would like to take the discussion any further we can off-line, as I do
not really want to promote anybody else tools on the list. I will say
their web site is http://www.starbase.com/ and we are using the
enterprise version of the product.
There were other products we reviewed, but this met all our needs.
Al
-----Original Message-----
From: Tim Heuer [mailto:TimH@i...]
Sent: Friday, August 24, 2001 9:16 AM
To: ASP+
Subject: [aspx] RE: Visual SourceSafe.
Al,
What SCM system are you implementing and does it integrate into the IDE?
-----Original Message-----
From: Al LeMay [mailto:alemay@d...]
Sent: Friday, August 24, 2001 9:00 AM
To: ASP+
Subject: [aspx] RE: Visual SourceSafe.
To chime in here...
VSS integration is very "buggy" at best in .Net. We have a large
project in progress, and have decided to leave VSS for another product.
As noted FPSE is the actual best way to manage the project. It is
tricky, but it works. We leave the files checked out in VSS on the web
server. (Exclusive check outs only in VSS.) Then you just open the
project through the FPSE. The .SLN file is also checked into VSS, but
it is checked out locally in the Visual Studio Projects folder on the
developers system. As I say... it seems to work well, but may not be
the best way to go about it.
Switch to a better SCM tool and you will be happier, much.
Al LeMay
Virtuoso
Quality Assurance Manager
alemay@d...
http://www.virtuoso.com/
-----Original Message-----
From: Tim Heuer [mailto:TimH@i...]
Sent: Friday, August 24, 2001 8:33 AM
To: ASP+
Subject: [aspx] RE: Visual SourceSafe.
Mats,
We too have had significant issues with the VSS integration with the web
projects. After talking with some at Microsoft, they suggested not
using FPSE access and using the file share access (that didn't work too
well with us). As far as some lessons learned in our current project
(all these are regarding using the integration within the IDE):
(1) VSS didn't work too well with team development re: web projects
(main project kept getting checked out by all users, even when VSS said
nobody had it checked out)
(2) licenses.licx file - if your developers actually use the "Design"
mode for the webforms, this file will haunt you...whenever the Designer
mode in webforms are used, this file needs modification and gets
automatically checked out by the author...but generally the author
doesn't know it, so when another person uses the designer, they can't
modify anything, because the file needs to be checked in...our
workaround: don't use designer
(3) Checking our only the source files - bad idea...if needing to modify
only the source, check out the entire file (.aspx, .aspx.cs, .aspx.resx)
- it will make your life easier
(4) .resx files - these are for webforms and shouldn't be deleted...will
reak havoc
(5) Team Development in general: We had problems in a dev team of 6
working on the same web project...when I "built" the application it
would break other peoples code. What we did was instruct all developers
to use the "src" attribute on their pages, and additionally debug
locally, by attaching to their own process and *not* the web server to
not cause anyone else lock ups.
We don't feel it's ready for primetime yet, but trust the folks at MS
are figuring out all the oddities.
Make sure you are using the VSS6c that VS.NET came with also.
Tim
-----Original Message-----
From: Mats Boberg [mailto:mats.boberg@n...]
Sent: Friday, August 24, 2001 7:09 AM
To: ASP+
Subject: [aspx] Visual SourceSafe.
Hi,
We are trying to manage our .Net projects with Visual SourceSafe, but
have not quite figured out how to make it work with web projects. There
seems to be a conflict between the Frontpage Server Extensions and the
version control of VSS. Is there an easy solution to this problem, or do
we need to keep the projects separate (web projects managed by Frontpage
Server Extensions and class libraries in VSS)?
Best regards
Mats
|
|
|
View Cart
