
|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
The MSBuild project files can be included in one another. Properties/items defined in one file could be used in another freely.
- If some file is included, it should be considered too (hope it's already done).
- 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".
|
|
Description
|
The MSBuild project files can be included in one another. Properties/items defined in one file could be used in another freely.
- If some file is included, it should be considered too (hope it's already done).
- 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". |
Show » |
|
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.