Virtual path maps to another application
First, I'm not sure if I am in the correct Forum please direct to proper forum if it is wrong.
I'm am getting the following error when I run my VS2019 WCF app. (Note it was originally written in VS2019)
[ArgumentException: The virtual path '/MyApp/MyService.svc' maps to another application, which is not allowed.]
System.Web.CachedPathData.GetVirtualPathData(VirtualPath virtualPath, Boolean permitPathsOutsideApp) +247
System.Web.HttpContext.GetFilePathData() +31
System.Web.HttpContext.GetConfigurationPathData() +27
System.Web.Configuration.RuntimeConfig.GetConfig(HttpContext context) +48
System.Web.Configuration.CustomErrorsSection.GetSettings(HttpContext context, Boolean canThrow) +42
System.Web.HttpResponse.ReportRuntimeError(Exception e, Boolean canThrow, Boolean localExecute) +103
System.Web.HttpContext.ReportRuntimeErrorIfExists(RequestNotificationStatus& status) +485
My Project file has the following in it;
<VisualStudio>
<FlavorProperties GUID="...">
<WebProjectProperties>
<UseIIS>True</UseIIS>
<AutoAssignPort>True</AutoAssignPort>
<DevelopmentServerPort>7821</DevelopmentServerPort>
<DevelopmentServerVPath>/</DevelopmentServerVPath>
<IISUrl>http://localhost:9630/WCF/MyService.svc/rest</IISUrl>
<OverrideIISAppRootUrl>True</OverrideIISAppRootUrl>
<IISAppRootUrl>http://localhost:9630/WCF/MyService.svc/rest</IISAppRootUrl>
<NTLMAuthentication>False</NTLMAuthentication>
<UseCustomServer>False</UseCustomServer>
<CustomServerUrl>
</CustomServerUrl>
<SaveServerSettingsInUserFile>False</SaveServerSettingsInUserFile>
<servers defaultServer="">
<server name="SelfHostServer" exePath="" cmdArgs="" url="http://localhost:9620/" workingDir="" />
</servers>
</WebProjectProperties>
</FlavorProperties>
</VisualStudio>
Now, the app was working before I upgraded to VS2019 16.11.35. Also, IIS 10 Express is installed. I am lost why this is happening now. Can anyone offer insights or solution to this issue?
Thank you!
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more