In your project’s preferences, you must set the compiler –source option to 1.7 and –target option to 1.7 also. There are dedicated option boxes for that. Right-click on the project. Choose Properties. Choose Java Compiler on the left. Choose 1.7 for the Compiler Compliance level. If the 2 drop-downs below that aren’t 1.7, uncheck Use … Read more
From .Net 4.5 onwards: Use IProgress<T> Since .Net 4.5 you can handle asynchronous progress reporting with the IProgress<T> interface. You can write an extension method for downloading files using the HttpClient that can be called like this where progress is the implementation of IProgress<float> for your progress bar or other UI stuff: // Seting up … Read more
VS2017/VS2019 -> Solution Explorer -> right-click References -> “Migrate packages.config to PackageReference” VS2019 -> Solution Explorer -> right-click packages.config -> “Migrate packages.config to PackageReference” I think this happens when you add a .NET core library to a .NET standard project.
My process above still works, but it simply gets around a race condition issue, where Windows Update (yes, oddly enough) is in charge of wiping out “staged packages.” According to Microsoft, the “other fix” – and I still consider this issue to be a bug – is: Cause of the problem: Windows Update (WU) downloads … Read more
Well you need to use the value returned by the method. Do you know the type? For example, if it’s always a Task, you could use: await (Task) objType.GetTypeInfo() .GetDeclaredMethod(“ThePrivateMethod”) .Invoke(theObject, null); If you don’t know the return type but know it will be awaitable, you could use dynamic typing: await (dynamic) objType.GetTypeInfo() .GetDeclaredMethod(“ThePrivateMethod”) .Invoke(theObject, … Read more
It’s easier to directly get the CoreWindow from the non-UI thread. The following code will work everywhere, even when GetForCurrentThread() or Window.Current returns null. CoreApplication.MainView.CoreWindow.Dispatcher.RunAsync(CoreDispatcherPriority.Normal, <lambda for your code which should run on the UI thread>); for example: CoreApplication.MainView.CoreWindow.Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { // Your UI update code goes here! }); You’ll need to reference Windows.ApplicationModel.Core … Read more
This is the preferred way: Windows.ApplicationModel.Core.CoreApplication.MainView.CoreWindow.Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () => { // Your UI update code goes here! }); The advantage this has is that it gets the main CoreApplicationView and so is always available. More details here. There are two alternatives which you could use. First alternative Windows.ApplicationModel.Core.CoreApplication.GetCurrentView().CoreWindow.Dispatcher This gets the active view for the app, … Read more
Just simply uncheck Tools -> Options -> Debugging -> General -> Enable UI Debugging Tools for XAML -> Show runtime tools in application.
There’s a lot here, but here goes: Is Windows Forms (Winforms) dead? No. Its still actively supported. That said, its a horrible technology to work in (at least once you know the magic of WPF) If you want to build a nice-looking, well designed desktop (classic, not Metro) app, WPF is the answer in pure … Read more
I’m porting my existing project to Win8 right now. It consists of windows service and tray application which are talking to each other via NamedPipes WCF. As you may already know Metro doesn’t support named pipes. I ended up using TcpBinding for full duplex connection. This post describes what functionality is supported. Sample of my … Read more