Compilation Error - inheriting the profile provider from YAF web.config

Welcome Guest! To enable all features please Login or Register

Mick
54.2% (Neutral)
YAF Forumling Topic Starter

16 years ago

YAF 1.9.3 on ASP.Net 3.5 IIS 6.0

I'm getting the error below on all ASP.Net apps in virtual IIS application ROOT sub directories. Seems to be inheriting the profile provider from YAF.

Appreciate any ideas to resolve - Thanks guys!

-----------------------------

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS0246: The type or namespace name 'YAF' could not be found (are you missing a using directive or an assembly reference?)

Source Error:

[No relevant source lines]

Source File: d:\hosting\healthlink\web.config Line: 168

Line 162:

Line 163:

Line 164:

Line 165:

Line 166:

Line 167:

Line 168:

Line 169:

Line 170:

Line 171:

Line 172:

Line 173:

Wanna join the discussion?! Login to your YAF.NET Support Forum forum account or Register a new forum account

Sponsor

Jaben
100% (Exalted)
YAF Developer

16 years ago

The Yaf*.bin files are not in your application root/bin directory.

Mick
54.2% (Neutral)
YAF Forumling Topic Starter

16 years ago

The Yaf*.bin files are not in your application root/bin directory.

Jaben wrote:

OK great - Thanks Jaben - copying the dlls seems to work.

Just to be clear, these are totally separate and independent web sites unrelated to YAF in their own IIS root sub-directory. Will all ASP.net sites running on this hosted account in an IIS root sub-directory inherit from the YAF providers and therefore have to contain the YAF dlls even though they are not connected to the YAF application? If so, can you help me understand why that is? Would it be the same situation with an earlier version of YAF like 1.9.1.8?

Thanks again.

Mick
54.2% (Neutral)
YAF Forumling Topic Starter

16 years ago

I have several ASP.NET web sites as IIS virtual directory applications under my main web site. After integrating YAF with the main site, I began having some problems with web.config inheritance on the virtual sub directories. Even though physically separate and set as root in IIS, just being in a virtual directory located within another webapp resulted in many of the settings being inherited and messing up my other ASP.NET webapps.

I found the method to resolve these issues on a couple of very helpful blog entries below that others may find useful. The key is adding to the right area my main web application’s web.config file.

Another victory and mystery solved!

IIS/ASP.NET Settings and Virtual Directory Inheritance by Rick Strahl

Prevent ASP.NET web.config inheritance, and inheritInChildApplications attribute by Jerome Laban

Important Information: