Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28665 Discussions

Visual Studio Project: IVsSccProject2::SccGlyphChanged(0, NULL, NULL, NULL) not handled

rhuijben
Beginner
438 Views
Hi,

One of our AnkhSVN (http://ankhsvn.net) users reports that the Intel Fortran projects in Visual Studio don't automatically update their SCC (Source Code Control) glyphs when this project is used with AnkhSVN.

After investigation it seems that the call to
IVsSccProject2::SccGlyphChanged() that AnkhSVN performs isn't handled according to the specifications.

The documentation of this function (http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.shell.interop.ivssccproject2.sccglyphchanged.aspx) implemented by each individual project type like the Intel Fortran projects says:

If all of the parameters are a null reference (Nothing in Visual Basic) and the count equals zero (cAffectedNodes == 0), then all of the associated project files will be updated. In this case, the project must call GetSccGlyph on the SVsSccManager service to retrieve the glyphs for its files. Otherwise, do not call this method.
(My emphasis).


The Fortran project implementation only calls to the SCC manager for the top level files. (I created a Console application using the trial versionto reproduce the problem and the readme.txt file is refreshed correctly, but all files below folders/filters are not).

This results in the behavior that the glyphs are only changed when the project is initially loaded, but not on any status changes.
(As far as I know the rest of our features work correctly on the project)

AnkhSVN is a free download on http://ankhsvn.net/download, so you easily check/reproduce this for yourself.
0 Kudos
2 Replies
Steven_L_Intel1
Employee
438 Views
Thanks - I will pass this on to the development team.
0 Kudos
Steven_L_Intel1
Employee
438 Views
This issue was fixed in Update 2 Revised (11.1.048).
0 Kudos
Reply