E
edster
A *lot* of our teams code is being deleted from the
InitializeComponent() section of a winform, such as Grid settings,
event handler hooks, layout settings etc. This mainly seems to
happen to 3rd party controls such as Infragistics grids and menu bars
and toolbars, but it also happens on native .net tools.
I know you're thinking that I modified that procedure, but that's not
the case, the designer generates it wholly, i don't even move code
region in the code behind, I just leave it where it is. I tested
without an inherited form, without enums in the same cs file, etc
etc. But sometimes as soon as i open a form, it asks to check out
from source control and then wipes all the extended properties that
the designer generates in the initialize component procedure.
Recently, we cannot even make changes to the controls in the
"properties" window because it will wipe the code out.
We *never* touch this region of the form, the designer controls it
all. And we can't lose the productivity of not using the designer
for such simple tasks as layout and such.
I've read quite a few postings, but no solutions, and this bug has
followed us from beta, to 2002, to 2003....please has anyone a
solution for this issue? This is documented across multiple projects
and 8 developer boxes, some not even connected to the same domain, it
definitely exists.
InitializeComponent() section of a winform, such as Grid settings,
event handler hooks, layout settings etc. This mainly seems to
happen to 3rd party controls such as Infragistics grids and menu bars
and toolbars, but it also happens on native .net tools.
I know you're thinking that I modified that procedure, but that's not
the case, the designer generates it wholly, i don't even move code
region in the code behind, I just leave it where it is. I tested
without an inherited form, without enums in the same cs file, etc
etc. But sometimes as soon as i open a form, it asks to check out
from source control and then wipes all the extended properties that
the designer generates in the initialize component procedure.
Recently, we cannot even make changes to the controls in the
"properties" window because it will wipe the code out.
We *never* touch this region of the form, the designer controls it
all. And we can't lose the productivity of not using the designer
for such simple tasks as layout and such.
I've read quite a few postings, but no solutions, and this bug has
followed us from beta, to 2002, to 2003....please has anyone a
solution for this issue? This is documented across multiple projects
and 8 developer boxes, some not even connected to the same domain, it
definitely exists.