Last post Oct 23, 2007 05:05 PM by hongping
Oct 23, 2007 01:34 PM|rjmorton|LINK
Does anyone have any experience in using the Web Deployment Project pieces to deploy Web Application style projects (rather than the web site projects model)?
We have a rather larger eCommerce site that uses WAP model (it was originally a website model, but we ran into so many problems with compile times, temp .dll file lockups at compile etc that we moved it to WAP a long time ago).
What's strange is that the project compiles fine normally when we're not using the Web Deployment Project and everything is fine. However, the second we hook the WDP stuff up, we're getting allsorts of compile errors that we shouldn't be getting including:
'Error 212 Circular file references are not allowed. /www_4imprint_com_WAP.csproj/_ControlsLibrary/_UserControls/Products/Common/ProdList.ascx'
'Error 218 The virtual path '/_ControlsLibrary/_UserControls/Common/Search/ucQuikSearch.ascx' maps to another application, which is not allowed. /www_4imprint_com_WAP.csproj/Admin/_ControlsLibrary/_Common/ucHeaderAdmin.ascx'
We're thinking that the WDP stuff is under the false impression that our eCommerce site is a Web Site project and not a Web Application project. These are exactly the types of errors you get with web site model sites, but we shouldn't be getting them in
our web application project model app. All our controls, classes etc are correctly namespaced and once again, the project always compiles fine when WDP isn't part of the equation.
We've tried messing around with the 'output assemblies' settings in the Deployment Project options - setting single assembly, assembly per folder and assemblies for each page, but the darned thing never works properly.
Does anyone have any ideas on how to get this all working with Web Application Project apps? Most of the articles online I've found don't specifically deal with WAP.
Oct 23, 2007 05:05 PM|hongping|LINK
One thing you might try is to use the command line version of the tools to see if they provide any more information. Web Deployment Project uses aspnet_compiler and aspnet_merge. Both tools should work with both WAP and Web sites.
aspnet_compiler -f -c -d -v MySite -p MySite output_folder
aspnet_merge -errorstack -o MySite_deploy output_folder
You mentioned that the error only appears after adding WDP, so the error might be from aspnet_merge. The -errorstack flag would provide a stack trace which might help identify where the failure came from.