Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to place aspx-files in seperate Web Application Projects in one solution?
    text
    copied!<p>We have been building ASP.Net websites for many years. During this time we gathered a lot of knowledge of ASP.Net. We know what to use, a what not. One problem is still, persistently, bugging us. I hope to solve this for once and for all.</p> <p>We have a fairly large solution with lots of aspx-files. All aspx-files reside in one Web Application Project. This single big WAP needs to be split in multiple smaller projects. The exact reasoning is beside the point, please believe me ;-).</p> <p>There are a number of ways to accomplish this, but I am still unsure what the best way would be. We use ASP.Net 4.0 and Visual Studio 2010 Premium.</p> <p>Any advice is greatly appreciated.</p> <p><strong>This is our current work-around (which we do not like)</strong></p> <ol> <li>Create a WAP (Runner).</li> <li>Create a second WAP (ProjectA)</li> <li>Create a third WAP (ProjectB)</li> <li>Delete the web.config's in ProjectA and ProjectB</li> <li>Create a simple aspx-file in Runner, ProjectA and ProjectB with a hello world message</li> <li>Remove ProjectA and ProjectB</li> <li>Go to Windows Explorer</li> <li>Move the folders ProjectA and ProjectB inside the folder Runner</li> <li>Go back to Visual Studio</li> <li>Add Existing Project to solution (ProjectA and ProjectB)</li> <li>Hit F5</li> <li>Navigate to <a href="http://localhost:4867/WebForm1.aspx" rel="nofollow">http://localhost:4867/WebForm1.aspx</a></li> <li>Navigate to <a href="http://localhost:4867/ProjectA/WebForm1.aspx" rel="nofollow">http://localhost:4867/ProjectA/WebForm1.aspx</a></li> <li>Navigate to <a href="http://localhost:4867/ProjectB/WebForm1.aspx" rel="nofollow">http://localhost:4867/ProjectB/WebForm1.aspx</a></li> </ol> <p>Tada! The above works, but it feels like a hack and it smells awful. Is there a better way?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload