Conflicting paths for Website module

Kate Percival

I used the
Cobalt Module Setup Instructions to set up the Website module. This told me I needed to get the Static Content module as well, and to set the path from $/Cobalt Static Content/Development to \data\Cobalt Static Content. Now I need the Document module as well, which also needs Static content, and this has told me to map $/Cobalt Static Content/Development/Static Content to \data\Cobalt Static Content. I thought it would be OK to leave the static content module as I already had it, but no, when I try to build the document module I get "The Web site 'D:\data\Cobalt Static Content\Development\StaticContent\site' does not exist". Please tell me how I can get both Website and Document to use the same Static Content module, instead of having to have the whole lot checked out twice!!

Kajsa Anderson

One option would be to use a directory junction (like a symbolic link) to point from one to the other. The command (at the command prompt) is `MKLINK /J


`

Joel Peterson

Kate, there are some conflicting Document module setup instructions out there. The instructions at
http://tfsnpt.int.thomson.com/Sites/Cobalt%20Document/Team%20Wiki/Wiki%20Pages/Set%20up%20your%20Computer%20(Native).aspx seem to be the most accurate,minus the part about MVC3 since Document now uses MVC4. I have both modules running locally and they both expect that $/Cobalt Static Content/Development is mapped to \data\Cobalt Static Content\Development. This results in the path \data\Cobalt Static Content\Development\StaticContent\site existing locally.