Wrox Programmer Forums
| Search | Today's Posts | Mark Forums Read
BOOK: ASP.NET Website Programming Problem-Design-Solution
This is the forum to discuss the Wrox book ASP.NET Website Programming: Problem - Design - Solution, Visual Basic .NET Edition by Marco Bellinaso, Kevin Hoffman; ISBN: 9780764543869
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: ASP.NET Website Programming Problem-Design-Solution section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
  #1 (permalink)  
Old June 18th, 2003, 10:45 PM
Registered User
 
Join Date: Jun 2003
Location: , , .
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default deployment chapter hard to follow

I would like a complete copy of the solution built on another machine. Apparently deployment projects are "easy", but I can't see how. The last chapter opens a new deployment project/solution and suddenly a screenshot shows directories from ThePhile project. How did they get there? The book talks of dragging and dropping and I can see that directories can be dragged and dropped from Explorer. Is this what he meant? Do you have to manually drag all the dll's into the bin folder? The talk of source/without source is not explained. Does without source, mean manually delete the .vb code behind classes? How do you create the msi files? None of this seems very automatic or easy to me.
It seems to me preferrable just to xcopy the whole thing. It's a pity that after all the careful description in previous chapters, comes a final chapter that explains virtually nothing.
  #2 (permalink)  
Old June 18th, 2003, 11:57 PM
Authorized User
 
Join Date: Jun 2003
Location: Bolingbrook, IL, USA.
Posts: 17
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi robert -

As far "installing" a running copy of the site, in theory it's quite simple: you literally duplicate the site structure in an appropriate directory and set it up in IIS so it's recognized as a "Web Application." Of course, you might want to omit files specifically for development, such as .csproj and .sln files (and there's no need to copy the /obj directories either).

Disclaimer: I didn't actually get as far as testing ThePhile, but I am extrapolating, based on my own experience adapting the core structure for my own in-progress site.

If you set it up like they did - there is one so-called "Web Project" called ThePhile and something like 19 local projects - then I think you will get a cleaner setup where every time you compile, VS.NET will copy the required DLLs to the /bin folder right off of the site's root folder. You don't ever have to worry about copying things left and right - when you deploy the site, along with copying all the files and folders of the project (as described above), you just copy over to the /bin directory on the live server all the DLLs that were collected there locally.

Stupidly enough, or perhaps I'm just that impatient, I didn't have just one Web Project, but instead developed the site live, so that after every compile, the site is immediately updated... it's always live. A main drawback of this (other than obviously if you break the latest build, anyone visiting will be affected right away), is that the DLL situation is a bit cleaner, with sub-Web Projects such as the News Module having their own local /bin directory. At the end of the day, however, if you keep your naming neat, VS.NET will still keep track of everything and copy everything in the correct places. I had -one- exception to this: it's on another thread in this board.

I don't know if this was helpful, but I hope you get some ideas -
Allen

mencher cat, mencher cat. boo. cattydear. what a lovely!
  #3 (permalink)  
Old June 19th, 2003, 12:12 AM
Registered User
 
Join Date: Jun 2003
Location: , , .
Posts: 6
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Allen,
Thanks for the reply. Creating a web application in IIS on a different server and copying the whole solution directory (perhaps deleting project and sln files), is something I can already do. My problem is doing that same job via a deployment project within vs.net. Have you tried that? Questions:
1. how do you "drag and drop" the directories? Is it done from Explorer to vs.net?
2. are you supposed to manually drag the dll files into the bin directory using the same technique?
3. is removing source files (code behind .vb files?) also a manual process?
4. is there any way of automating this stuff?
5. how do you produce an msi file?
I must be missing something, because it doesn't seem so magnificently easy to me.
  #4 (permalink)  
Old June 20th, 2003, 12:22 PM
Authorized User
 
Join Date: Jun 2003
Location: Bolingbrook, IL, USA.
Posts: 17
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Robert -

-My problem is doing that same job via a deployment project within vs.net. Have you tried that?

Hmm. I must say I haven't. I've been "cheating" you see, by developing the site "live." It's a personal site and I'm running my own server, so I was able to do that. Not good practice, I know, but hey. :D But now you've gotten me interested in finding out about this deployment project.

Allen


-----
mencher cat, mencher cat. boo. cattydear. what a lovely!


Similar Threads
Thread Thread Starter Forum Replies Last Post
Chapter 2 Unable to follow instructions GarethHowell BOOK: Professional SharePoint 2007 Development ISBN: 978-0-470-11756-9 4 July 9th, 2008 03:49 AM
Book: Full Of Errors And Hard To Follow SonnyG BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 4 May 27th, 2008 12:37 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.