What I want to do can't be that unusual. In my solution, I have a MVC3 project and a WebForms project. The MVC3 project is the meat & potatoes of the application- it's what the user will interact with. The 2nd project is going to be a shared "content delivery" project. It'll ultimately be shared by many projects. There is nothing in it that says it has to be WebForms, as it's meant to be static css/js/images.
On top of that, I'd like to use the built-in VS.NET development server.
I have tried a variety of things:
- Setting my MVC project as the start-up project with and without the "Always Start When Debugging" property set to true/false (RESULT: can't access the files in my /webforms project)
- Setting multiple start-up projects (RESULT: 2 instances of the development server run on different ports)
- Setting the WebForms project as a reference to my main MVC project(RESULT: can't access the files in my /webforms project)
- Setting the virtual path under Properties --> Build for my webform project (RESULT: can't access the files in my /webforms project)
My goal is to:
- Keep these as 2 separate projects
- When I run the MVC project, I can access the files in the other project as a virtual directory (e.g. /WebForms/images/whatever.png)
- Keep using the VS.NET development server
As I said - it doesn't seem like this should be that hard, but I'm pulling a big fat failure.
