Wrox Programmer Forums
|
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
 
Old March 11th, 2004, 01:20 PM
Authorized User
 
Join Date: Jul 2003
Posts: 52
Thanks: 0
Thanked 0 Times in 0 Posts
Default WROX.WebModules namespace--Help??

I am coding my own app using thePhile as a blueprint. I have
one main question right now...
1. where is the namespace "WROX.WebModules" originated? I cannot
find a file/class that declares this namespace, so my own site has
a squiggly line under "Imports XXX.WebModules" in my "XXXPage.vb"
file (the same as "thePhilePage.vb" under "thePhile" project.)
I need to accomplish the declaration of the namespace so the squiggly
line goes away. I need to accomplish this step to learn what I am doing
wrong. On page 27 of the VB version, it shows the IIS directory tree
and says this is the result of converting the namespace hierarchy into
a directory tree. So I'm wondering if the namespace is created by virtue of
creating the directory tree?

R Corcoran, Jr.
__________________
Reid C.
 
Old March 17th, 2004, 01:00 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 917
Thanks: 0
Thanked 0 Times in 0 Posts
Default

The namespace has nothing to do with the directory tree, although I can understand why you would think that.

Your problem might be caused by the way you set up a virtual directory. You have to set up a virt dir called "ThePhileVB", and that will be the root dir of the app.

There are many, many places in the source code and .config files where they make this assumption about the virtual directory.

But I'm not saying it has anything to do directly with the namespace. It needs to have the right path in terms of the http protocol in order to find the right files. If the right files aren't found, then it won't find the namespace.

Eric
 
Old March 22nd, 2004, 02:51 PM
Authorized User
 
Join Date: Jul 2003
Posts: 52
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks, Eric...but I still have the problem...if you or
anyone can help me. In the "PhilePage.vb" file, there is the
declaration "Imports Wrox.WebModules". I am trying to find out
where they are importing this FROM...where is the file that
originally creates the namespace "Wrox.WebModules" so I can
mirror this in my project and then reference it.

Thx
Reid C.

R Corcoran, Jr.
 
Old March 23rd, 2004, 03:43 PM
Authorized User
 
Join Date: Jul 2003
Posts: 52
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Plz disregard above...I figured this out...did not have my root namespace
entered correctly in the "Core" project, so I could not see the namespace
in my version of the PhilePage.vb file.

R Corcoran, Jr.





Similar Threads
Thread Thread Starter Forum Replies Last Post
Thanks to some outstanding p2p.wrox.com Wrox.com jminatel Forum and Wrox.com Feedback 0 February 23rd, 2006 11:30 PM
HELP!! Reusing the Webmodules in a non web app madlo BOOK: ASP.NET Website Programming Problem-Design-Solution 7 February 20th, 2006 01:33 AM
'Wrox' in the namespace JsonTerre1 BOOK: ASP.NET Website Programming Problem-Design-Solution 1 November 1st, 2004 11:54 AM
WebModules.Accounts.Data error zamankazi BOOK: ASP.NET Website Programming Problem-Design-Solution 2 October 29th, 2004 09:56 AM
Wrox and Wrox.com FAQs (updated March 2, 2004) jminatel General Announcements 0 June 6th, 2003 09:23 AM





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