Our main form has menu, toolbar and status bar. Sometimes when opening form in the designer we get exceptions (visible as items in task bar) -CodeDomSerializerException saying : "variable XXX was either not declared or was never initialized.". XXX can be Categories, Bars or Items properties, always all of them. When debugging this problem we see only .Net code on the stack, and exception was from CodeDomSerializer.DeserializeExpression.
Visible result is disappearing of status and tool bars (code that creates and initializes them in InitalizeComponent is erased too). It happens to SyncFusion controls only, and only in this project - we have no problems with them in another projects. After re-entering VS.Net, erasing all binaries and rebuild it usually stops, but sometimes doesn't. In addition - when executing VS.Net under debugger it's almost impossible to reproduce, we've attached debugger to the VS.Net process after it happened once, closed and re-opened mainform.
Any ideas ?
ASArun Srinivasan Syncfusion Team October 29, 2003 03:38 PM
We are sorry to hear you are encountering this problem and it would be of great help if you could help us reproduce this issue consistently before we can get to what could be causing this.
There have been sporadic instances of folks encountering problems when using the Designer.
Here are a few suggestions we have to see if it helps you get this issue resolved:
a. Did this happen after an upgrade from a previous version of Essential Suite?
b. Do you have more than one version of Essential Suite installed on your machine?
c. Can you check the references of your project and see that they are correct?
You can run the Assembly Manager from the Start Menu (Start->Programs->Syncfusion->Essential Suite->Assembly Manager.
This will also update your GAC.
d. Can you check your GAC to ensure that there is only one version of the syncfusion dlls?
e. Can you try setting copy local = false in the references for syncfusion dlls and see if it helps? (If you set copy local = true, the syncfusion dlls should be deleted from the GAC.)
f. Do you encounter this problem in the samples that ship with Essential Tools?
Can you take a look at these suggestions and post an update?
AAAlexander ArlievskyNovember 4, 2003 05:35 AM
Sorry for delay. Here are the answers:
c. They are correct.
d. I use version from local directory, without GAC, and there is no syncfusion in GAC. Local directory is under ClearCase control, but problem is seems to be unrelated to ClearCase.
e. Copy local-false leads to multiple dlls locks and build fails (we have 12 dlls in our solution).
f. Samples and other _our_ projects works more or less ok.
Our main project is the biggest one, and sometimes has those "designer" problems. It looks like root of those problems is in the mix of VS.Net, complex visual inheritance and Syncfusion.
In our case, controls that derive and/or use Syncfusion controls are declared in assembly A, placed on controls in assembly B, and those controls are derived in assembly C, and used in forms in assembly D - a heck of visual inheritance :)
ASArun Srinivasan Syncfusion Team November 4, 2003 12:20 PM
The reason for the controls disappearing is due to the fact that the Syncfusion dlls are not in the GAC.
You need to have the Syncfusion dlls in the GAC and you can have local copies of the other dlls.
Can you try this out and let us know if you still encounter this problem?