Monday, September 28, 2015

"Pending Changes” and “Source Control Explorer” missing from Team Explorer in Visual Studio 2013

To fix the issue simply run the below command in an elevated command prompt as detailed here.
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe" /setup
My understanding is this command forces the recreation (what Microsoft refers to as "merging") of current VS settings into what is apparently a corrupt settings cache. On the surface, this is similar to deleting the directory path C:\Users\username\AppData\Local\Microsoft\VisualStudio\version and allowing visual studio to recreate it at launch.
Recently I found this sometimes occurs when I launch several solutions at once (i.e. I have 1 or more Visual Studio instances loading a solution at the same time). I also have ReSharper, SQL Prompt, VSCommands and TFS Power Tools installed which I'm sure contribute to some degree.
This fix should work for all versions of Visual Studio, however you will need to execute the command in the directory appropriate to your version. For example with Visual Studio 2015 the path would be:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe" /setup

Monday, February 16, 2015

Reactive programming in WPF

Project Description
The object of this project is to create a library that offers Functional Reactive Programming abilities to common .Net languages.
With FRP your calculations automatically respond to changes in the underlying data. Obtics includes a live Object Linq and Linq to Xml.

Project Description
Continous LINQ is a .NET Framework 3.5 extension that builds on the LINQ query syntax to create continuous, self-updating result sets. 
In traditional LINQ queries, you write your query and get stale results. With Continuous LINQ, 

you write a query and the results of that query are continuously updated as changes are made to the source collection or items within the source collection. 

CLINQ has tremendous value in GUI development and is especially useful in binding to filtered streams of data such as financial or other network message data.

The Reactive Extensions (Rx) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators. Using Rx, developers represent asynchronous data streams withObservablesquery asynchronous data streams using LINQ operators, and parameterize the concurrency in the asynchronous data streams using Schedulers. Simply put, Rx = Observables + LINQ + Schedulers.
Whether you are authoring a traditional desktop or web-based application, you have to deal with asynchronous and event-based programming from time to time. Desktop applications have I/O operations and computationally expensive tasks that might take a long time to complete and potentially block other active threads. Furthermore, handling exceptions, cancellation, and synchronization is difficult and error-prone.
Using Rx, you can represent multiple asynchronous data streams (that come from diverse sources, e.g., stock quote, tweets, computer events, web service requests, etc., and subscribe to the event stream using the IObserver interface. The IObservable interface notifies the subscribed IObserver interface whenever an event occurs.
Because observable sequences are data streams, you can query them using standard LINQ query operators implemented by the Observable extension methods. Thus you can filter, project, aggregate, compose and perform time-based operations on multiple events easily by using these standard LINQ operators. In addition, there are a number of other reactive stream specific operators that allow powerful queries to be written.  Cancellation, exceptions, and synchronization are also handled gracefully by using the extension methods provided by Rx.
Rx complements and interoperates smoothly with both synchronous data streams (IEnumerable) and single-value asynchronous computations (Task).
(currently not supported)

Powered by Blogger.