Don't do it.
Well there's no harm in it as long as you recognize that if you make a subsequent change to a form in the designer the design.cs code is COMPLETELY regenerated

>Update: It worked and didn't seem to break it :o)
>
>
>
>(Sorry, this is a Duplicate Post)
>
>Ok, the general rule is to leave the designer.cs file alone. However, the only thing I want to edit is the BoundProperty value on my controls. I am redoing a VFP form of 32 pages and each page has approximately 10-30 controls on it so updating the bound property on every page is very time consuming. Right now, the form has old variables in the boundproperty and I need to update every one with the new dotnet variable name. So, I want to parse the file and find:
>
>this.pgGenProp1.BoundProperty = "glMyVarName";
>
>and take the value glMyVarName, find it in a table, and replace it in the designer.cs file with "MyNewVarName" programmatically.
>
>I have a table with the old vars and the new vars.
>
>Can I do it? Has anyone done that before? As long as I don't touch anything else, is it reasonable for it not to break?