private void RunAsync() { //Beware of closures. String is immutable. string param = “Hi”; Task.Run(() => MethodWithParameter(param)); } private void MethodWithParameter(string param) { //Do stuff } Edit Due to popular demand I must note that the Task launched will run in parallel with the calling thread. Assuming the default TaskScheduler this will use the .NET … Read more
For me, such tags are enabled by default. You can configure which task tags should be used in the workspace options: Java > Compiler > Task tags Check if they are enabled in this location, and that should be enough to have them appear in the Task list (or the Markers view). Extra note: reinstalling … Read more
I agree that using async/await is the best approach here. As noted, when you await an async method, then even though the declared return type is a Task<T>, the compiler translates this into an implicit return type of T. The gotcha is that all async methods must return void, Task, or Task<T>. So once you … Read more
Maybe public async Task<Task[]> RejectFailedFrom(params Task[] tasks) { try { await Task.WhenAll(tasks); } catch(Exception exception) { // Handle failed tasks maybe } return tasks.Where(task => task.Status == TaskStatus.RanToCompletion).ToArray(); } Usage var tasks = new[] { Task.FromResult(1), Task.FromException<int>(new ArgumentException(“fail1”)), Task.FromException<int>(new ArgumentException(“fail2”)) }; var succeed = await RejectFailedFrom(tasks); // [ tasks[0] ]
Note: The following applies to VS2010 and publishing web-application projects with the “Web Deploy” publish method selected in the ‘Build/Publish {projectname}’ dialog. Julien Hoarau’s correct in that “Publish” is NOT the name of the msbuild target invoked in the above case; the actual target name is “MSDeployPublish”. Therefore, you have to define a “Target” element … Read more
In a nutshell, Automatic Task Killers work by polling the OS for a list of currently running processes and the memory they are consuming. Then either with an intelligent algorithm or with user input the Task Killers issue a call to the system telling the system to kill the process. There are two apis you … Read more
Queue.task_done is not there for the workers’ benefit. It is there to support Queue.join. If I give you a box of work assignments, do I care about when you’ve taken everything out of the box? No. I care about when the work is done. Looking at an empty box doesn’t tell me that. You and … Read more
The idea of using Task.Wait will do the trick but will cause the calling thread to (as the code says) wait and therefore block until the task has finalized, which effectively makes the code synchronous instead of async. Instead use the Task.ContinueWith option to achieve results: Task.Run(() => { //do some work }).ContinueWith((t) => { … Read more
As puce says, you have to use Task or Service for the things that you need to do in background. And Platform.runLater to do things in the JavaFX Application thread from the background thread. You have to synchronize them, and one of the ways to do that is using the class CountDownLatch. Here is an … Read more
Oh, I think I’ve found the answer. Because I was launching the app by using IntelliJ, it seems it launches the application in a different way than a user, clicking a home screen widget, would launch. It’s explained in the answer to another SO question: This is due to the intents being used to start … Read more