Hi Stuart,

I have consulted this issue with our dev team--you are correct that
providing your own browse object would enable you to control what is shown
in the properties window, and as such, if you don't need those per file
properties to be part of the build, you can come up with way to store them
in the project file and retrieve them later, but may not be in the way you
show for the sample (which may be required if you need those as part of the
build).

For the issue about persisting some extra data for the customer project
node, you should be able to set metadata with
IVsBuildPropertyStorage::SetItemAttribute. You can also use a property
extender (rather than replacing the browse object entirely) in order to
display your additional property.

Wish it helps!

Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006.  Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.