Note that there are some explanatory texts on larger screens.

plurals
  1. POUpgrade error .net 1 winforms application
    primarykey
    data
    text
    <p>I have an ld application written in .NET 1.1 which I try to upgrade to .NET 3.5. The VsStudio conversion is all fine, and after the upgrade I can run the application without any problems. However, since the fonts are another the text won't fit inside the controls. And that's where my trouble start, because as soon as I change anything, be it the size of a control or the size of any font, after a build the designer stops working with that form, hides it and display an error:</p> <pre><code>at System.ComponentModel.ReflectPropertyDescriptor.SetValue(Object component, Object value) at Microsoft.VisualStudio.Shell.Design.VsTargetFrameworkPropertyDescriptor.SetValue(Object component, Object value) at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializePropertyAssignStatement(IDesignerSerializationManager manager, CodeAssignStatement statement, CodePropertyReferenceExpression propertyReferenceEx, Boolean reportError) at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeAssignStatement(IDesignerSerializationManager manager, CodeAssignStatement statement) at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeStatement(IDesignerSerializationManager manager, CodeStatement statement) </code></pre> <p>Then, when I try to run the application, it won't load those forms at all, I only get an error. I'm not that comfortable with .NET so any hint on what might be the error would be helpful, thanks and regards!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload