 |
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
|
|
|
|

June 19th, 2003, 11:24 AM
|
Authorized User
|
|
Join Date: Jun 2003
Posts: 17
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Error on local load of downloaded app
Hello,
I downloaded the source Installed it on localhost/ThePhile. And i runned it without SQL, but I get this, which is not SQL related. In IIS I created the app. Being a newbie, I dont understand why it doesn't inherit properly?
Note: I noticed that the folder /ThePhile contains NO .dll. Is this normal?
Here's the error:
Server Error in '/ThePhile' Application.
--------------------------------------------------------------------------------
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'Wrox.ThePhile.Web.Global'.
Source Error:
Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="Wrox.ThePhile.Web.Global" %>
Source File: C:\Inetpub\wwwroot\monuc\ThePhile\global.asax Line: 1
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.0.3705.0; ASP.NET Version:1.0.3705.0
Any idea?
Kim Gjerstad
__________________
Kim Gjerstad
|

June 19th, 2003, 03:02 PM
|
Authorized User
|
|
Join Date: Jun 2003
Posts: 17
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Hi Kim -
>> Note: I noticed that the folder /ThePhile contains NO .dll. Is this normal?
Yes, they have deliberately left out the assemblies.
Before being able to check out ThePhile, you will have to compile the entire solution (in VS.NET, command line, however you prefer), then copy the resulting DLLs to the /bin folder of ThePhile, as installed on your Web server. The parser error you're getting is essentially saying it can't find the DLLs it's expecting to use.
Hope this helps,
Allen
-----
mencher cat, mencher cat. boo. cattydear. what a lovely!
|

June 20th, 2003, 03:59 AM
|
Authorized User
|
|
Join Date: Jun 2003
Posts: 17
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Allen,
I got myself a little smarter today because of you. Since I'm new to VS.net, I'd like to ask a few more questions that could help me out here:
-What is the difference between Building and Rebuilding.
-When you Build, that means compiling the DLL, right?
-
What is the difference between Debug and Release in the Config Manager of the menu Build?
If I wish to deploy wouldn't it make sense that everything is in the same folder?
Thanks for your contributions ahead of time!
Kim Gjerstad
|

June 20th, 2003, 12:15 PM
|
Authorized User
|
|
Join Date: Jun 2003
Posts: 17
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Hi Kim -
Glad to be of help to a fellow seeker...
-Difference between building and rebuilding
Rebuilding causes VS.NET to compile and link every single file, depending on what you try to execute it on: For example, if you choose Rebuild for the solution, then your *entire* site will be rebuilt - this is useful if you need to make sure that all files are up to date. Choosing Rebuild at the project level will just rebuild that project. On the other hand, Building causes VS.NET to only compile and link source files that have *changed.* As you might imagine, this can be quite a bit quicker.
-Difference between Debug and Release
I'm not sure if this has changed much in VS.NET (or in .NET in general) but in previous versions, essentially, compiling and linking in Debug mode tells VS.NET to leave bits of code (debugging symbols) in the assemblies. This "extra" information allows you to get more detailed information regarding how your program is running, which naturally useful when you are trying to zero in on the cause of a problem. Also, the Debug build will be non-optimized; essentially, what this will mean for you is that your program will be larger and run a bit slower in Debug mode vs. Release mode.
-If I wish to deploy wouldn't it make sense that everything is in the same folder?
Actually, everything is in the same folder: there are just sub-folders holding various pieces (Modules) of the web application. If you mean, every single file should be in one folder, I suppose you could do that, but it would be a pain to organize and keep track of! Also, what if you wanted a different Default.aspx for various modules? If would be impossible without having sub-folders.
Ok, hope this helps! Later,
Allen
-----
mencher cat, mencher cat. boo. cattydear. what a lovely!
|

June 21st, 2003, 10:36 AM
|
Authorized User
|
|
Join Date: Jun 2003
Posts: 17
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Allen, thx again. The same folder issue was actually a left over after I edited my message.
I'm progressing here, although learning C# AND VS.net wiht no help at hand here in the Congo is not easy. Loosing patience, but I've been thru the learning drill b4: patience is key!
So here is my next question:
-The function of a .snk is to make sure nobody else can compile my code?
Kim Gjerstad
|
|
 |