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

Pros and Cons - publishing vs Copying

P: n/a
Since I came from the HTML world many years ago - I am just in the habit of
copying/FTPing all my ASP.Net websites to the remote server

However, I have a friend who says that Publishing is the only way to go and
it's the 'MS' way to do it

I've had nothing but trouble trying to do this, many times, with different
errors popping up, either in publishing, building before publishing, or
running after publishing...

What are any pros and cons either way?
Oct 31 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Publishing precompiles the pages. You can still xcopy or FTP the resulting
bits. If you "publish", you will get rid of all source files, which is a
wise maneuver.

Build >Publish
Choose directory locally
FTP or copy from that directory to live server

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*************************************************
Think outside of the box!
*************************************************
"Elmo Watson" <sp*****@yahoo.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
Since I came from the HTML world many years ago - I am just in the habit
of
copying/FTPing all my ASP.Net websites to the remote server

However, I have a friend who says that Publishing is the only way to go
and
it's the 'MS' way to do it

I've had nothing but trouble trying to do this, many times, with different
errors popping up, either in publishing, building before publishing, or
running after publishing...

What are any pros and cons either way?


Nov 1 '06 #2

P: n/a
We're talking about a secured, shared hosting environment here, so - - -
Just curious - why is it a wise maneuver, to remove the source code?

"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMwrote in
message news:%2****************@TK2MSFTNGP04.phx.gbl...
Publishing precompiles the pages. You can still xcopy or FTP the resulting
bits. If you "publish", you will get rid of all source files, which is a
wise maneuver.

Build >Publish
Choose directory locally
FTP or copy from that directory to live server

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*************************************************
Think outside of the box!
*************************************************
"Elmo Watson" <sp*****@yahoo.comwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
Since I came from the HTML world many years ago - I am just in the habit
of
copying/FTPing all my ASP.Net websites to the remote server

However, I have a friend who says that Publishing is the only way to go
and
it's the 'MS' way to do it

I've had nothing but trouble trying to do this, many times, with
different
errors popping up, either in publishing, building before publishing, or
running after publishing...

What are any pros and cons either way?


Nov 1 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.