I've just upgraded to Windows 10 and VS2017, and after importing my project I've noticied that my ListView column headers aren't aliging up properly with the rows below.
I've created a blank new WinForm project in VS and got the same result, in the designer as well as the compiled program.
As my program pretty much centres around this it just doesn't look right, anyone seen this or know how to fix it?
It was working fine on Win7/VS2015, so not sure what's changed?
Related
Unfortunalty I need to use .NET 3.5 and use charts in the designer. Everything works quite well. I have added a package Microsoft Chart Controls that are not there by default with .NET 3.5 and added the dlls to the tools bar and to the reference.
I able to have the chart displayed in the designer and work with its data in the class. Problems start if I close the designer window and then open it again - I get a bunch of design time errors!
The strangest thing is that the code compiles and the chart works well in the application. Also the code behind in the auto generated design.cs stays untouched but i get millions of errors such as:
Has anyone come across a similar situation? Don't know how to go around it. I am using Visual Studio 2017. Thanks!
I think you have to add reference of this dll
System.Windows.Forms.DataVisualization.Charting.ChartArea
If this error will showing continuously then
Please add a new Winform and add a chart control.
then write your code in new created form . it will work.
This is really annoying: a WPF production application that works for months at the customer and hasn't been touched suddenly stopped to compile. I'm getting tons of errors of the type "schema information not found":
Could not find schema information for the element 'http://schemas.microsoft.com/winfx/2006/xaml/presentation:Grid'
Could not find schema information for the element 'http://schemas.microsoft.com/winfx/2006/xaml/presentation:UserControl'.
Could not find schema information for the element 'http://schemas.microsoft.com/winfx/2006/xaml/presentation:Grid.ColumnDefinitions'.
etc...
Anyone out there that has an idea how to fix that?
OK, after a day of playing around I got the thing working again and I would like to share what happened.
All the errors came from a single user control. They were so many that their count exceeded what VS2015 would display. When I opened the component in the editor I could see the XAML code but the design window didn't show up, as if for VS this was a normal class module.
After trying around eventually I copied both file of the component (XAML and c#) to a backup location, deleted the coponent from the project, created a new user control with the same name and copied and pasted all code from the saved files into the newly created component. And suddenly everything worked again as always.
It seems to me that the problem was somewhere within VS2015 as the application works now again with literally the same code as before. I only recently updated from VS2013 and in all the years I never had any comparable issue with that version.
I'm working on an existing WinForms application and I am having some weird issues with Infragistics controls in a WinForms app.
When I open a form or usercontrol in the project that has Infragistics controls on it, it looks like
this http://sdrv.ms/S7gvmS
I cannot access any of the controls in the design surface. Clicking does nothing. And, all of the controls appear in the lower area.
So I created a new test solution and dropped some Infragisstics controls on and got this http://sdrv.ms/SRdo2y
Anyone know what's going on?
When I've run in to similar issues before it's tended to be a license or version problem, the Infragistics libraries contain code stopping them working at design-time if a valid license isn't installed. To resolve this, I'd first recommend deleting all of the *.licx files in your solution. These can be easily corrupted especially if you're using source control and should be regenerated correctly when you go in at design time. If that fails, then I'd try uninstalling and reinstalling Infragistics ensuring the version installed matches those of your projects' reference.
P.S. Realise this is far too late to help the original poster but hopefully will help people coming across similar issues in the future.
This happens when Visual Studio cannot find the Design assembly. The components refer to a designer and if Visual Studio cannot find the designer, it makes the assumption that the object is a component instead of a control and places it in the system tray.
Typically, this indicates that something when wrong with your installation of the components, so the usual solution is to re-install.
We have an old project that is designed using VS2005 and WinForms. Everything works perfectly on Windows XP, but when I open the designer on Windows 7, everything breaks down.
The controls get sized to random size and some of them dissappear (or are moved to random coordinates).
What can we do to solve this issue? Should we switch to VS2008?
A newer version of VS should help, but i'd be surprised if this can't be fixed in 2005.
Try commenting everything out in the method where initializeComponent runs, or any properties that set UI change. You should find it easy enough, it's a method that has long lists of calls against the controls on the form.
The problem was that we used TableLayoutPanel inside a GroupBox and not on the form. When we added the TableLayoutPanel on the form and moved the GroupBox into it, the designer stays ok.
I'm a big fan of the rather obscure "Document Outline" window in VS 2008 (it's buried in the View -> Other Windows menu).
It's the only way I know to get a view of the containment heirarchy for a complicated WinForm that has a lot of nested controls.
Some months ago, this just stopped working for the most complicated form in my WinForms project. Now it just displays "There are no items to show for the selected document", no matter what I select in the designer.
No clue as to what broke it - the form contains a mix of common MS controls and some third party controls (mainly DevExpress). Several SplitContainers, but Document Outline originally had no problem with these.
Anybody else seen this, and any suggestions on how to fix it?
After some poking around, I solved the problem myself.
I just started deleting controls from the form, to see what would happen.
Turns out the 3rd party grid I'm using caused the problem - when I reconfigured it, the problem went away. (Looks like a bug in the control, which I've reported to the vendor).
Interesting...misbehaving controls can break the VS IDE, not just your apps.