Hello,
when I open a form or a user control with a NetAdvantage control on it, VS attempts to check out all the related files (xxx.cs, xxx.resx, xxx.Designer.cs, xxx.GeneratedCode.cs). When these files are checked out by another person, the Designer will fail to open the form or user control.
Is there any way to circumvent this behaviour? Currently I am not even able to just look at a form when one of the files can't be checked out by me.
Regards,
Torsten
I see this problem as well. For some forms, it will check out the form, designer, and resx ever time I open it. This is doubly troubling because the designer is not the most stable, and tends to crash, often dropping my grid definitions or some other important item. When this happens, it is hard to know if there is a legitimate change, or if opening the form caused the checkout.
I noticed that it also renames the controls in the designer quite a bit, so maybe those two are related.
Hi,
mislicensing said: [...] For some forms, it will check out the form, designer, and resx ever time I open it. [...] When this happens, it is hard to know if there is a legitimate change, or if opening the form caused the checkout.
[...] For some forms, it will check out the form, designer, and resx ever time I open it. [...] When this happens, it is hard to know if there is a legitimate change, or if opening the form caused the checkout.
We experience exactly the same problem. Fixing this issue would do us a great favour!
mislicensing said: I noticed that it also renames the controls in the designer quite a bit, so maybe those two are related.
As far as we could observe, renaming affects mostly "helper objects" as Appearances, UltraGridColumns, UltraGridBands etc., which are used to initialize controls.
In addition we observe, that line order has changed and that sometimes ressource strings are arbitrarily assigned to string properties. For example the latter is the case for UltraNumericEditor.FormatString, when no FormatString is assigned.
All these things make it difficult to seperate intended changes by the developer from random changes by the designer code generator.
Hope you (Infragistics) can address this behaviour.
Thanks,
Roman