p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

aspdotnet_website_programming thread: Deploying site: Copy Project 21 projects or one?


Message #1 by gjm@s... on Wed, 22 May 2002 21:35:50
On page 506 you suggest making a clean copy by using the Copy Project 
opton. Do all 21 projects need to be copied for the site to function?
Thanks,
Gary
Message #2 by "Mike Gale" <info@d...> on Thu, 23 May 2002 08:51:29 +1200
The book talks about copying a solution which is all the projects.  (I
have found that it works as expected in other solutions, but not this
one yet.  I'd suggest doing it to check.  It's only a few minutes work!)

Like the authors I give "only files needed" a heartfelt round of
applause.  This is really good functionality.

I haven't read the deployment part of the book but I have found three
versions of a site make for comfortable deployment.

1)  Development with all source

2)  Staging with only needed files (not publicly available)

3)  Live site

For any significant deploy I believe it's very important to run your QA
on the Staging site.  That way you get your checks (unit testing, does
obfuscation work?, valid html/XHTML, eyeballing, code inspection
(x/html), spelling, configuration switching across machines, cross
browser...) on a realistic version of your site.   It gives you much
more confidence than a "publish without checking" approach.

Mike Gale, Decision Engineering (NZ) Ltd.

Subject: [aspdotnet_website_programming] Deploying site: Copy Project 21
projects or one?

On page 506 you suggest making a clean copy by using the Copy Project 
opton. Do all 21 projects need to be copied for the site to function?
Thanks,
Gary

Message #3 by gjm@s... on Wed, 22 May 2002 22:36:54
After copying the startup project, I find that none of the other projects 
in the solution display the 'Copy Project' option in either the Solution 
Explorer tool bar, or the Project menu.

Now what?

While I've appreciated much of the book, it seems like a rather glaring 
deficiency to gloss over deployment in this way.  

  Return to Index