Deployment Receiver, Multiple Source Path Folders

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2009 11:45 AM
Is there a way to specify multiple folders in a deployment receiver's source path attribute? It would be a lot easier to specify a few folders TO deploy, rather than a bunch of excludes to NOT publish.
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2009 12:32 PM
No. Excludes only filters out. The expected use-case is pretty much everything in the web project is deployed.
However I'm interested in your use-case here. What are you trying to achieve?
However I'm interested in your use-case here. What are you trying to achieve?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2009 04:16 AM
We have our code base in the ROOT webapp to enable virtualization preview, and we have 2 (with the necessity to extend to more) localized content folders. The english content folder is the "pivot" folder, and we make layered folders for every other localization.
I ended up making a folder called 'content' in 'ROOT' which I placed both localized content folders in, which I entered as the source path in the deployer.
We don't want the code to get deployed along with the content because we have a Continuous Integration server running (CruiseControl) working along with our code base that is versioned in SVN that does all the code deployment.
I ended up making a folder called 'content' in 'ROOT' which I placed both localized content folders in, which I entered as the source path in the deployer.
We don't want the code to get deployed along with the content because we have a Continuous Integration server running (CruiseControl) working along with our code base that is versioned in SVN that does all the code deployment.
