App-V and .NET Performance
This post is about the performance impacts of combining Microsoft App-V 5 sequenced virtual applications with applications that use Microsoft .Net. I wish this story ended with good news, or at least reasonable actions that you could take to improve performance, but it isn’t so. Instead it is mostly informational, however, in the end there is a technique mentioned that might be useful for a really poorly performing app. In the most typical cases the trick is probably too much work for the performance gains that you might receive, but maybe it can help you if you are stuck with user’s complaining about the runtime performance. So here is the story (so far).
Background on .Net
Like Java, Microsoft .Net programs are constructed with the concept of “write once, run anywhere”. Except anywhere means places where you have the supporting runtime. For Java, this means the appropriateJava Runtime (which can be placed about everywhere), and with .Net it means the appropriate .Net Framework (more limited currently, but now it might be coming to other OSs). But while Java may run on more CPU architectures and OS platforms, .Net tends to have much fewer version incompatibilities. Both programing languages achieve processor independence by compiling into a processor independent language. This is called MSIL (Microsoft Independent Language) in “.Net-speak”.
Read the entire article here, App-V and .NET Performance