There's a few issues with this if your customers will be using VS (at least there were under 2008, haven't tried in 2010). You might want to experiment a little to see if these cause you issues.
In my experience: * the Visual Studio Source Control plugins hate this and will not grab new files that are added by other users (this seems to be because these tools read the project file and they have no idea what **\*.* means in your repo). * VS will occasionally rewrite your ItemGroup. For instance, if you add a JS file via Visual Studio it will add it explicitly to the project. Sometimes it seems to rewrite the whole ItemGroup and drop your wildcard which is quite frustrating. On Wed, Mar 24, 2010 at 10:36 AM, David Connors <da...@codify.com> wrote: > On 24 March 2010 11:37, Filip Kratochvil <filip...@gmail.com> wrote: > >> <ItemGroup> >> <JSFiles Include="root_dir\another_dir\*.js" /> >> </ItemGroup> >> > > Good (and totally obvious except if you're using the IDE :) suggestion ! > > Unfortunately it only does one level deep. > > Based on your inspiration, I found this: > http://blogs.msdn.com/msbuild/archive/2005/11/07/490068.aspx > > which lead me to write this: > <ItemGroup> > <Content Include="NewFolder2\**\*"> > <CopyToOutputDirectory>Always</CopyToOutputDirectory> > </Content> > > Using either *.* or * as the match part works *almost* correctly but > it will not include empty folders. > > -- > David Connors (da...@codify.com) > Software Engineer > Codify Pty Ltd - www.codify.com > Phone: +61 (7) 3210 6268 | Facsimile: +61 (7) 3210 6269 | Mobile: +61 417 > 189 363 > V-Card: https://www.codify.com/cards/davidconnors > Address Info: https://www.codify.com/contact > > -- Michael M. Minutillo Indiscriminate Information Sponge Blog: http://wolfbyte-net.blogspot.com
