We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

converting resx files with 4.1.0.62 fails

Thread ID:

Created:

Updated:

Platform:

Replies:

43519 Apr 25,2006 08:09 AM Apr 28,2006 02:27 AM General Discussion 9
loading
Tags: General Discussion
Administrator [Syncfusion]
Asked On April 25, 2006 08:09 AM

We''ve updated syncfusion from 4.101.0.50 to the assemblies 4.102.0.62. But now the converter from the newest version cannot convert the resx files. Exception: UnauthorizedAccessException when converter is trying to access the pathes of resx files. We didn''t make any changes in the CodeAccessSecurity. And there is no problem when we change the references and lic files back to 4.101.0.50 and try to call converter 2.0 there. Any idea why this exception occures with 4.102.0.62? thx

Administrator [Syncfusion]
Replied On April 25, 2006 10:57 AM

For the main resx file not language specific a serialisation exception occured. And it''s a problem with the GridBagConstraintsConverter ... The attached bmp is a screenshot of the exception from your log in the converter tool. Copy the exception from your tool was not possible. But this would be helpful for giving your support more detailed informations about errors in your tool. So the attached file contains a screenshot from the visible exception text of your tool. thx for your help Lars

GridBagConstraintsSerialization.zip

Davis Jebaraj [Syncfusion]
Replied On April 25, 2006 01:36 PM

Hi Lars, Could you please try downloading and running the Converter Tool from this location: ftp://syncpatch.syncfusion.com/misc/migration.zip Thanks, Davis

Administrator [Syncfusion]
Replied On April 26, 2006 03:12 AM

Hi Davis, here is the log of the exception. System.Runtime.Serialization.SerializationException: Type could not be read from the data in line 477, position 5. The type''s internal structure may have changed. Either implement ISerializable on the type or provide a type converter that can provide a more reliable conversion format, such as text or an array of bytes. The conversion exception was: Member ''GridPosX'' was not found. ---> System.Xml.XmlException: Type could not be read from the data in line 477, position 5. The type''s internal structure may have changed. Either implement ISerializable on the type or provide a type converter that can provide a more reliable conversion format, such as text or an array of bytes. The conversion exception was: Member ''GridPosX'' was not found. Line 477, position 5. ---> System.Runtime.Serialization.SerializationException: Member ''GridPosX'' was not found. at System.Runtime.Serialization.SerializationInfo.GetElement(String name, Type& foundType) at System.Runtime.Serialization.SerializationInfo.GetInt32(String name) at Syncfusion.Windows.Forms.Tools.GridBagConstraintsSerializationSurrogate.System.Runtime.Serialization.ISerializationSurrogate.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector) at System.Runtime.Serialization.ObjectManager.FixupSpecialObject(ObjectHolder holder) at System.Runtime.Serialization.ObjectManager.DoFixups() at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) at Syncfusion.Windows.Forms.Tools.GridBagConstraintsConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value) at System.ComponentModel.TypeConverter.ConvertFrom(Object value) at System.Resources.ResXDataNode.GenerateObjectFromDataNodeInfo(DataNodeInfo dataNodeInfo, ITypeResolutionService typeResolver) at System.Resources.ResXDataNode.GetValue(ITypeResolutionService typeResolver) at System.Resources.ResXResourceReader.ParseDataNode(XmlTextReader reader, Boolean isMetaData) at System.Resources.ResXResourceReader.ParseXml(XmlTextReader reader) --- End of inner exception stack trace --- --- End of inner exception stack trace --- at System.Resources.ResXResourceReader.ParseXml(XmlTextReader reader) at System.Resources.ResXResourceReader.EnsureResData() at System.Resources.ResXResourceReader.GetEnumerator() at ConvertResX.Run(String[] args) at Form1.ConvertFiles()

Administrator [Syncfusion]
Replied On April 26, 2006 03:39 AM

Hi Davis, i have found following problem in your forum. http://www.syncfusion.com/Support/Forums/message.aspx?MessageID=41999

Administrator [Syncfusion]
Replied On April 26, 2006 07:23 AM

We could convert the the resx files now! But the resx conversions forced the related cs file to delete many properties and this is very bad because all our layouts not working. The conversion was working with 4.101.0.50 and didn''t influence any code and application still got the layouts. Only problem we had with 4.101.0.50 that the controls was not editable in Designer of VS 2005! So we''ve installed your patch 4.102.0.62 and converted the resx files. Now they editable with VS 2005 but some changes of your conversions was deleting many code (properties of used controls) in the cs file. What''s that for? For me it looks like many sideeffects occured in the patch changes related to the conversion tool. And many layout and formatting bugs coldn''t be solved especially for GridBagLayouts. So,how to proceed now? Thanks >Hi Davis, > >i have found following problem in your forum. > >http://www.syncfusion.com/Support/Forums/message.aspx?MessageID=41999

Mano J [Syncfusion]
Replied On April 26, 2006 09:26 AM

Hi Lars, We are currently working on this issue.I will update you as early as possible. Thanks for your patience. Regards, Mano

