c#-5.0

I have few hundreds of files i need to upload to Azure Blob Storage. I want to use parallel task library. But instead of running all the 100 threads to upload in a foreach on list of files, how can i put a limit on max number of threads that it can use and finish the job in parallel. or does it balance the things automatically? You should not be using threads for this at all. There's a Task -based API for this, which is naturally asynchronous: CloudBlockBlob.UploadFromFileAsync . Use it with async/await and SemaphoreSlim to throttle the number of parallel uploads. Example (untested): const MAX

Given a standard view model implementation, when a property changes, is there any way to determine the originator of the change? In other words, in the following view model, I would like the "sender" argument of the "PropertyChanged" event to be the actual object that called the Prop1 setter: public class ViewModel : INotifyPropertyChanged { public double Prop1 { get { return _prop1; } set { if (_prop1 == value) return; _prop1 = value; // here, can I determine the sender? RaisePropertyChanged(propertyName: "Prop1", sender: this); } } private double _prop1; // TODO implement

This question already has an answer here: Is it possible to replace a reference to a strongly-named assembly with a “weak” reference? 3 answers I am developing a class library ( MyClassLibrary ). I depend on a third party class library ( ThirdPartyClassLibrary ). I need to use the same version of ThirdPartyClassLibrary as my users. e.g., if I set a static value in ThirdPartyClassLibrary the user needs to see that change. Users of my class may be depending on any one of 4 different versions of ThirdPartyClassLibrary . ThirdPartyClassLibrary is large, I do not want to distribute it with my

I have a method that produces an array of tasks ( See my previous post about threading ) and at the end of this method I have the following options: await Task.WhenAll(tasks); // done in a method marked with async Task.WhenAll(tasks).Wait(); // done in any type of method Task.WaitAll(tasks); Basically I am wanting to know what the difference between the two whenall s are as the first one doesn't seem to wait until tasks are completed where as the second one does, but I'm not wanting to use the second one if it's not asynchronus. I have included the third option as I understand that this will

I have an async method inside a portable class library with this signature: private async Task<T> _Fetch<T>(Uri uri) It fetches a resource that is cast back as a concrete type T. I'm working with a 3rd party cache library ( Akavache ) that requires a Func<T> as one of the parameters and have tried to do so in this manner: await this.CacheProvider.GetOrCreateObject<T>(key, async () => await _Fetch<T>(uri), cacheExpiry); This results in the error: Cannot convert async lambda expression to delegate type ' System.Func<T> '. An async lambda expression may return void , Task or Task<T> , none of