Recursively ignored files appear as unresolveds
Hello
Visual Studio suport files (.suo, .ncb, .user) appear as unresolved even though there are recursively ignored from the component root folder.
Editing the .jazzignore and refreshing the sandbox does not change anything but running the command "Add to Ignore List..." on them makes those files actually ignored (no longer unresolved).
Has anybody experienced such a behaviour (seen in VS2005 with RTC 3.0iFix1)?
Visual Studio suport files (.suo, .ncb, .user) appear as unresolved even though there are recursively ignored from the component root folder.
Editing the .jazzignore and refreshing the sandbox does not change anything but running the command "Add to Ignore List..." on them makes those files actually ignored (no longer unresolved).
Has anybody experienced such a behaviour (seen in VS2005 with RTC 3.0iFix1)?
3 answers
Hi Yann,
We have not seen this behavior, can you please give us detailed steps so we can try to reproduce the problem?
- RTC for VS team
Hi
The user loaded a repository workspace in a fresh sandbox, opened a solution containing a few visual C projects and built it.
He refreshed his sandbox and the VS files were shown as unresolved.
To remove them from the pending changes view, he added their extension to the ignore list, which only swapped a few line in the .jazzignore in the component root folder, and the unresolved were gone.
The .jazzignore had originally been created and edited by hand in Eclipse but it shouldn't matter since .jazzignore are plain text files.
Hope it helps.
Yann