I apologize - I am new to .NET. I am trying to navigate my way through ALL these directories and am getting lost. Is this some standard build process or what? Where do I go for the actual source code? It appears as if it is in TBH_Web, but what is TBH_Setup, TBH_Deploy, TBH_CustomEvents? I see there is a .SLN file under the TheBeerHouse subdir as well. Can someone help me understand all of this structure?

If the TBH_Web is correct, what do I do with it from there? Just setup a vdir from there for IIS or what?

DB? I see there is an included ASPNETDB but I am to make the other objects?

Appreciate any assistance!

Thanks,

Bob

OK, I answered a couple of my questions. Problem was, I downloaded the updated C# version straight from the author's site which is a different dir structure than off the Wrox site. I then discovered the VB version from the Wrox site and started messing with version last night.

ONE THING TO NOTE: I still had not downloaded the original C# version from the Wrox site until just now. The book really does not go through how to set this up in any one place. However, after reviewing the Wrox C# example, it includes a Readme.txt file that certainly explains more of this to me.

However, can someone still explain to me the dir structure of _Setup, _Deploy, _CustomEvents?

Thanks,

Bob

Your questions are answered in the book, but briefly TBH_Web is the website, TBH_CustomEvents is a precompiled project used by the website to act as a provider in logging exception events to the database, TBH_Setup is used to compile an installer and finally TBH_Deploy is meant to aid in setting up the website for deployment.

If you are new to .NET, I strongly urge you to read a tutorial on the basics. This book is meant to be read by someone who is at the intermediate level and would like to know how to get from point a to point b. It assumes that you know something about programming in .NET and can manage code. The first three chapters do hold your hand and help you with the initial structure, but beginning in chapter 4 you're on your own and only new material is presented.

Visual Studio 2005 doesn't require a virtual directory in IIS.

Thanks for the reply - much appreciated. Maybe I should clarify, new to 2.0. Been through all the basics, just trying to apply them now. :)

About the vdir, VS2005 does not require it, but should not matter if it has it or not, correct? As I understand it, while within VS2005 - it will push it to the built-in web server, but you should also be able to hit it from IIS (I am using 5.1 under XP).

So here is where I am at. I think where my original problem came into play is that I opened this as a Web Site and not through the solution file. I was getting all sorts of compile errors under the VB version when trying to run it. I deleted everything, unzipped it again and opened the solution file and it actually runs now.

:) !!!!

>while within VS2005 - it will push it to the built-in web server, but you should also be able to hit it from IIS (I am using 5.1 under XP).

The word "push" probably isn't good in this context. The built-in webserver merely displays pages based on their current folder, and their is no deployment or copying that takes place.

You can view the pages in IIS if you use the built-in deployment wizard to deploy the files to IIS. Or, you can set up a project to live in a virtual directory just as it would in 2003, and no deployment would be needed. Pressing F5 would bring it up using IIS in that case. The key is the HTTP vs NT Filesystem that you choose when creating the project.

Eric