.designer.cs doesn't work properly with nested web application projects - by John Culviner1

Status : 


Sign in
to vote
ID 544948 Comments
Status Active Workarounds
Type Bug Repros 4
Opened 3/26/2010 8:49:40 AM
Access Restriction Public


My organization used nested web application projects (WAP) in VS2005 and it worked just fine for the purpose of sharing common components across multiple WAP as well as having all the WAPs share the same web.config (and the same session state) that is located in the "Root" WAP. Now that we have upgraded to VS2010 RC the same user controls and masterpages do not work properly with this setup.

*Root Application*
C:\WebApplication\SharedMasterPage.master //this contains a method SetText()
C:\WebApplication\SharedUserControl.ascx     //this contains a method SetText()
C:\WebApplication\RootPage.aspx   //Uses the masterpage's and usercontrol's SetText()
C:\WebApplication\WebApplication.csproj   //the root web project's project file
C:\WebApplication\web.config //shared by both web application projects

*Nested Application*
C:\WebApplication\NestedWebApplication\NestedWebApplication.csproj  \\the project file for the nested web application project.
//this page uses the masterpage and usercontrol from the root WAP and tries to call SetText() but cannot due to it not being declared properly in it's designer.cs file.
Sign in to post a comment.
Posted by Microsoft on 9/29/2010 at 8:28 AM
Hi, thanks a lot for your feedback we really appreciate it. This was an issue with the RC build of Visual Studio that is now fixed in the final version. Can you please try with that version? If you have any issues with the release version then please follow these steps:
1) Delete the .designer.cs files
2) Right-click on the web project and select "Convert to Web Application" to regenerate those files

For now I will close this issue, but if you are still having issues please reactivate it.

Sayed Ibrahim Hashimi | http:\\sedodream.com
Posted by Microsoft on 3/29/2010 at 12:40 AM
Thank you for reporting the issue.
We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.These specialized experts will follow-up with your issue.
Posted by Microsoft on 3/27/2010 at 4:08 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)