We have a situation where we have too many developers needing to work on the same SharePoint 2013 farm. We thought the best way around this was to build out another front-end and install VS 2012 on both, since we have to develop features locally. Now that we have two front-end servers, we're having issues using Visual Studio's "deploy" action where it can't install the feature because it couldn't be found:
Error 1 Error occurred in deployment step 'Activate Features': Feature with Id 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' is not installed in this farm, and cannot be added to this scope. 0 0 TestWP
The crazy part is, until we built out the second front-end server the solutions would install to their server
sp13devserver01. Once we introduced
sp13devserver02 into the mix did things stop working. Another thought was that maybe we were missing a feature to be activated on the new front-end. Turns out that GUID the error message talks about is the one we're trying to deploy.
It seems like Visual Studio will only deploy to one server, and we've evidenced that with a project that just had a package and the package only deployed files to the server with the URL. Is there anyway we can around this? Packaging up and manually adding .WSP through PowerShell is very time consuming when you are developing, and it's stopping us from debugging. Does anyone have any idea on what we can do to get the VS 2012 deploying to work when you have two web front-ends for SharePoint 2013?