Hi Jeff, This solution is just what I have been searching for, except… I get the following error:
Parser Error Message: Access is denied: ‘adminorders’.
Source Error:
Line 1: %@ Assembly Name=“adminorders” %
Line 2: %@ Page Language=“vb” AutoEventWireup=“false” Codebehind=“test.aspx.vb” Inherits=“adminorders.test”%
Line 3: !DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”
ASP.Net - “LOG: Policy not being applied to reference at this time”
Potential Causes/Solutions for this issue I’ve seen online:
web server runs out of space – free up disk space
aspnet worker process is messed up – kill aspnet worker process (development environment obviously)
Indexing Service is running (and locking files) – disable it
assemblies are in bin that aren’t supposed to be (ref), and the machine.config has an add assembly="*" (all) – remove unreferenced/unnecessary DLLs from the bin folder.
The last bullet is what I ran into - I removed the DLLs (named “Copy of dllNameHere.dll”) from the bin folder and voila! my web service worked. I never saw this fix anywhere, so I’m posting it. Hope it helps.
I’m confused: why not simply create a virtual directory/application within that website (at IIS) instead? That’s a one-time setup also. Why mess with web.config changes and changes in that third-party’s aspx files (isn’t that riskier)?
If this was about development setup within Visual Studio, there are other ways to keep both web projects running without having one a child of another in the VS solution tree, while still having them accessed with the same URLs as if one IS a child of another.