Getting “Value of '-2147483648' is not valid for 'RowPosition'” in Visual Studio while building after making changes to design using WinForms designer.

Researcher 96 Reputation points
2026-05-28T11:51:29.5+00:00

I am running into a persistent and unusual issue while working with the WinForms designer in Visual Studio. Whenever I move or drag any control (such as a TextBox) on a form and then start debugging, Visual Studio throws the following error message three times consecutively before the application finally boots up normally:

InvalidArgument=Value of '-2147483648' is not valid for 'RowPosition'.

This behavior only happens right after I manually alter the layout in the designer. If I run the project for the second time without any changes, the debugger runs completely fine without throwing any errors.

Environment Details:

Project Type: Windows Forms Application

Target Framework: .NET Framework 4.0

Language: VB.NET

IDE Versions: Occurs across Visual Studio 2017 (including Express), 2019, and 2022.

Troubleshooting Already Attempted

I have tried a wide array of code-level checks, environment resets, and caching purges, but most fixes either yielded no results or only worked the very first time before the error returned:

Global Code & Project Search: I globally searched the entire solution for the text RowPosition and the specific value -2147483648, but nothing was found in my custom source code. I also tried commenting out lines calling set_RowPosition inside the .Designer.vb file to no avail.

Layout Panel Configuration: Ensured all controls added via TableLayoutPanel.Controls.Add have unique row and column assignments.

Directory Purges: Performed Build -> Clean Solution followed by Rebuild Solution. I also completely deleted the local, hidden .vs/ environment directory and deleted the project obj/ folder entirely.

Resource File Isolation: Inside the obj/ folder, I deleted the frmmwgrid.resources file. This worked the very first time, but as soon as the designer recreated it on a subsequent control drag, the error returned.

Visual Studio Environment Reset: Executed devenv /resetsettings via the Developer Command Prompt. I also manually exported my settings and reset the IDE to defaults. This also only worked on the very first layout modification before failing again.

Existing Documentation Reviewed: I have researched existing threads on similar issues, Unfortunately, the solutions suggested in those threads have not permanently resolved the issue for my environment.

StackOverflow: https://stackoverflow.com/questions/37030370/visual-studio-2015-ui-throws-invalid-argument-message-on-successful-build

Microsoft Q&A: https://learn.microsoft.com/en-us/answers/questions/5650982/getting-value-not-valid-for-rowpositon-in-visual-s

Question:

What is causing the Visual Studio WinForms designer engine to pass an uninitialized integer (Integer.MinValue) to RowPosition when a control layout is modified, and how can this be permanently resolved?

Developer technologies | Windows Forms
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-05-28T11:51:51.5466667+00:00

    The behavior described is a design‑time problem in the Windows Forms Designer, not an error in the application code. The designer is generating or consuming invalid layout metadata (RowPosition = Int32.MinValue) when the form layout is changed, which then surfaces as an InvalidArgument error during the next build/debug cycle.

    From the available documentation, the supported remediation steps for persistent Windows Forms Designer errors are:

    1. Clean and rebuild the project or solution
      1. In Solution Explorer, right‑click the solution or project.
      2. Select Clean.
      3. Right‑click again and select Rebuild.
    2. Delete intermediate build artifacts so the designer regenerates them
      1. Close Visual Studio.
      2. In the project folder, delete the bin and obj folders.
      3. Reopen the solution and build again.
      This forces a full regeneration of resources and designer‑generated code, which can clear corrupted design‑time metadata that leads to invalid layout values.
    3. Close and reopen the designer after changes When the designer encounters design‑time errors, Visual Studio may require the designer to be closed and reopened for changes to take effect. After modifying the layout:
      1. Close the form designer tab.
      2. Reopen the form from Solution Explorer.
    4. If the issue is tied to a third‑party control or designer Several documented design‑time errors are explicitly caused by third‑party component designers (for example, errors where Visual Studio “cannot save or load instances of the type” or cannot find expected options). In such cases, the permanent fix is to obtain an updated version of the component or contact the component vendor, because the invalid value is being produced inside the component’s designer logic rather than in project code.
    5. If the problem is a known Visual Studio bug For designer bugs that persist after cleaning, deleting bin/obj, and reopening the designer, the documented path is to:
      • Ensure the latest Visual Studio updates are installed.
      • If still reproducible, report it using Report a Problem from Visual Studio so it can be addressed in a future update.

    In summary, the invalid RowPosition value is coming from corrupted or incorrect design‑time metadata rather than user code. The supported ways to permanently resolve it are to:

    • Force regeneration of all designer artifacts (Clean, Rebuild, delete bin/obj).
    • Reopen the designer after changes.
    • Update or replace any third‑party controls whose designers may be emitting invalid layout values.
    • If it remains reproducible on a supported Visual Studio version with no third‑party components involved, file it as a Visual Studio designer bug via Report a Problem so it can be fixed in the product.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Taki Ly (WICLOUD CORPORATION) 4,440 Reputation points Microsoft External Staff Moderator
    2026-05-29T06:03:46.23+00:00

    Hello @Researcher ,

    Thank you for the detailed report and the thorough troubleshooting steps you have already attempted.

    Based on observed behavior reported across the community, the error seems to be triggered by the WinForms Designer's serialization process. When a control's layout is modified inside a TableLayoutPanel, the Designer re-serializes the layout state, and at some point, during this process, Int32.MinValue (-2147483648) appears to be passed as the RowPosition value. It is worth noting that commenting out set_RowPosition in the .Designer.vb file did not resolve the issue in your case, which may suggest the value originates from somewhere beyond the Designer-generated code, though the exact internal mechanism is not officially documented by Microsoft.

    I attempted to reproduce this in my own environment using Visual Studio 2022 Enterprise on Windows 11 24H2, with a VB.NET Windows Forms Application targeting .NET Framework 4.6, 4.7.2, and 4.8, but was unable to reproduce the error on any of those versions. I was unable to test on .NET Framework 4.0 directly due to compatibility limitations, so I cannot confirm whether the issue is specific to that version. Below are screenshots from my reproduction attempt.

    The first shows the initial run with the original layout:

    User's image

    The second shows a subsequent run after deliberately dragging and rearranging controls within the TableLayoutPanel:

    User's image

    In both cases, the application launched without any error dialogs.

    Regarding your question about a permanent resolution, based on community reports and my own testing, there does not appear to be a known permanent fix that keeps .NET Framework 4.0 and the Designer workflow intact. The most viable path to permanently eliminating this issue would be upgrading the target framework to.NET Framework 4.8, as I was unable to reproduce the error on any of the higher framework versions I tested. Since .NET Framework 4.0 is no longer officially supported by Microsoft, this may also be worth considering from a long-term maintenance perspective.

    I hope this helps. Please let me know if you have any additional details that might help narrow down the cause further. If my explanation and the information I provided were helpful, I would greatly appreciate it if you could follow the instructions here so others with the same problem can benefit as well.

    Thank you.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.