Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / May 2004

Tip: Looking for answers? Try searching our database.

Remote Administration

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Thom Little - 06 May 2004 04:52 GMT
I developed and run some ASP.NET applications on my local machine.  I have
IIS 5.0 available on two servers from two different ISPs.  I would like to
have the applications served from the two ISP controlled machines.  I have
FTP-access (only) to the two remote servers.

Simple .aspx applications execute (such as trace) but .aspx applications
with a .aspx.cs code behind file fail on the statement ...

<%@ Page language="c#" Codebehind="Sample.aspx.cs" AutoEventWireup="false"
Inherits="Sample.Sample" %>

... because it can not resolve the Sample.Sample

Any suggestions on how to proceed?
Is there documentation available on installing an application on a remote
ISP-controlled machine?

Signature

-- Thom Little -- www.tlaNET.net -- Thom Little Associates, Ltd.
--

Tian Min Huang - 07 May 2004 03:11 GMT
Hello Thom,

Thanks for your post. As I understand, the problem you are facing is that
your ASP .NET web pages with codebehind do not work after deploying to
remote web server. Please correct me if there is any misunderstanding.

As you know, ASP .NET application includes a project DLL if the code-behind
features of .asp files are used. This DLL together with other assemblies
are located in the bin folder underneath the virtual directory of the
application. Did you also copy them to your target machine? For simple Web
applications, it is often appropriate to XCOPY all the files of your ASP
.NET application to the target computer. Please refer to the following MSDN
article for detailed ASP .NET deployment information:

Deploying .NET Applications Lifecycle Guide
http://www.microsoft.com/italy/net/business/netarchitect/dotNET_application_
lifecycle_guide.pdf

Hope this helps.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Thom Little - 07 May 2004 04:31 GMT
Thank you for the response.

The problem I was having was that the /bin directory had to be in the root
of the website in order for the class resolution to occur.  In my case it
was not.  Simply creating a /bin in the root and moving the dll into it
resolved my problem.

My guess is that this is a "feature".

Signature

-- Thom Little -- www.tlaNET.net -- Thom Little Associates, Ltd.
--

> Hello Thom,
>
[quoted text clipped - 11 lines]
>
> Deploying .NET Applications Lifecycle Guide

http://www.microsoft.com/italy/net/business/netarchitect/dotNET_application_
> lifecycle_guide.pdf
>
[quoted text clipped - 8 lines]
> Get Secure! -- www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.