Wrox Programmer Forums
Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 2.0 > ASP.NET 2.0 Basics
|
ASP.NET 2.0 Basics If you are new to ASP or ASP.NET programming with version 2.0, this is the forum to begin asking questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Basics 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 9th, 2008, 05:19 PM
Friend of Wrox
 
Join Date: Mar 2007
Posts: 205
Thanks: 4
Thanked 0 Times in 0 Posts
Default [Resolved] Posting to Remote Site

I am doing a posting of a web project to a remote site. I have 7 pages. All pages work except for 2 pages that gives me errors, these pages has user controls like a button, gridview etc. Can anyone tell me what I am doing wrong?

Here is the error for one of the two pages:


Code:
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 the assembly 'App_Web_1dv5or5d'. Make sure that it is compiled before accessing the page.

Source Error: 


Line 1:  
Line 2:  <%@ page language="VB" masterpagefile="~/MasterPage.master" title="Untitled Page" autoeventwireup="true" inherits="Contact_aspx, App_Web_1dv5or5d" %>
Line 3:  
Line 4:  <asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
 

Source File: /Contact.aspx    Line: 2
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
 
Old March 10th, 2008, 09:27 AM
planoie's Avatar
Friend of Wrox
 
Join Date: Aug 2003
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

Line doesn't look right. I pretty sure you can not do what you are instructing it to do here. The class name "App_Web_1dv5or5d" is randomly generated by the ASP.NET runtime. It will change with each reset of the web application. I'm surprise this worked for you at all.

Can you explain what you are trying to accomplish with the inherits value of this page directive?

Something else doesn't look right as well... there is no "CodeFile" attribute. This is usually present and contains the file name of the code behind file that contains the class that the markup page inherits.

-Peter
peterlanoie.blog
 
Old March 10th, 2008, 12:11 PM
Friend of Wrox
 
Join Date: Mar 2007
Posts: 205
Thanks: 4
Thanked 0 Times in 0 Posts
Default

Got it working ... the assembly 'App_Web_1dv5or5d' was located in a \bin\bin folder on the remote site instead of the \bin folder, once moved to the \bin folder things worked .... thank you for your help .... to reply to the previous post from planoie, this is the correct line:

Code:
<%@ Page Language="VB" MasterPageFile="~/MasterPage.master" Title="Untitled Page" AutoEventWireup="true" CodeFile="Contact.aspx.vb" Inherits="Contact_aspx" %>







Similar Threads
Thread Thread Starter Forum Replies Last Post
"The remote name could not be resolved" teddyk ASP.NET 2.0 Basics 0 October 28th, 2008 12:49 AM
[RESOLVED] Remote Debugging Issue dparsons ASP.NET 1.0 and 1.1 Professional 1 March 19th, 2007 01:19 PM
remote name could not be resolved: '(localhost)' Tremmorkeep BOOK: ASP.NET 2.0 Website Programming Problem Design Solution ISBN: 978-0-7645-8464-0 2 June 30th, 2006 07:57 AM
Remote Site Set Up Anne Harrington Dreamweaver (all versions) 1 April 7th, 2005 04:25 PM
Accessing a remote web site Ray Pinnegar Access VBA 2 July 24th, 2003 08:34 PM





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