I have just finished reading the "Team Development with Visual Studio .NET
and Visual SourceSafe" patterns & practices white paper. I just wanted to
get a good feel from others if what they suggest here is really the best
implementation for team development. My company only has a handful of
developers (2 currently, as many as 5 possibly in the future) that need to
work on the same ASP.NET projects. All of our existing apps are in classic
ASP and we do not even use source control since there is only two of us and
we communicate well ;). We simply use InterDev to connect to the web site
and edit the files necessary as long as we know the other isn't working on
it as well. This white paper suggest setting up Visual SourceSafe in such a
way that all code will be executed on the developer's actual workstation,
which is a big concern for me.
Following are a few things in this white paper I do not understand:
1. Since all code is executed on the developer's workstation, and not on the
development web server, how will images, external javascript files, etc. be
referenced? Will the ENTIRE site be copied to EACH developer's workstation?
Our sites are rather huge and this may not be a good idea. We also do not
want to put the entire web site in Visual SourceSafe -- only the .NET/HTML
code. In other words -- no images, flash files, etc. in VSS.
2. How can we be sure our development server is updated upon files being
checked in? I'd like our development server to always be running the latest
version of the software available (meaning a rebuild would be necessary
everytime code changes). How can we implement this on a development server?
This is required for our QA department to always be able to test the latest
version of our sites.
I know I'll think of some other scenario's as well, but these are just a few
of my first concerns. Is there an easier way to work on ASP.NET projects
with other developers withOUT using VSS and making things this complicated?
Thanks!
Shawn 5 2053
Shawn:
That guide is gold. Everything they say is on the ball and totally worth
following. To answer some of your questions:
"all code will be executed on the developer's actual workstation"
When developers debug an application it locks the IIS process.. If you
develop on a shared server you'll have serious problems because of this.
Also, you don't want one developer's broken build to break all other builds.
1 - You should go all in, not partially else youl'l run into these problems.
2 - That guide talks about the "build process" and through the build process
and continuous integration (via CruiseControl.N et) you can easily keep a
server up to date..
It seems to me that you haven't fully bought into the benefits of source
control. Until you're there, I wouldn't bother and I'd stick with the "good
communication" approach. .
Karl
--
MY ASP.Net tutorials http://www.openmymind.net/
"Shawn Berg" <sh***@saeweb.c om> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. .. I have just finished reading the "Team Development with Visual Studio .NET and Visual SourceSafe" patterns & practices white paper. I just wanted to get a good feel from others if what they suggest here is really the best implementation for team development. My company only has a handful of developers (2 currently, as many as 5 possibly in the future) that need to work on the same ASP.NET projects. All of our existing apps are in classic ASP and we do not even use source control since there is only two of us and we communicate well ;). We simply use InterDev to connect to the web site and edit the files necessary as long as we know the other isn't working on it as well. This white paper suggest setting up Visual SourceSafe in such a way that all code will be executed on the developer's actual workstation, which is a big concern for me.
Following are a few things in this white paper I do not understand:
1. Since all code is executed on the developer's workstation, and not on the development web server, how will images, external javascript files, etc. be referenced? Will the ENTIRE site be copied to EACH developer's workstation? Our sites are rather huge and this may not be a good idea. We also do not want to put the entire web site in Visual SourceSafe -- only the .NET/HTML code. In other words -- no images, flash files, etc. in VSS.
2. How can we be sure our development server is updated upon files being checked in? I'd like our development server to always be running the latest version of the software available (meaning a rebuild would be necessary everytime code changes). How can we implement this on a development server? This is required for our QA department to always be able to test the latest version of our sites.
I know I'll think of some other scenario's as well, but these are just a few of my first concerns. Is there an easier way to work on ASP.NET projects with other developers withOUT using VSS and making things this complicated?
Thanks!
Shawn
Shawn Berg wrote: we do not even use source control since there is only two of us and we communicate well ;). We simply use InterDev to connect to the web
site and edit the files necessary as long as we know the other isn't
working on it as well.
First off, Yikes! You have a SINGLE copy of your code living in a
SINGLE place? As in, one errent delete away from oblivion? And no way
to track down changes that may be causing bugs?
Following are a few things in this white paper I do not understand:
1. Since all code is executed on the developer's workstation, and not
on the development web server, how will images, external javascript files,
etc. be referenced? Will the ENTIRE site be copied to EACH developer's
workstation?
Yes. All the code is on your box. A 200GB hard drive costs $200. Are
you saying you can't fit your Huge site on one of those?
And Yes, ALL the code is in source control. Even the images and .SWFs.
2. How can we be sure our development server is updated upon files
being checked in?
Build & deploy from VSS. You can do that. No, really you can!
Is there an easier way to work on ASP.NET projects with other developers withOUT using VSS and making things this
complicated?
I think you will soon discover the true meaning of "complicate d" if you
continue with your current process. Everybody screws up from time to
time. Personally, when I need to roll back a whole day's worth of
changes that inadvertently broke something, I'd rather not have to do
it by hand.
Good luck!
Jason http://www.expatsoftware.com/
Hi Shawn,
We followed that guide almost to the letter in a small team of 4-5
developers for an ASP.NET project and it was very good. The worst problem
was with VSS which sometimes got corrupted and had to be repaired.
The key to working that way is to have a rule that no one can check in a
page if it doesn't build without error. It doesn't have to be complete, it
just has to compile. If there are errors and you "get latest", you're stuck
with bad code on your machine.
When we thought we had a build to send to QC, we'd get the latest and test
it locally. Then, someone would compile the project and post the relevant
files to the development server. After a test there, we'd label the build in
VSS and tell QC to go get it.
Ken
Microsoft MVP [ASP.NET]
"Shawn Berg" <sh***@saeweb.c om> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. .. I have just finished reading the "Team Development with Visual Studio .NET and Visual SourceSafe" patterns & practices white paper. I just wanted to get a good feel from others if what they suggest here is really the best implementation for team development. My company only has a handful of developers (2 currently, as many as 5 possibly in the future) that need to work on the same ASP.NET projects. All of our existing apps are in classic ASP and we do not even use source control since there is only two of us and we communicate well ;). We simply use InterDev to connect to the web site and edit the files necessary as long as we know the other isn't working on it as well. This white paper suggest setting up Visual SourceSafe in such a way that all code will be executed on the developer's actual workstation, which is a big concern for me.
Following are a few things in this white paper I do not understand:
1. Since all code is executed on the developer's workstation, and not on the development web server, how will images, external javascript files, etc. be referenced? Will the ENTIRE site be copied to EACH developer's workstation? Our sites are rather huge and this may not be a good idea. We also do not want to put the entire web site in Visual SourceSafe -- only the .NET/HTML code. In other words -- no images, flash files, etc. in VSS.
2. How can we be sure our development server is updated upon files being checked in? I'd like our development server to always be running the latest version of the software available (meaning a rebuild would be necessary everytime code changes). How can we implement this on a development server? This is required for our QA department to always be able to test the latest version of our sites.
I know I'll think of some other scenario's as well, but these are just a few of my first concerns. Is there an easier way to work on ASP.NET projects with other developers withOUT using VSS and making things this complicated?
Thanks!
Shawn
Ken,
Thanks for your informative and encouraging response. After the brief
convincing here, I am definitely moving forward to put this environment into
place.
The reason I originally asked about the web site existing on each developers
workstation as well is because we have some virtual directories that hold
hundreds of gigabytes of videos and image files, and there is absolutely no
reason to keep these under source control, and to push them to each
developers machine. The problem posed, however, is that some of the code on
the ASP.NET web sites we will be placing in VSS will need to access the
files in these subdirectories programatically . Is it possible to test that
without copying hundreds of GBs of data to each developer's workstation?
This data is also updated frequently and will cause a network bandwidth
nightmare if it will have to be updated on each developer's machine. Maybe
somebody could explain a little better exactly how this works?
Also, I planned on putting VSS and it's databases on a server separate from
our development Web server. This seems standard, but not exactly clear in
the white-paper. Is this common?
Shawn
"Ken Cox [Microsoft MVP]" <BA************ @sympatico.ca> wrote in message
news:#L******** ******@tk2msftn gp13.phx.gbl... Hi Shawn,
We followed that guide almost to the letter in a small team of 4-5 developers for an ASP.NET project and it was very good. The worst problem was with VSS which sometimes got corrupted and had to be repaired.
The key to working that way is to have a rule that no one can check in a page if it doesn't build without error. It doesn't have to be complete, it just has to compile. If there are errors and you "get latest", you're
stuck with bad code on your machine.
When we thought we had a build to send to QC, we'd get the latest and test it locally. Then, someone would compile the project and post the relevant files to the development server. After a test there, we'd label the build
in VSS and tell QC to go get it.
Ken Microsoft MVP [ASP.NET]
"Shawn Berg" <sh***@saeweb.c om> wrote in message news:%2******** ********@tk2msf tngp13.phx.gbl. ..I have just finished reading the "Team Development with Visual Studio
..NET and Visual SourceSafe" patterns & practices white paper. I just wanted
to get a good feel from others if what they suggest here is really the best implementation for team development. My company only has a handful of developers (2 currently, as many as 5 possibly in the future) that need
to work on the same ASP.NET projects. All of our existing apps are in
classic ASP and we do not even use source control since there is only two of us and we communicate well ;). We simply use InterDev to connect to the web
site and edit the files necessary as long as we know the other isn't working
on it as well. This white paper suggest setting up Visual SourceSafe in
such a way that all code will be executed on the developer's actual
workstation, which is a big concern for me.
Following are a few things in this white paper I do not understand:
1. Since all code is executed on the developer's workstation, and not on the development web server, how will images, external javascript files, etc. be referenced? Will the ENTIRE site be copied to EACH developer's workstation? Our sites are rather huge and this may not be a good idea. We also do
not want to put the entire web site in Visual SourceSafe -- only the
..NET/HTML code. In other words -- no images, flash files, etc. in VSS.
2. How can we be sure our development server is updated upon files being checked in? I'd like our development server to always be running the latest version of the software available (meaning a rebuild would be necessary everytime code changes). How can we implement this on a development server? This is required for our QA department to always be able to test the latest version of our sites.
I know I'll think of some other scenario's as well, but these are just a few of my first concerns. Is there an easier way to work on ASP.NET projects with other developers withOUT using VSS and making things this complicated?
Thanks!
Shawn
Hi Shawn,
We had a similar situation where we had thousands of PDF files on the file
system that were triggered by and linked from our Web application and a
backend database process. On everyone's machine, we set up a virtual
directory in IIS that pointed to a common mapped drive on another file
server. That's where the PDFs were stored. I can't recall the detail now but
it seemed to work very well except when we had to change the passwords that
IIS kept for the remote server. That caused a fair amount of confusion for a
while because the app would break without explanation.
Of course the files we were creating and referencing were demo files. We
used the web.config and a little code to detect whether the PDFs were to
come from the development remote server, the QC remote server or the
production remote server.
So, you shouldn't need to copy anything more than the updated source code
files and a few images that are part of the Visual Studio project that you
are checking out from VSS.
Ken
"Shawn Berg" <sh***@saeweb.c om> wrote in message
news:u0******** ******@TK2MSFTN GP15.phx.gbl... Ken,
Thanks for your informative and encouraging response. After the brief convincing here, I am definitely moving forward to put this environment into place.
The reason I originally asked about the web site existing on each developers workstation as well is because we have some virtual directories that hold hundreds of gigabytes of videos and image files, and there is absolutely no reason to keep these under source control, and to push them to each developers machine. The problem posed, however, is that some of the code on the ASP.NET web sites we will be placing in VSS will need to access the files in these subdirectories programatically . Is it possible to test that without copying hundreds of GBs of data to each developer's workstation? This data is also updated frequently and will cause a network bandwidth nightmare if it will have to be updated on each developer's machine. Maybe somebody could explain a little better exactly how this works?
Also, I planned on putting VSS and it's databases on a server separate from our development Web server. This seems standard, but not exactly clear in the white-paper. Is this common?
Shawn
"Ken Cox [Microsoft MVP]" <BA************ @sympatico.ca> wrote in message news:#L******** ******@tk2msftn gp13.phx.gbl... Hi Shawn,
We followed that guide almost to the letter in a small team of 4-5 developers for an ASP.NET project and it was very good. The worst problem was with VSS which sometimes got corrupted and had to be repaired.
The key to working that way is to have a rule that no one can check in a page if it doesn't build without error. It doesn't have to be complete, it just has to compile. If there are errors and you "get latest", you're stuck with bad code on your machine.
When we thought we had a build to send to QC, we'd get the latest and test it locally. Then, someone would compile the project and post the relevant files to the development server. After a test there, we'd label the build in VSS and tell QC to go get it.
Ken Microsoft MVP [ASP.NET]
"Shawn Berg" <sh***@saeweb.c om> wrote in message news:%2******** ********@tk2msf tngp13.phx.gbl. .. >I have just finished reading the "Team Development with Visual Studio .NET > and Visual SourceSafe" patterns & practices white paper. I just wanted to > get a good feel from others if what they suggest here is really the > best > implementation for team development. My company only has a handful of > developers (2 currently, as many as 5 possibly in the future) that need to > work on the same ASP.NET projects. All of our existing apps are in classic > ASP and we do not even use source control since there is only two of us > and > we communicate well ;). We simply use InterDev to connect to the web site > and edit the files necessary as long as we know the other isn't working on > it as well. This white paper suggest setting up Visual SourceSafe in such > a > way that all code will be executed on the developer's actual workstation, > which is a big concern for me. > > Following are a few things in this white paper I do not understand: > > 1. Since all code is executed on the developer's workstation, and not > on > the > development web server, how will images, external javascript files, > etc. > be > referenced? Will the ENTIRE site be copied to EACH developer's > workstation? > Our sites are rather huge and this may not be a good idea. We also do not > want to put the entire web site in Visual SourceSafe -- only the .NET/HTML > code. In other words -- no images, flash files, etc. in VSS. > > 2. How can we be sure our development server is updated upon files > being > checked in? I'd like our development server to always be running the > latest > version of the software available (meaning a rebuild would be necessary > everytime code changes). How can we implement this on a development > server? > This is required for our QA department to always be able to test the > latest > version of our sites. > > I know I'll think of some other scenario's as well, but these are just > a > few > of my first concerns. Is there an easier way to work on ASP.NET > projects > with other developers withOUT using VSS and making things this > complicated? > > Thanks! > > Shawn > >
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: codabill |
last post by:
Can someone please refer me to books, articles, websites where I can obtain
information on how to set up VS2003 for team development.
I am a project manager for a non-trivial military software project that is
migrating from ASP to ASP.NET. I have a team of 9 developers using VS2003.
Of concern to me is that VS2003 compiles its projects into a single DLL.
This will not work for our environment as our architecture is SOA based and
as...
|
by: Sammy |
last post by:
I have a development team working on a web application. I have a development
server with VS 2003 installed. Each developer checks out a copy of the
source code via source safe and edits/compiles/debugs it on their machine.
However, we always need to debug this code on the server itself, since, for
example we have external devices (mobiles) that call web services, that are
only exposed via the server.
I do not want to give server access...
|
by: Joe |
last post by:
Based on what it says in the subscribers downloads for Team Suite I would
think it would be there. Can it be downloaded separately or is it just the
Workgroups one?
Visual Studio Team System consists of:
a.. Visual Studio Team Foundation Server, an extensible team collaboration
server that enables all members of the extended IT team to effortlessly
manage and track the progress and health of projects
b.. Visual Studio Team Edition for...
|
by: Martin |
last post by:
Hello,
We are in the process of putting together an A class C++ Development
team(ecommerce / billing applications) for a project in the Bay Area.
Reqt. details:
ReqId : Req-3911 - C++ Senior Developer
Primary Skills: C++, SQL
Secondary Skills: XML, Oracle
Description: As a part of the development team for our client's
|
by: bharathreddy |
last post by:
This Article gives an introduction to VSTS Team Foundation & fundamental difference between Visual Source Safe (VSS) and VSTS Team Foundation.
Team Foundation is a set of tools and technologies that enable a team to collaborate and coordinate a project (software or non software projects). The team collaboration is achieved by several tools and features available as part of "Team Foundation".
Team Foundation Server
The Team...
| |
by: Smokey Grindel |
last post by:
Ok this is making me want to rip my hair out trying to figure out the real
price of this thing... we are trying to make up our 2008 budget... we have
VS 2005 Pro right now... we like the team features in 08... and want to
figure out the price... I've seen everything from $2,500 to $15k... wich
$15k is ridicilous.... anyways... then it has editions in 2005! database,
app analyst, performance.... what ever they where called... then in 2008...
|
by: Joseph Geretz |
last post by:
Our application consists of a suite of webservices. Depending upon
application area, different methods are grouped into separate webservice
projects, and are developed and maintained by separate development teams.
Let's assume for the sake of this discussion, that Team A, Team B and Team C
are working on separate webservice projects. (Ultimately, these separate
projects will integrate and comprise the entire application solution.)
Our...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
| |
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |