ASP.NET error, publish with VS 2005

R

Ryan

I don't get what the problem is here. I have tried everything for 5 hours
straight and have not had any luck. The project is being compiled, the .dll
does exist in the /bin folder of the web server. The .NET framework is the
same (2.0) on the web server as on my PC. I'm just trying to create and
publish a simple .ASPX page (right now all it contains is text "This is a
test"). The Web Server is IIS 6.0. The folder is a virtual directory. How
do I get this to work??? Please help! Thanks!

Ryan

-----------------------------------------------------------------------------------------------------------------------------------------------------
Server Error in '/' 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 the assembly 'App_Web_j5_yopnt'. Make
sure that it is compiled before accessing the page.

Source Error:


Line 1: <%@ page language="VB" autoeventwireup="false" inherits="_Default,
App_Web_j5_yopnt" %>
Line 2:
Line 3: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


Source File: /Ticket/Default.aspx Line: 1
 
S

Steven Cheng[MSFT]

Hello Ryan,

From your description, you're encountering some assembly loading error
after deploy a certain ASP.NET 2.0 web application from development machine
to a server machine, correct?

According to the detailed error message you pasted below

======================
Parser Error Message: Could not load the assembly 'App_Web_j5_yopnt'. Make
sure that it is compiled before accessing the page.

Source Error:


Line 1: <%@ page language="VB" autoeventwireup="false" inherits="_Default,
App_Web_j5_yopnt" %>
Line 2:
Line 3: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
=======================

The runtime can not locate the "App_Web_j5_yopnt.dll" assembly, and since
the @Page directive also reference this assembly, I think you have perform
precompilation(publish the website ) before deploy it , correct?

if this is the case, after you performing the precompilation(publish web
site), the target directory's "bin" folder should contain those precompiled
assemblies(such as "App_Web_j5_yopnt.dll") together with some *.compiled
files. Be careful that you should use the "target" or "output" directory
rather than your origional web site's directory after you perform the
precompilation because only those directories contains the correct
content/assemblies for deployment:

#Precompilation In ASP.NET 2.0
http://www.odetocode.com/Articles/417.aspx

#How to: Precompile ASP.NET Web Sites
http://msdn2.microsoft.com/en-us/library/ms227972.aspx

#Managing ASP.NET Precompiled Output for Deployment Using the
aspnet_merge.exe Command
http://msdn2.microsoft.com/en-us/library/aa479044.aspx

Please feel free to let me know if you have anything unclear above or if
there is any other questions here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================



This posting is provided "AS IS" with no warranties, and confers no rights.
 
R

Ryan

Hi Steven,
Correct I am encountering the error after deployment from the dev machine to
the server. Looking at the /bin folder the only thing in it is the
App_Web...dll file, looks like I'm missing the .compile files. Will look
over your links to see if I can find the solution.

Thanks,
Ryan
 
R

Ryan

Ok.. I really didn't want a pre-compiled page, so I was going about this
wrong. I changed my process so I did the build on the dev computer and then
instead of "publishing" which generates the pre-compiled files, I just
FTP'ed the entire build folder. This seems to work.

Thanks,
Ryan
 
S

Steven Cheng[MSFT]

Thanks for your reply Ryan,

Yes, for precompiled application, you need to copy both the precompiled
assemblies(dll) and the .compiled files. If you do not want precompile,
you can simply copy all the original content in your web application root
folder to the target server's virtual directory without any change. The
Visual Studio's "Copy Web Site" function can also help to do this.

BTW, if you will perform precompilation or wonder more information on this,
here are some useful reference:

http://msdn2.microsoft.com/en-us/library/399f057w.aspx

http://odetocode.com/Articles/417.aspx

http://www.west-wind.com/WebLog/posts/2128.aspx

If you have any further questions or concerns, please feel free to let me
know.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,770
Messages
2,569,583
Members
45,075
Latest member
MakersCBDBloodSupport

Latest Threads

Top