I want to give other team members solid coding practices so we minimize trouble.Īs we convert methods to be async they often also still need to be consumed by syncronous code that we lack time to refactor. Trying to keep the wheels on while we introduce async to a legacy application.
#Visual studio 2017 hotkeys not working free
Hopefully the the information I gave is enough to fix the code, If you need more information Please feel free to ask me! 'FadeOut' is not a definition on 'MainWindow'Īnyways that's the error I'm getting, Quick Note: I'm kind of new to Visual Studio and C#.^ that Bracket didn't went inside the the code thing for some reasons. Private async void Grid_Loaded(object sender, RoutedEventArgs e) Storyboard.SetTargetProperty(Animation, new PropertyPath(MarginProperty)) ThicknessAnimation Animation = new ThicknessAnimation() Public void ObjectShift(DependencyObject Object, Thickness Get, Thickness Set) Storyboard.SetTargetProperty(Fade, new PropertyPath("Opacity", 1))
Public void Fade(DependencyObject Object)ĭoubleAnimation Fade = new DoubleAnimation()
TimeSpan duration2 = TimeSpan.FromMilliseconds(1000) TimeSpan duration = TimeSpan.FromMilliseconds(500) Storyboard storyboard = new Storyboard() / Interaction logic for MainWindow.xaml Here is all the code I have type so far: using System Even though it works for my other friends. But for some reason it keeps saying 'MainWindow' does not contain a definition for 'FadeOut.'. This part of the code will make the 'Logo' Fade and after 350 ms it will Fade out. ObjectShift(Logo, Logo.Margin, new Thickness(247, 200, 0, -53)) ObjectShift(Logo, Logo.Margin, new Thickness(247, 72, 0, 0)) This is part of the code I'm getting the error from: private async void Grid_Loaded(object sender, RoutedEventArgs e) I'm trying to make a Lua Executor and I am getting this error: 'MainWindow' does not contain a definition for 'FadeOut' and no accessible extension method 'FadeOut' accepting a first argument of type 'MainWindow' could be found (are you missing a using directive or an assembly reference?) Can someone please explain how this system works. Now when right-click the file tab, I can see that the hotkey to close the document is CTRL + W, but it is still not working. I changed the hotkey combination to my desired CTRL + W and saved the changes. Now I searched hotkeys for close again and found that Window.CloseDocumentWindow is currently globally set to CTRL + F4.
The ProblemĪlmost every time I decide I need a custom hotkey I have to investigate all different scopes, because for example Text editor scope overrides Global, so if I want a Global hotkey, I have to look through other scopes, or try to guess the name of the function that overrides my custom hotkey. Assigning custom hotkey in Visual Studio is a pain in the ass and very often I can't get it working.