By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,679 Members | 2,036 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,679 IT Pros & Developers. It's quick & easy.

Help:How to do the version control of ASP.Net application?

P: n/a
Hi,

I have a web site built in ASP.Net 1.1 running on production server. It's the version 1.0.
Now I need to build the version 2.0 for this web site. The version 2.0 will be built based
on the code of version 1.0.

Since it take some time to have the version 2.0 ready for production, the code of version 1.0
needs to be kept somewhere for possible bug fix. At this point, the only feasible idea I have is:
1) create a new project for version 2.0 on machine A with same project name and copy code of
version 1.0 over.
2) keep the code of version 1.0 on machine B.
3) when there are bugs found on version 1.0 on production server, fix the bug in the code on
machine B and post new code to production server, then make the same change in the
code on machine A so that the version 2.0 will contain these bug fixes.

The reason I need to keep the code of version 1.0 on another machine is that new code in
version 2.0 may be not finished and untested when bug occurs on production server. I cannot
fix the bug on machine A and post the new DLL containing unfinished and untested code to
production server.

Even this idea will work, but I don't like it since I have to do the same job on both machines.

I use Visual Studio 2003 and C# for this web site.

Would you please tell me are there better ways I can do this?

Thank you

hb
Jul 20 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hongbo,
for this kind of task, you're going to need a source control
application. Most of these apps support versioning control, along with
code diff and merge capabilities. Some examples are Sourcegear Vault,
Subversion (free) , or if you're willing to go to VS.NET 2005, Team
System.

Happy Coding!
Hongbo wrote:
Hi,

I have a web site built in ASP.Net 1.1 running on production server. It's the version 1.0.
Now I need to build the version 2.0 for this web site. The version 2.0 will be built based
on the code of version 1.0.

Since it take some time to have the version 2.0 ready for production, the code of version 1.0
needs to be kept somewhere for possible bug fix. At this point, the only feasible idea I have is:
1) create a new project for version 2.0 on machine A with same project name and copy code of
version 1.0 over.
2) keep the code of version 1.0 on machine B.
3) when there are bugs found on version 1.0 on production server, fix the bug in the code on
machine B and post new code to production server, then make the same change in the
code on machine A so that the version 2.0 will contain these bug fixes.

The reason I need to keep the code of version 1.0 on another machine is that new code in
version 2.0 may be not finished and untested when bug occurs on production server. I cannot
fix the bug on machine A and post the new DLL containing unfinished and untested code to
production server.

Even this idea will work, but I don't like it since I have to do the same job on both machines.

I use Visual Studio 2003 and C# for this web site.

Would you please tell me are there better ways I can do this?

Thank you

hb
------=_NextPart_000_000A_01C6AC14.B5DC12A0
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Google-AttachSize: 3275

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1555" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I have a web site built in ASP.Net 1.1 running on
production server. It's the version 1.0.</FONT></DIV>
<DIV><FONT face=Arial size=2>Now I need to build the version 2.0 for this web
site. The version 2.0 will be built based</FONT></DIV>
<DIV><FONT face=Arial size=2>on the code of version 1.0.</FONT><FONT face=Arial
size=2</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Since it take some time to have the version 2.0
ready for production, the code of version 1.0</FONT></DIV>
<DIV><FONT face=Arial size=2>needs to </FONT><FONT face=Arial size=2>be kept
somewhere for possible&nbsp;bug fix. At this point, the only feasible idea I
have is: </FONT></DIV>
<DIV><FONT face=Arial size=2>1) create a new </FONT><FONT face=Arial
size=2>project for version 2.0 on machine A with same project name and copy code
of</FONT></DIV>
<DIV><FONT face=Arial size=2>version 1.0 over.</FONT></DIV>
<DIV><FONT face=Arial size=2>2) keep the code </FONT><FONT face=Arial size=2>of
version 1.0 on </FONT><FONT face=Arial size=2>machine B. </FONT></DIV>
<DIV><FONT face=Arial size=2>3) when there are bugs found on version 1.0 on
production server, fix the bug&nbsp;in the code on</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; machine B and post new code to
production server, then make the same change in the </FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; code on machine A so that the
version 2.0 will contain these bug fixes.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>The reason I need to keep the code of version 1.0
on another machine is that new code in </FONT></DIV>
<DIV><FONT face=Arial size=2>version 2.0 may be not finished and untested when
bug occurs on production server. I cannot</FONT></DIV>
<DIV><FONT face=Arial size=2>fix the bug on machine A and post the new DLL
containing unfinished and untested code to</FONT></DIV>
<DIV><FONT face=Arial size=2>production server.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Even this idea will work, but I don't like it since
I have to do the same job on both machines.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I use Visual Studio 2003 and C# for this web site.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Would you please tell me are there better ways I
can do this?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thank you</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>hb</FONT></DIV></BODY></HTML>

