467,166 Members | 1,133 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,166 developers. It's quick & easy.

Do I Really Need to Copy All This?

I am using VSNET 2003 to build an ASP.NET/VB set of pages. There are
currently about a dozen aspx pages. When I make even a minor change to one
page I currently rebuild the solution, copy the project files to a copy
directory on my local wwwroot and then FTP all those files and directories
to my ISP account to be able to see the change on my web site. This is a lot
of data to FTP every time (the bin directory alone is close to 4MB)

Is there a better way?

Wayne
Nov 19 '05 #1
  • viewed: 1379
Share:
6 Replies
You do not need to copy:
- .vb or .cs files (source code)
- .resx (ressource files since they are compile into the bin directory)
- .suo, sln, .vbproj, .csproj .... all projects, visual studio related files
- Inside the bin directory .pdb (those files contain only debug information)
only dll are required.

However don't forget to copy:
- Web.Config
- Global.asax
and the bin directory.
--------------------------
Jean-Claude Morin, MCP
Software Developer
2k1Soft/kCentric, Canada
"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:e5****************@TK2MSFTNGP09.phx.gbl...
I am using VSNET 2003 to build an ASP.NET/VB set of pages. There are
currently about a dozen aspx pages. When I make even a minor change to one
page I currently rebuild the solution, copy the project files to a copy
directory on my local wwwroot and then FTP all those files and directories
to my ISP account to be able to see the change on my web site. This is a lot of data to FTP every time (the bin directory alone is close to 4MB)

Is there a better way?

Wayne

Nov 19 '05 #2
<<.pdb (those files contain only debug information)>>

You should, in fact, copy the .pdb file to production IF/WHEN you have
exception handlers that make user of the stack trace (e.g., to log the exact
line of code that choked, thereby throwing the exception). If you are doing
this (I can't imagine why anyone wouldn't want this information in a
produciton system), then you will need to copy BOTH the .pdb and .dll file
whenever you recompile - as the .pdb version is logically tied to the .dll
version.

HTH


"Jc Morin" <mi****************@jcmorin.net> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
You do not need to copy:
- .vb or .cs files (source code)
- .resx (ressource files since they are compile into the bin directory)
- .suo, sln, .vbproj, .csproj .... all projects, visual studio related
files
- Inside the bin directory .pdb (those files contain only debug
information)
only dll are required.

However don't forget to copy:
- Web.Config
- Global.asax
and the bin directory.
--------------------------
Jean-Claude Morin, MCP
Software Developer
2k1Soft/kCentric, Canada
"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:e5****************@TK2MSFTNGP09.phx.gbl...
I am using VSNET 2003 to build an ASP.NET/VB set of pages. There are
currently about a dozen aspx pages. When I make even a minor change to
one
page I currently rebuild the solution, copy the project files to a copy
directory on my local wwwroot and then FTP all those files and
directories
to my ISP account to be able to see the change on my web site. This is a

lot
of data to FTP every time (the bin directory alone is close to 4MB)

Is there a better way?

Wayne


Nov 19 '05 #3
I agree with you Alfred, but the first question about data size, so I think
that it's important to point out that pdb files are not *required*.

Any good tracing library that show line number, full stack trace and various
stuff required those files to work property...
This is a lot of data to FTP every time
Yep, you can still cut on those pdb files if data transfer is an issue. :)
--------------------------
Jean-Claude Morin, MCP
Software Developer
2k1Soft/kCentric, Canada
"Alfred E. Newman" <Mr******@WhatMeWorry.com> wrote in message
news:OV**************@tk2msftngp13.phx.gbl... <<.pdb (those files contain only debug information)>>

You should, in fact, copy the .pdb file to production IF/WHEN you have
exception handlers that make user of the stack trace (e.g., to log the exact line of code that choked, thereby throwing the exception). If you are doing this (I can't imagine why anyone wouldn't want this information in a
produciton system), then you will need to copy BOTH the .pdb and .dll file
whenever you recompile - as the .pdb version is logically tied to the .dll
version.

HTH


"Jc Morin" <mi****************@jcmorin.net> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
You do not need to copy:
- .vb or .cs files (source code)
- .resx (ressource files since they are compile into the bin directory)
- .suo, sln, .vbproj, .csproj .... all projects, visual studio related
files
- Inside the bin directory .pdb (those files contain only debug
information)
only dll are required.

However don't forget to copy:
- Web.Config
- Global.asax
and the bin directory.
--------------------------
Jean-Claude Morin, MCP
Software Developer
2k1Soft/kCentric, Canada
"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:e5****************@TK2MSFTNGP09.phx.gbl...
I am using VSNET 2003 to build an ASP.NET/VB set of pages. There are
currently about a dozen aspx pages. When I make even a minor change to
one
page I currently rebuild the solution, copy the project files to a copy
directory on my local wwwroot and then FTP all those files and
directories
to my ISP account to be able to see the change on my web site. This is
a lot
of data to FTP every time (the bin directory alone is close to 4MB)

Is there a better way?

Wayne



Nov 19 '05 #4
If you are only modifying the HTML, then you can just copy the relevant aspx
page(s), i.e. no changes to the code behind. Conversely, if you are just
modifying the functionality, just copy the bin directory and not the aspx
pages

Paul

"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:e5**************@TK2MSFTNGP09.phx.gbl...
I am using VSNET 2003 to build an ASP.NET/VB set of pages. There are
currently about a dozen aspx pages. When I make even a minor change to one
page I currently rebuild the solution, copy the project files to a copy
directory on my local wwwroot and then FTP all those files and directories
to my ISP account to be able to see the change on my web site. This is a lot of data to FTP every time (the bin directory alone is close to 4MB)

Is there a better way?

Wayne

Nov 19 '05 #5
Hi Wayne,

If you make a change to the programming code in a DLL, you need to copy over
the DLL. If you make a change to a template (aspx or ascx) that doesn't
affect the CodeBehind DLL, just copy over the template.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:e5****************@TK2MSFTNGP09.phx.gbl...
I am using VSNET 2003 to build an ASP.NET/VB set of pages. There are
currently about a dozen aspx pages. When I make even a minor change to one
page I currently rebuild the solution, copy the project files to a copy
directory on my local wwwroot and then FTP all those files and directories
to my ISP account to be able to see the change on my web site. This is a
lot
of data to FTP every time (the bin directory alone is close to 4MB)

Is there a better way?

Wayne

Nov 19 '05 #6
Thanks for the responses. Good to know I can separate the html from the
dll's

Wayne

"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...
Hi Wayne,

If you make a change to the programming code in a DLL, you need to copy over the DLL. If you make a change to a template (aspx or ascx) that doesn't
affect the CodeBehind DLL, just copy over the template.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.

"Wayne Wengert" <wa***************@wengert.com> wrote in message
news:e5****************@TK2MSFTNGP09.phx.gbl...
I am using VSNET 2003 to build an ASP.NET/VB set of pages. There are
currently about a dozen aspx pages. When I make even a minor change to one page I currently rebuild the solution, copy the project files to a copy
directory on my local wwwroot and then FTP all those files and directories to my ISP account to be able to see the change on my web site. This is a
lot
of data to FTP every time (the bin directory alone is close to 4MB)

Is there a better way?

Wayne


Nov 19 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Peter Young | last post: by
2 posts views Thread by James | last post: by
11 posts views Thread by Mr. Berserker | last post: by
27 posts views Thread by mike3 | last post: by
17 posts views Thread by Chris M. Thomasson | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.