Hi there,

many users of our product (a VS add-in) regularly report that positions & docking state of the tool windows we create are not persisted across VS sessions. We create tool windows using IVsUIShell.CreateToolWindow and pass it in a valid GUID of the persistence slot in the registry (and this GUID key really exists in the registry). Nevertheless, in some cases the positions and docking state of tool windows are not persisted, and the tool windows display in the default state & position on the next VS restart. The VS logs some users submitted to us contain one interesting cue: in case the tool window positions are not persisted, the log contains the following entry:

<entry>
<record>143</record>
<time>2007/03/01 07:32:36.381</time>
<type>Information</type>
<source>Microsoft Visual Studio</source>
<description>Unexpected system error mode before loading package [Visual Studio Common IDE Package]</description>
<guid>{6E87CFAD-6C05-4ADF-9CD7-3B7943875B7C}</guid>
</entry>

I'm not sure it is relevant, and I don't know what this entry means. Does anybody have an idea what may cause the problem with persistence and how / is the entry above is relevant to this problem?

Thanks.

Hi Dmitry,

Did you report the bug already? If not - you can do it here.

Hi Dmitry,

I think that the conditions of reproducing it is too vague to submit a bug. And also I'm not 100% sure that it is a problem in VS and not in our product. Anyway, thanks for the link - I've to admit that I've not come across connect.microsoft.com it yet :)