------=_NextPart_000_000A_01C6AC14.B5DC12A0--
Jul 21 '06 #2

P: n/a
Thank you!
"JustinBlat" <pi*******@yahoo.comwrote in message
news:11**********************@i3g2000cwc.googlegro ups.com...
Hongbo,
for this kind of task, you're going to need a source control
application. Most of these apps support versioning control, along with
code diff and merge capabilities. Some examples are Sourcegear Vault,
Subversion (free) , or if you're willing to go to VS.NET 2005, Team
System.

Happy Coding!
Hongbo wrote:
Hi,

I have a web site built in ASP.Net 1.1 running on production server.
It's the version 1.0.
Now I need to build the version 2.0 for this web site. The version 2.0
will be built based
on the code of version 1.0.

Since it take some time to have the version 2.0 ready for production,
the code of version 1.0
needs to be kept somewhere for possible bug fix. At this point, the only
feasible idea I have is:
1) create a new project for version 2.0 on machine A with same project
name and copy code of
version 1.0 over.
2) keep the code of version 1.0 on machine B.
3) when there are bugs found on version 1.0 on production server, fix
the bug in the code on
machine B and post new code to production server, then make the same
change in the
code on machine A so that the version 2.0 will contain these bug
fixes.

The reason I need to keep the code of version 1.0 on another machine is
that new code in
version 2.0 may be not finished and untested when bug occurs on
production server. I cannot
fix the bug on machine A and post the new DLL containing unfinished and
untested code to
production server.

Even this idea will work, but I don't like it since I have to do the
same job on both machines.

I use Visual Studio 2003 and C# for this web site.

Would you please tell me are there better ways I can do this?

Thank you

hb
------=_NextPart_000_000A_01C6AC14.B5DC12A0
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Google-AttachSize: 3275

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1555" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I have a web site built in ASP.Net 1.1
running on
production server. It's the version 1.0.</FONT></DIV>
<DIV><FONT face=Arial size=2>Now I need to build the version 2.0 for
this web
site. The version 2.0 will be built based</FONT></DIV>
<DIV><FONT face=Arial size=2>on the code of version 1.0.</FONT><FONT
face=Arial
size=2</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Since it take some time to have the version
2.0
ready for production, the code of version 1.0</FONT></DIV>
<DIV><FONT face=Arial size=2>needs to </FONT><FONT face=Arial size=2>be
kept
somewhere for possible&nbsp;bug fix. At this point, the only feasible
idea I
have is: </FONT></DIV>
<DIV><FONT face=Arial size=2>1) create a new </FONT><FONT face=Arial
size=2>project for version 2.0 on machine A with same project name and
copy code
of</FONT></DIV>
<DIV><FONT face=Arial size=2>version 1.0 over.</FONT></DIV>
<DIV><FONT face=Arial size=2>2) keep the code </FONT><FONT face=Arial
size=2>of
version 1.0 on </FONT><FONT face=Arial size=2>machine B. </FONT></DIV>
<DIV><FONT face=Arial size=2>3) when there are bugs found on version 1.0
on
production server, fix the bug&nbsp;in the code on</FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; machine B and post new
code to
production server, then make the same change in the </FONT></DIV>
<DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; code on machine A so
that the
version 2.0 will contain these bug fixes.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>The reason I need to keep the code of
version 1.0
on another machine is that new code in </FONT></DIV>
<DIV><FONT face=Arial size=2>version 2.0 may be not finished and
untested when
bug occurs on production server. I cannot</FONT></DIV>
<DIV><FONT face=Arial size=2>fix the bug on machine A and post the new
DLL
containing unfinished and untested code to</FONT></DIV>
<DIV><FONT face=Arial size=2>production server.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Even this idea will work, but I don't like
it since
I have to do the same job on both machines.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I use Visual Studio 2003 and C# for this
web site.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Would you please tell me are there better
ways I
can do this?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thank you</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>hb</FONT></DIV></BODY></HTML>

------=_NextPart_000_000A_01C6AC14.B5DC12A0--

Jul 21 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.