Administrator [Syncfusion]
Replied On April 27, 2006 01:03 PM

I might found the reason for the problems. The binary description in the resx file is invalid. We didn''t set any constraints in the property section,all are using default. Maybee thats the reason why only this control has the problem. Because our other controls with GridBagLayouts are using manually settings in constraints instead the default and there we have no problems. Also your customer who had the same problem and postet his problems here in the forum are using default settings for the constraints and did not change them. Thats what the binary information is showing us. Maybee it helps you to fix the problems. Default values in the property "Contraints on" might cause buggy binary entries in resx files. AAEAAAD/////AQAAAAAAAAAMAgAAABZTeW5jZnVzaW9uLlNoYXJlZC5CYXNlBQEAAAAxU3luY2Z1c2lv bi5XaW5kb3dzLkZvcm1zLlRvb2xzLkdyaWRCYWdDb25zdHJhaW50cwwAAAAIZ3JpZFBvc1gIZ3JpZFBv c1kJY2VsbFNwYW5YCWNlbGxTcGFuWQd3ZWlnaHRYB3dlaWdodFkGYW5jaG9yBGZpbGwGaW5zZXRzBWlw YWRYBWlwYWRZB2lzRW1wdHkAAAAAAAAEBAQAAAAICAgIBgYqU3luY2Z1c2lvbi5XaW5kb3dzLkZvcm1z LlRvb2xzLkFuY2hvclR5cGVzAgAAACdTeW5jZnVzaW9uLldpbmRvd3MuRm9ybXMuVG9vbHMuRmlsbFR5 cGUCAAAAJVN5bmNmdXNpb24uV2luZG93cy5Gb3Jtcy5Ub29scy5JbnNldHMCAAAACAgBAgAAAAUAAAAA AAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAPA/Bf3///8qU3luY2Z1c2lvbi5XaW5kb3dzLkZvcm1zLlRv b2xzLkFuY2hvclR5cGVzAQAAAAd2YWx1ZV9fAAgCAAAAAAAAAAX8////J1N5bmNmdXNpb24uV2luZG93 cy5Gb3Jtcy5Ub29scy5GaWxsVHlwZQEAAAAHdmFsdWVfXwAIAgAAAAEAAAAF+////yVTeW5jZnVzaW9u LldpbmRvd3MuRm9ybXMuVG9vbHMuSW5zZXRzBAAAAARsZWZ0A3RvcAVyaWdodAZib3R0b20AAAAACAgI CAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACw==

Administrator [Syncfusion]
Replied On April 27, 2006 01:06 PM

Complete XML from resx. AAEAAAD/////AQAAAAAAAAAMAgAAABZTeW5jZnVzaW9uLlNoYXJlZC5CYXNlBQEAAAAxU3luY2Z1c2lv > bi5XaW5kb3dzLkZvcm1zLlRvb2xzLkdyaWRCYWdDb25zdHJhaW50cwwAAAAIZ3JpZFBvc1gIZ3JpZFBv > c1kJY2VsbFNwYW5YCWNlbGxTcGFuWQd3ZWlnaHRYB3dlaWdodFkGYW5jaG9yBGZpbGwGaW5zZXRzBWlw > YWRYBWlwYWRZB2lzRW1wdHkAAAAAAAAEBAQAAAAICAgIBgYqU3luY2Z1c2lvbi5XaW5kb3dzLkZvcm1z > LlRvb2xzLkFuY2hvclR5cGVzAgAAACdTeW5jZnVzaW9uLldpbmRvd3MuRm9ybXMuVG9vbHMuRmlsbFR5 > cGUCAAAAJVN5bmNmdXNpb24uV2luZG93cy5Gb3Jtcy5Ub29scy5JbnNldHMCAAAACAgBAgAAAAUAAAAA > AAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAPA/Bf3///8qU3luY2Z1c2lvbi5XaW5kb3dzLkZvcm1zLlRv > b2xzLkFuY2hvclR5cGVzAQAAAAd2YWx1ZV9fAAgCAAAAAAAAAAX8////J1N5bmNmdXNpb24uV2luZG93 > cy5Gb3Jtcy5Ub29scy5GaWxsVHlwZQEAAAAHdmFsdWVfXwAIAgAAAAEAAAAF+////yVTeW5jZnVzaW9u > LldpbmRvd3MuRm9ybXMuVG9vbHMuSW5zZXRzBAAAAARsZWZ0A3RvcAVyaWdodAZib3R0b20AAAAACAgI > CAIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACw==

Administrator [Syncfusion]
Replied On April 28, 2006 02:27 AM

Hi Larsk, Sorry for the delay in getting back to you. I was able to reproduce the problem regarding the GridBagLayout and have notified our development team regarding this issue. This problem seems to be raised because of structural changes made for fix #1472 1472. We will try our very best to fix this issue at the earliest. Defect #1810 - GridBagLayout throws error as Resource transformation for file ''''ctlExtraction.resx'''' failed. I will update you once this issue is fixed along with the download link. Thanks for your patience. Best Regards, Seetha

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;