1. The website in the root folder works fine on the DASP server. 2. I have a subdirectory under the root (Util), on the DASP server, where I have published an (.asmx) web service. 3. The subdirectory (Util) containing the web service has been setup as a web application using the DASP web application tool. 4. This .asmx web service has been tested thoroughly locally on my machine and it works fine. When I try to test the published web service in a browser (http://www.mywebsite.com/Util/FileServer.asmx), or add the web service as a service ref, I get an error shown below. "RiffRecorder" is a namespace used only in the root web app. I have tried precompiling the root web app, and then uploading it, but the same thing happens. I can't understand why I get a compiler error complaining it can't find the namespace of the root web app. The root web app is not a .dll, so I can't imagine how I would reference it. Just using a namespace of the same name doesn't work. Any suggestions would be appreciated. Thanks, Ed -------------------------------------- Server Error in '/Util' Application. 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 'RiffRecorder' could not be found (are you missing a using directive or an assembly reference?) Source Error: Line 134: } Line 135: Line 136: public virtual RiffRecorder.BLL.Newsletters.SubscriptionType Newsletter { Line 137: get { Line 138: return ((RiffRecorder.BLL.Newsletters.SubscriptionType)(this.GetPropertyValue("Newsletter"))); Source File: c:\WINDOWS\microsoft.net\Framework\v2.0.50727\Temporary ASP.NET Files\util\224a30d9\c60cd321\App_Code.ip8bidla.0.cs Line: 136
This is caused by web.config inheritance. The sub folder web application where the web service resides is currently inheriting everything declared in the root web.config including type declarations. This is the default behavior but it can be overridden quite easily; have a search in this forum for 'inheritInChildApplications' and also take a look at these: http://www.aspdotnetfaq.com/Faq/how...ld-applications-in-subfolders-in-asp-net.aspx http://stackoverflow.com/questions/...d-web-application-using-inheritinchildapplica This question does come up quite often around here and I don't think there is a DASP knowledgebase article about it or a sticky post in the forum..hint hint.
Hi Joe: Thank you for responding and for the article links. You nailed the problem. I was eventually able to get my web service responding. I had one problem surrounding my <system.web> tags with: <location path="." inheritInChildApplications="false"> I was getting a squiggly red line message "inheritInChildApplications is not declared" in the VS2008 editor, until I found this article, which revealed something I broke earlier. http://www.commonwealthprosthodonti...=24&t=Webconfig-inheritInChildApplications-is where she states: "Simple, the inheritInChildApplication attribute is a .NET 2.0 addition to the web.config definition. Added this declaration to the configuration node at the top of the XML file: <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> No more squiggly red line." I normally have this in my web.config. I may taken it out when I upgraded my app from 2.0 to 3.5, thinking it might be a problem. The old "Don't fix it if....". Thanks again, Ed
Hi Ed, good job. The red squiggly thing has been discussed and answered in these forums before. It looks like you found the same solution I mentioned last time ;-)
