By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,179 Members | 1,102 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,179 IT Pros & Developers. It's quick & easy.

need diagnosis: problem loading assemblies

P: n/a
I have made a web application that is giving me an error in loading
assemblies. It reports file not found (error message below). I know I have
the .dll in the .bin directory for the 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 file or assembly 'epicFlashControl' or
one of its dependencies. The system cannot find the file specified.

If I can identify the simple cause for this, then I'm done: feel free to
suggest the solution for dummies because I may have made a newbie error
here. Are there any files that should reference the load locations of files
like "epicFlashControl" (i.e. is it possible I inadvertantly tore something
necessary out of web.config?)

I notice a couple of other things that may help us get to the bottom of
this. The stucture of the URL that throws this error is as follows:

http://machinename.subdomain.domain...._overview.aspx

"appRootDir" is defined as an application in IIS. I have a custom domain
name set up that points to appRootDir via IIS Host Header mapping.
Interestingly the following URL will load the page, though other things
break due to the alteration of the directory structure:

http://www.customdomainname.org/dir2..._overview.aspx

The third data point is that if I go into IIS, expand "Default Web Site",
find the directory that is appRootDir, and enable it as an application, then
my application WILL load the assembly using the first URL I mentioned, and
my file references work OK. Unfortunately, nesting/duplicating an app in
this way (remember, appRootDir is also defined as a standalone app) appears
to break other things.

There's something I'm missing here, and a few things I need to learn,
obviously. Can anyone help?

Thanks,
-KF
Aug 1 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi,

To use local compiled code, you must include a \Bin directory directly
beneath your application root. And you must create application in IIS for
the parent folder of \Bin to make it an application root.

#ASP.NET Web Site Layout
http://msdn2.microsoft.com/en-us/library/ex526337.aspx

#Creating a Directory Structure for an ASP.NET Application
http://www.microsoft.com/technet/pro.../Library/IIS/2
3b7ba37-f5be-420f-95b8-8f9dd1015174.mspx?mfr=true

Hope this helps. Please feel free to post here if anything is unclear.
Sincerely,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.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/subscripti...t/default.aspx.
==================================================

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

Aug 2 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.