We have a bug tracking a similar issue: http://nuget.codeplex.com/workitem/435
Currently, our plan is to add a PowerShell helper library that allows you to mark these things in Install.ps1. The reason we're going with this route is we don't want to bake in Visual Studio specifics into the .nuspec file. A package might be installed
via a Command Line or via Web Matrix (ASP.NET Web Pages) and such concepts wouldn't apply. We want .nuspec to be universal.
But it got me thinking, there are some very common scenarios for VS that would be nice to support in a declarative way.
One thing we could do is consider having a separate .vsnuspec specifically for VS settings that would be otherwise ignored by other systems, much in the way "tools" is ignored by non-VS environments.
So if you include .vsnuspec, you could define what the Build Action is for each file if you so choose using a syntax similar to our <files> element. Thoughts?