Even if you could, you wouldn't want to. The designer has to be able to set the minimum size of a control. You don't actually care about that probably.
What you want to do is manage what it gets set to. For that the base Control class already provides a better solution. To be notified when the size is set you'll override the base property.
In the few cases where you can't change the size of a control Label comes to mind you'll find that the setter either doesn't do anything or it just doesn't use the property at all internally. If you absolutely must ensure that MinimumSize doesn't show up as an option then you can't derive from Control.
It's still settable, just not visible. Make it intuitive for a future developer that the minimum size shouldn't be changed without some thought. I still think that the designer itself creating a compiler error by trying to set a protected property, that it knows is protected since it grays out the options in the properties section is a bug. The content you requested has been removed.
Reporting a problem through Visual Studio allows for diagnostic information to automatically be included in the report. It's essential information that gives our engineers the context they need to fully understand your issue and work to resolve it. When you report through Visual Studio, you can easily share rich diagnostic information with us, such as large log files, crash information, screenshots, repro recording, and other artifacts that help us deliver higher-quality resolutions faster to you.
If you don't want to or can't use Visual Studio to report a problem, there's a chance the problem has already been reported and a solution posted on the Visual Studio Developer Community page. If you don't have a problem to report but want to suggest a feature, there's a place for doing that too.
For more information, see the Suggest a feature page. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback. In this article. New indicates that the bug or issue is newly reported, and no action has been taken on it yet. Triaged indicates that preliminary steps such as moderation, translation, and initial check for duplicates are complete.
Your ticket has been routed to the appropriate engineering team for consideration. Under Consideration indicates that Microsoft is reviewing your problem for community impact and will prioritize it accordingly. If the community impact isn't clear or significant yet, we'll continue to monitor the problem in this state.
Under Investigation indicates that engineers are actively investigating your problem to find a resolution. Need More Info indicates that we need more diagnostic information from you so that we can go forward with the investigation. Learn how to respond to Need More Info requests. Report abuse. Details required :. Cancel Submit.
Hi, I'm Elise, and I'd be happy to help with your issue. Kind Regards, Elise. How satisfied are you with this reply? But given all of the possible combinations, it is simply not possible for us to test our code sufficiently for all configurations. In Visual Studio , for example, we have identified some performance issues if you are on specific hardware and we published a list of hardware configurations that commonly encounter problems, and how to trouble shoot them.
To understand this correlation, we had to collect a lot of information from our customers through emails, or back-and-forth communication on MS Connect, and forums. The Visual Studio feedback tool collects this machine configuration information automatically, and places it in the DxDiagOutput. Our engineers will use this information to find correlations with less effort, and fix them.
While we can sometimes reproduce repeatable issues from a set of written repro steps, we can almost always reproduce an issue when a good recording and diagnostic information is included with the description of the issue. For example, what we need to understand a performance issue you are experiencing is quite different than what we need when you experience a crash in Visual Studio.
To make this process simpler, we have implemented a feature called repro recorder. If you encounter slow performance with the product, a trace with Windows Events is very helpful for our engineers to decipher the issue. Such trace files help our engineers identify whether the issue is CPU-based, disk or network intensive, or whether the issue is altogether a different program for more info, you can read about how to do a performance analysis.
Now we have a lighter version of this tool, called the Microsoft Visual Studio Trace recorder, which is integrated with the Visual Studio Feedback tool. Because the tool optimizes trace collection, you can run it for as long as it takes to show the problem, up to about 2 hours.
Hence, you can easily capture traces even if the performance issue is not happening consistently. If you are experiencing a crash in Visual Studio, you will see the Watson dialog.
The Windows Error Reporting service collects a memory dump of Visual Studio, and asks you whether to send the report back to Microsoft. This reporting is very helpful for us to identify and fix the most frequent crash issues, but we only know about the issue if you send us the error report. Such reports are collected in a central Watson server, and our engineers constantly watch it to identify the top issues and get most of them fixed.
In addition to sending the Watson report, you can report a Connect bug for it using the feedback tool. The Visual Studio Feedback tool allows you to capture the relevant information easily, working with VS Debugger to capture the dump file, and working with Windows Problem Step Recorder to capture your steps.
The Connect bug will give you a place to have a conversation about the issue, whereas Watson captures the issue, but there is no follow-up. If Visual Studio hangs for example, the editor freezes up for some time , you usually do not get a Watson dialog. Hangs are similar in nature to crashes, but harder to detect since the IDE generally comes out of the freeze.
0コメント