i get a strange trouble ,i am developing a software (WPF) with Expression Blend 4 and Visual Studio 10 and untill yesterday i could modify my code in Xaml but today after open the project to continue to work i tried to add some new UIElement as Grid,Border,Textbox and so on i could save without trouble but when i launch the software to verify the result those UIElemen added before did not appear ,i checked out well if the Visibility are Visible and the opacity is nto set to the value =0 ,so i tried to repeat to add others UIElemtn in others Window of the same project but this strange behaviour continuing to bother me...
Do you have any idea what it can be or have some advice to help and work out this step??
Thanks so much for your attention,
Cheers
Related
I'm using Visual Studio 2022 Community Edition w/ .Net 4.8 but the same behavior presents itself with Visual Studio 2019 Professional w/ .Net 4.6.1
What is happening is that I can clone a new Feature branch from Git to my local system and when I launch it everything is fine. The main application form presents itself just fine and I can get to all of the buttons, dropdown lists, file selectors just fine. The minute that I had any new control to the form when I subsequently launch the application the form is cut in half and I can't get to any of the controls and maximizing the form doesn't help either. When I inspect the designer code things have been drastically moved around in the post modification file as compared to the original. I've included sample information--
Original Form Display
Post Modification Form Display
Designer Code Compare Sample
A team member can take the same code base and add controls without any problems. Additionally he took my codebase which runs fine on his system compiled it and sent me the executable and when I launched that executable I had the problems with form display that my solution exhibits.
One final not thinking it was my laptop I got a brand new laptop and I'm still seeing the issue. I also created an AWS EC2 Instance and tried it there with the same behavior.
We're all stumped here none of us has ever seen behavior like this. We're hoping that someone in the Community has seen this sort of thing before and can shed some light on the issue.
Thanks,
Bill
Yesterday I updated windows 10. Today when I opened visual studio it seems like .cs[design] is not working properly. All the components I used is aligned with same size and same margin.
I've tried to roll back some updates, except for those updates that required specific files('__vs' some thing like this).
I didn't change designer.cs or resx file.
Thanks in advance.
i recently installed visual studio 2015 and made my first code in c#.
('maximized' for window state at the properties of the form)
everything went fine (comilation and testrun without errors) until i attempted to load one of the example tutorials, which i interrupted during loading.
after that i compiled and started my self coded application again from within visual studio. this time the output of the form was, unlike before, displayed half its size.
all the buttons including the window of the form appeared half its original size.
but when i executed the comiled application outside of visual studio (without it actually running) the application started in normal scale as intended.
this effect happens for this specific project only. if i start a new project the compilation & testrun will show a form scale as expected.
so my question: is there any magical setting that i have to change to end this nightmare ? i dont like to start all over again with a new project. i had set up 72 different button already. each buttonpress causes a different
SendKeys.Send("");
to be executed.
Check the Form's AutoScaleMode property!
The default is Font:
Controls scale relative to the dimensions of the font the classes are
using, which is typically the system font.
If that won't help do try to create a new project and copy the relevant cs-files into it!
In theory there is a zoom option in the VS designer, but at least in the Winforms desiner the shortcut does nothing for me.. It probably is for the WPF designer.
You did tag the question correctly and it is indeed about Winforms?
My properties window (WPF & C#) will "freeze" after sometime, meaning that I can not edit values, as I can not even enter the textboxes. Weirdly enough, I do can edit anything without text boxes (such as colors, gradients and check boxes).
I have marked red the elements I can not even enter, and green the elements which I can edit normally.
The XAML editor works fine, it is just the properties window. Restarting Visual Studio fixes the problem, aber after 10-30 minutes, the problem repeats.
I'm using Visual Studio Update 4 Community Edition.
I found that selecting one of the properties that works (such as Brush) unfreezes all the properties and events solving the issue in a simple fashion.
I know similar questions exists but they don't address this exact problem.
I'm having an issue with Visual Studio 2008 SP1 whereby it hangs for 4-10 seconds whenever the xaml edit receives focus. It is literally driving me to despair and I'm about to move back to Winforms. Note - Just editing the straight up xaml (i.e no designer enabled) doesn't fix the issue.
I have done the following :
Disable the xaml designer
Disable all plugins Checked FileMon for activity during the hang (there is none)
Checked Disk / Paging for activity the hang (again, none)
Uninstalled Silverlight
Setup :
Windows XP64
8 Core Zeon, 16Gb RAM
The designer for XAML in VS 2008 is weak. Many of these issues have been addressed and dramatically improved in VS 2010 (even in beta 2).
I've started using Blend exclusively for designer-work, and just setup VS to use the XML editor (instead of the designer) for dealing with XAML files. This makes editing instantaneous within Visual Studio, although you need to swap out to Blend if you want a design time experience.
For me, the XML editor just didn't quite work right. What I did was in Tools/Options/Text Editor/XAML/Miscellaneous, activate "Always open documents in full XAML view." This prevents the IDE from trying to render your xaml at open and get right to editing your XAML. When you are ready to pay the render penalty, you can click on the design tab.
Because everyone knows writing xaml by hand is faster and more fun :)
I had exactly same issue with XAML editor - every time I focused, saved, opened XAML code, the Visual Studio got stuck for few seconds.
For me the solution was removing reference to Microsoft.mshtml - I don't understand the reason (if someone does, please comment), but it really was the only problem and removing the reference solved my nightmare.