Last post May 08, 2012 05:29 PM by aabruzzese
May 03, 2012 04:39 PM|aabruzzese|LINK
I am trying to understand what the issue is here:
1... I copy a site to a remote server under a standard subdirectory
When I try this approach I get a namespace not found for the Class that I compiled in a C# project under my
VS2008 WebSiteSolution. The dll file is under the BIN directory and I added a reference to it before building
2... I did a Deploy instead and the codebehind files are all added to a dll file on the Remote Server under the BIN
When I try this approach I still get an error:
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_tgy5kzff'. Make sure that it is compiled before accessing the page.
Line 1: <%@ page language="C#" autoeventwireup="true" inherits="MyPageClass, App_Web_tgy5kzff" %> Line 2: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
Line 3: <html>
App_Web_tgy5kzff I am going to guess is the dll file that contains all the codebehind classes for the entire website.
And yes the file is physically present on the webserver itself, also keep in mind that I cannot do anything beyond simply copying the files onto the server, I cannot even copy the web.config file so the directory I create has everything minus the web.config
file which was
only for the database connection string.
So what am I doing wrong here?
May 07, 2012 11:29 AM|Dino He - MSFT|LINK
You can refer to this discussion:
Hope it helpful.
May 08, 2012 05:29 PM|aabruzzese|LINK
In this instance I am out of luck really, I cannot do anything beyond create a directory and drop the files in, cannot go to IIS manager or add a web.config so basically it will be all from codebehind using anything but a standard approach.
So all I am doing is writing all the code in each seperate codebehind file, I cannot think of any other way to get around it for now.
Thanks for the info though.