When we changed the Output Path in the project configuration we instructed the system to place the compiled output in the staging directory based on the current configuration.
- Chatting seks online in usa
- gucci mane mya dating
- Chat with horney girls no sign up or payment
- when updating security for a remote procedure call rpc
- Chathurika peiris hard xxx videos
- eric r osar dating
(hopefully not in the future) “Enabling MVC5 intellisense in a Class Library Project.” Thetoeb, 5 January 2014. In any event, all of the discussion related to the problem that I found online pointed to, essentially, the same answer. Not content with what I found online I tried a few approaches of my own.
The only way to get the Intellisense support back is set the output path back to the bin directory. First, I tried adding MSBuild .targets files to the solution where the solution would compile its output to the staging folder as intended and then copy the output back to the bin directory. Next I tried updating the .targets such that, instead of physically copying files, they created symbolic links where the bin\Debug folder linked to the compiled output in the staging directory. If I changed the Output Path back to the bin directory and compiled the solution then everything worked as expected.
The problem seems to be specifically related to the Razor view engine and Intellisense based on where the output files are kept.
After researching the problem on the Internet I was unable to come up with a clear explanation for why.
These elements tell MSBuild where to place files once they’ve been compiled.
By default, the Output Path target is the bin folder of the containing project (in this example, Website\bin\).In many cases it’s not uncommon to want to have the compiled files dumped to an external staging directory that can serve as a base for builds or distributed installations.Using this scenario as a use case we’re going to create an external staging directory and update the Output Path element in the project configuration such that the compiled files are placed in the staging directory.For the purposes of this exercise, we’re most interested in the property groups that set properties based on the configuration and platform values.In particular, we’re looking at the Output Path element.Then the application is changed to direct the compiled output to an external staging folder to demonstrate how changing the Output Path of the project file breaks Intellisense. Once we’ve got a bog standard MVC 5 application we’ll take a look at how it’s set up and then explore how it goes wrong.