J
Jon Maz
Hi,
Although I have placed my "wec.dll" in the correct folder
("wwwroot\wec\bin"), and have configured this "wec" folder in IIS as an
application, when an aspx page is hit, I get a "could not load type wec"
error. This error disappears if I cut-and-paste this wwwroot\wec\bin
directory into the wwwroot folder.
Thus the problem is that IIS is ignoring the fact that the sub-folder has
been configured as an application, and is refusing to look for dll's in the
sub-folder's bin directory. Does anyone know what might be causing this?
I'm now using Windows XP Pro, and never had this issue with W2000 Advanced
Server (on which this application was previously developed).
TIA,
JON
----------------------------------------------------------------------------
------------------------------------
FURTHER DETAILS
If I add the following to the wwwroot\wec\web.config:
<system.web>
<configuration>
<compilation>
<assemblies>
<add assembly="wec" />
</assemblies>
</compilation>
</configuration>
</system.web>
....I get the following error message, which simply confirms that for some
reason Dotnet is trying to find the dll in the 'Temporary ASP.NET Files'
folder, instead of in wwwroot\wec\bin:
CONFIGURATION ERROR
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: File or assembly name wec, or one of its dependencies,
was not found.
=== Pre-bind state information ===
LOG: DisplayName = wec
(Partial)
LOG: Appbase = file:///c:/inetpub/wwwroot
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===
LOG: Policy not being applied to reference at this time (private, custom,
partial, or location-based assembly bind).
LOG: Post-policy reference: wec
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET
Files/root/2135a508/8d69a834/wec.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET
Files/root/2135a508/8d69a834/wec/wec.DLL.
LOG: Attempting download of new URL file:///c:/inetpub/wwwroot/bin/wec.DLL.
LOG: Attempting download of new URL
file:///c:/inetpub/wwwroot/bin/wec/wec.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET
Files/root/2135a508/8d69a834/wec.EXE.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET
Files/root/2135a508/8d69a834/wec/wec.EXE.
LOG: Attempting download of new URL file:///c:/inetpub/wwwroot/bin/wec.EXE.
LOG: Attempting download of new URL
file:///c:/inetpub/wwwroot/bin/wec/wec.EXE.
Although I have placed my "wec.dll" in the correct folder
("wwwroot\wec\bin"), and have configured this "wec" folder in IIS as an
application, when an aspx page is hit, I get a "could not load type wec"
error. This error disappears if I cut-and-paste this wwwroot\wec\bin
directory into the wwwroot folder.
Thus the problem is that IIS is ignoring the fact that the sub-folder has
been configured as an application, and is refusing to look for dll's in the
sub-folder's bin directory. Does anyone know what might be causing this?
I'm now using Windows XP Pro, and never had this issue with W2000 Advanced
Server (on which this application was previously developed).
TIA,
JON
----------------------------------------------------------------------------
------------------------------------
FURTHER DETAILS
If I add the following to the wwwroot\wec\web.config:
<system.web>
<configuration>
<compilation>
<assemblies>
<add assembly="wec" />
</assemblies>
</compilation>
</configuration>
</system.web>
....I get the following error message, which simply confirms that for some
reason Dotnet is trying to find the dll in the 'Temporary ASP.NET Files'
folder, instead of in wwwroot\wec\bin:
CONFIGURATION ERROR
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: File or assembly name wec, or one of its dependencies,
was not found.
=== Pre-bind state information ===
LOG: DisplayName = wec
(Partial)
LOG: Appbase = file:///c:/inetpub/wwwroot
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===
LOG: Policy not being applied to reference at this time (private, custom,
partial, or location-based assembly bind).
LOG: Post-policy reference: wec
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET
Files/root/2135a508/8d69a834/wec.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET
Files/root/2135a508/8d69a834/wec/wec.DLL.
LOG: Attempting download of new URL file:///c:/inetpub/wwwroot/bin/wec.DLL.
LOG: Attempting download of new URL
file:///c:/inetpub/wwwroot/bin/wec/wec.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET
Files/root/2135a508/8d69a834/wec.EXE.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET
Files/root/2135a508/8d69a834/wec/wec.EXE.
LOG: Attempting download of new URL file:///c:/inetpub/wwwroot/bin/wec.EXE.
LOG: Attempting download of new URL
file:///c:/inetpub/wwwroot/bin/wec/wec.EXE.