Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SplitContainerDesigner is missing in .net6.0. #8749

Closed
PanchRajMaurya opened this issue Mar 6, 2023 · 9 comments
Closed

SplitContainerDesigner is missing in .net6.0. #8749

PanchRajMaurya opened this issue Mar 6, 2023 · 9 comments
Assignees

Comments

@PanchRajMaurya
Copy link

Environment

I have a project that uses the SplitContainer and its designer at runtime. It was working fine in .NET framework(4.8) but after upgrading to .net6.0 the control is not visible on designer site.

.NET version

I have upgraded the project from .Net framework(4.8) to .Net6.0.

Did this work in a previous version of Visual Studio and/or previous .NET release?

It was working fine in .Net Framework 4.8.

Issue description

We have provided a feature to our customers in which the controls of the forms can be resized and relocated at runtime.
Then it is stored as a xml file and reloaded when reopened the same form.
After upgrading to .net6.0 the designer of the form is not visible in edit mode at runtime.

Steps to reproduce

https://www.c-sharpcorner.com/UploadFile/asmabegam/easy-form-design-at-run-time-C-Sharp-winform/

Diagnostics

No response

@PanchRajMaurya PanchRajMaurya added area-VSDesigner Windows Forms out-of-proc designer related issues untriaged The team needs to look at this issue in the next triage labels Mar 6, 2023
@RussKie
Copy link
Member

RussKie commented Mar 6, 2023

Related #4908.

@PanchRajMaurya
Copy link
Author

As per #4908, SplitContainerDesigner is out of scope. Then what are the alternatives for the same.

@merriemcgaw merriemcgaw removed area-VSDesigner Windows Forms out-of-proc designer related issues untriaged The team needs to look at this issue in the next triage labels Mar 9, 2023
@merriemcgaw merriemcgaw added this to the Future milestone Mar 9, 2023
@merriemcgaw
Copy link
Member

This is the first request we've had for this designer at runtime. The out of process WinForms designer already implements this for working in VS. It looks like you were also using the designer at runtime, so we should consider porting it.

@dmitrii-drobotov can your team take a look and let me know what you think about picking up this issue?

@dmitrii-drobotov
Copy link
Contributor

@merriemcgaw sure, porting this designer doesn't seem too complicated, I think we can pick it up.

@PanchRajMaurya as a workaround, could you try an approach from this comment? The designer won't be very functional but at least would appear on the form.

@PanchRajMaurya
Copy link
Author

@merriemcgaw sure, porting this designer doesn't seem too complicated, I think we can pick it up.

@PanchRajMaurya as a workaround, could you try an approach from this comment? The designer won't be very functional but at least would appear on the form.

After implementing the SplitContainerDesigner as per the comment, the existing forms are visible on designer site but still not able to create new form by using SplitContainer because there are no Panels in dropped control.

@PanchRajMaurya
Copy link
Author

Any timeline to fix the issue?

@merriemcgaw
Copy link
Member

We don't yet have a timeline for this fix unfortunately. @dreddy-work do you think we can get this on the backlog and have it done for .NET 8?

@dreddy-work
Copy link
Member

Will take a look and update the scope here.

dreddy-work added a commit that referenced this issue Jun 20, 2023
SplitContainerDesigner
SplitterPanelDesigner
SplitterDesigner.

Related to #4908
Fixes ##8749
dreddy-work added a commit that referenced this issue Jun 21, 2023
#9320)

* Port missing designers.

SplitContainerDesigner
SplitterPanelDesigner
SplitterDesigner.

Related to #4908
Fixes ##8749

* Fix build failure.
@dmitrii-drobotov
Copy link
Contributor

SplitContainerDesigner was added in #9320.

@ghost ghost removed this from the Future milestone Jul 5, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Aug 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants