I am not sure did they change it the way we can do it or is there any simpler way or they actually removed the option and limited us to use code instead
in vs 2019 if we double click the button we directly went to click event of a button and then from the upper right dropdown box we can easily move to any other event of a current object like double click or mouse over etc which automatically created the event handling SUB
but I am not able to do it in the VS 2022 so what happened with it?
as you can see in the attached images
I'm truly hoping that it's a bug in VS2022 because I'm really missing this function too. I've found a lot of topics in the official discussions and feeds and it seems that different older versions have the same issue, but they have already patched them. No info about 17.0.x version. :( I'll investigate further. Please report if somebody find a working solution.
Go to Options->Text Editor->(your language) and enable "Navigation Bar".
Previously answered here:
Visual Studio window which shows list of methods
This bug has been fixed in the latest version of the VS 2022 as per below post. Just tested and seems to be working as it used to!
https://developercommunity.visualstudio.com/t/event-drop-down-menu-in-the-upper-right-corner-of/1579215
well finally I found the answer to my question with thanks to mrtn
Microsoft finally found the bug and fixed the Asked Issue in question, so New update will solve this problem that was a bug from VS 2022
Additionally, I want to mention there is another way to create/edit Object's Events from Design view
Go to the design view and then click the Button with Lightning icon, a list of Events will Appear, and then go for the desired event and double click to add the event or edit it
Related
Edit: I see "Silverlight -" is in front of my question, which I realize may have something to do with the alphabetical order of my tabs... really Visual Studio 2013 should be in front, anyone know if that can be changed?
I've been using the newer Visual Studio 2013 for about a week now, and I've found some quirks with it. The one that seems to happen the most is when I'm in the XAML editor working on something, suddenly if I go over to the property window I can't enter anything. I'm not running/debugging. I can type stuff in the regular XAML code editor window.
Even stranger, one of the times, I could get the cursors to appear in the fields. I typed a bunch of junk and just one character from what I types appeared. Another time I couldn't enter values into the properties, but I could double click on an event in the events window and create a new event handler. Just a minute ago I had the opposite, where I couldn't double click in the events window.
I think VS 2013 introduced async handling of more things, could it be related to that? Or perhaps because I'm using Silverlight? Right now my only workaround is to restart VS, does anyone have any knowledge about this? Anyone else experienced this?
I'm going to submit a bug report, but it would be a while before there's a patch, so I'm wondering if maybe someone understand the problem better and has a workaround? Or maybe just confirm that this exists and that I'm not crazy/my computer's haunted.
Edit:
I should mention another weird thing that happened two nights ago. I thought it was some how my doing, but I never figured out how I could have managed it without noticing. I was working on a piece of code, went to run after changing a few lines, and suddenly I had a ton of compiler errors. I go over to a user control I haven't touched in hours and suddenly the main LayoutRoot grid is completely empty. Luckily I'd committed to source control, but still...
I found an easy way to deal with this problem. It happens a lot after debugging so what I did was I created a batch file on my desktop containing this line taskkill /f /im XDesProc.exe and I run it every time the properties start misbehaving. Its the quickest way to reload the designer's functionality. I submitted this bug to microsoft they claim it will be included in the next update.
Me and another guy are developing a silverlight app and having the same exact problem. I accidentally found where the bug lies and how to mess with it to allow you to type "very briefly". Apparently this has something to do with tooltips. If you hover over anything in the property window when this bug is happening and allow a tooltip to popup while your cursor is blinking in a field, for the duration that the tooltip is up you can resume typing normal. As soon as the tooltip times out and disappears you can't type. So the only way you can edit or search properties is while a mouse tooltip is floating active. Very unusual. Can't seem to find any kind of tooltip settings in the program and the situation is very hard to find on google because search results assume your talking about programming tooltips. As far as I know we have had this issue since before release candidate. We are currently on official update 1 with the same problem persisting.
During openning my project in Visual Studio 2010 this issue came out.
So, how can I fix it? Can't open DataSet and contiu any other work in VS. Please, tell me what can be th ereason?
For me, the error disappeared after disabling Source Code Control integration. To disable SCC, do like this:
In the IDE Go to Tools->Options->Source Control->Plug-in Selection dialog page.
Select None from the drop-down box labeled Current Source Control plug-in:.
This issue sounds very similar to the others suggested, but I don't see it mentioned elsewhere.
My ListPicker is hosted inside a scrollviewer and a few items are added to it in design. since it's just 5 items (Title), it needs to expand - but it doesnt seem to. I need to manually regiter an event on Tap to Open() the control. once it's open , it needs to be doubletapped to close. is there a way I can prevent this behavior?
I see the same behavior in August build.
February toolkit doesn't have this issue, so if you can't to continue development with this bug, you could use an old one.
When debugging in VS I step through the code but the when I move my mouse over variables and properties it shows nothing.
For example:
If I hover my mouse over StoreId it should display the value. It doesn't though, however, if I I hover my mouse over myStore it displays the above?
It's like it cant map the properties to the object in run time.
Any ideas what's going wrong?
Thanks
Check that you haven't enabled any optimizations in the build options.
Optimizations can lead to whole variables being removed from compiled code, instructions being executed in a different order than initially expected...
This problem was addressed in the SP1 release of VS2O10, did you install it?
I am having a problem thats not about the code, it's about the screen in Microsoft visual studio 2008.
Actually problem is i created one utility from couple of weeks i didn't opened that utility today i opened (in Microsoft visual studio the screen appearing blank no controls are visible in that.But all the controls properties are there. I tried a lot but i didn't get solution. Last when the same thing happened i created the controls again. Now i don't want to go to create all the controls again. If any one have the solution please help me.
Before screen is like this:
Now its blank (like new page)
From your description I'm not sure if this is a application/code build issue or an IDE issue, what you could try is to reset the settings in visual studio and see if this helps.
You can do this by going to Tools -> Import/Export settings and then following the wizard to reset the settings, you may also want to perform a backup before resetting them (this is also part of the wizard) then they can be restored if this causes you further issues.
I don't have a copy of 2008 available at the moment so some menu entries may be slightly named different.
Hope this helps!
EDIT:
Now there is more information, this looks like there may be a problem with the code in the
InitializeComponent
method of the form.designer file (e.g. if you are using c# this would be something like Form1.Designer.cs and can be found by expanding the corresponding form in the solution explorer), if you remove/comment the lines that say
this.Controls.Add(this.NameOfControl)
(NameOfControl is where you would see your declared controls name)
then you get the behaviour that you are seeing, the controls do not render as they are never added to the forms controls collection but as they are declared you will still see them in the properties drop down and wont be able to add another control with the same name.