History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RSRP-36517
Type: New Feature New Feature
Status: Submitted Submitted
Priority: Normal Normal
Assignee: Andrew Serebryansky
Reporter: Serge Baltic
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ReSharper

MSBuild: Lookup More Files to Determine the Context

Created: 02 Mar 07 01:26   Updated: 20 Mar 08 22:56
Component/s: Language - Build Scripts
Fix Version/s: Future Versions
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
The MSBuild project files can be included in one another. Properties/items defined in one file could be used in another freely.
  1. If some file is included, it should be considered too (hope it's already done).
  2. Search more files for context (such as externally defined properties):
    • All files in the current solution (not project only! include solution items!). The extension could be *.*proj, *.targets, *.tasks, maybe something else; at least, it's an XML file with a known xmlns.
    • All suitable files in the default MSBuild folder (something like MS .NET Framework home dir).
    • All suitable files in the MSBuild extensions folder and its subfolders (program files -> msbuild).

Looking for solution items will work like "if you've opened them all in the editor at once, they'll catch up with one another".



 All   Comments   Work Log   Change History      Sort Order:
Victor Sergienko - 20 Mar 08 20:42
MSBuild community tasks (http://msbuildtasks.tigris.org/) are something one cannot really go without.
For instance, incrementing a version or checking out from VSS/TFS.

So this should be an important feature.
Maybe editor just can use third-party XML schema, users could even contribute it to you.


Serge Baltic - 20 Mar 08 22:56
You can use a third-party MSBuild XSD in Visual Studio already.