Previously WPF Performance Suite was part of Windows SDK.
I have Windows 10 and VS 2015 Update 3.
This page https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk says: Windows 10 SDK is available with VS Update 3.
I can see Windows Performance tools (WPA) but not WPF Performance Suite.
Here is what I have in my apps on Windows..
I just installed Visual Studio 2013 Community Edition on Windows 8 and when I go to create a new project, all the apps I see are for Silverlight.
Is this how it should be or did I miss some SDK or something?
You can't target WP8.1 on Windows 8 - you need Windows 8.1.
WinRT apps (i.e. non-Silverlight) on Windows Phone are only compatible with Windows Phone 8.1.
Upgrade Windows to 8.1, and make sure you also have the latest WP8.1 SDK installed.
Basically your dev machine's Windows version must at least match the target Windows version (including Windows Phone).
I've some time lately trying to find a clear answer for updating some of my desktop applications to run on Windows 8.1 (Desktop/laptop and Surface). So far everything I am finding is pointing toward developing for the Windows Store where the application then could be downloaded.
Heres my development Environment:
Windows 7 Ultimate
MS Visual Studio 2012 Premium
MS Visual Studio 2013 Express
My test environment consist of:
Windows 8.1 Surface Tablet
Windows 8.1 Laptop
When I build something now (retargeted to the newer framework (4.5 (4.5.1 is installed)) and copy it over to these devices and try to run them I get an error that the indicates "This app can't run on your PC" "To find apps for this PC, open the Windows Store.". This isn't really what I want to do, I just want to make he applications we use on a day to day basis in my retail store availible to the new computers.
A couple of questions come to mind;
Does the development environment need to be a Windows 8.1 based environment?
Do I need to again buy a new version of Visual Studio (Visual Studio 2013)?
Am I stuck using the Windows Store to deploy applications?
If anyone could point me in the right direction as to where to read or provide some insight tho cross this hurdle would surely save alot of repeated reading about how great the store is.
A Surface tablet does not permit running desktop apps. You can only run apps that are downloaded from the Store. So scratch the idea that your Winforms app is going to work on the tablet. There isn't any good reason why it would not work on the laptop, they work fine on mine.
Does the development environment need to be a Windows 8.1 based environment?
Yes, for VS2013. For VS2012 it needs to be at least 8.0
Do I need to again buy a new version of Visual Studio (Visual Studio 2013)?
You didn't buy VS2013, you do need the correct version of Express. There are several. You need the "Express 2013 for Windows" edition, it only supports developing apps for the Store. You probably have the "Express 2013 for Windows Desktop" edition, it only supports desktop apps and supports Winforms. The retail edition supports all targets. The Express editions were split to keep them small.
Am I stuck using the Windows Store to deploy applications?
If you develop Store apps, yes. You get a temporary license to develop the app but it expires after a month. If you need more time then you get just another license. But the app needs to be certified to obtain a permanent license so it can run permanently on the Surface machine. And everybody else's.
I've compiled my WPF project on Windows 7 64-bit, using VS 2010 and .NET 4. I have compiled it as a 32-bit application, of course, and it works fine in both 32- and 64-bit versions of Windows Vista/7.
But in Windows XP SP2 32-bit, I get an error:
wpfApp has encountered a problem and needs to close. We are sorry for the inconvenience."
How can I fix this so that my application will run on Windows XP?
.NET 4 requires Windows XP Service Pack 3.
Either upgrade to SP3, or downgrade your project to target .NET 3.5.
In all of my searching, I've only been able to find this one link that suggests the old CLR Profiler for .NET 2.0 should work with .NET 3.0 or 3.5 applications.
When I try and profile my .NET 3.5 SP1 WPF application with the CLR Profiler for .NET 2.0 it starts up my application just fine, but it throws up a dialog that says "Waiting for application to start common language runtime".
Since my application clearly uses the CLR, I can only conclude that the CLR Profiler for .NET 2.0 does not work with newer versions of the framework (maybe it's just a problem with 3.5 SP1 apps).
So, does anyone know if there is a version of the CLR profiler that works with 3.5 SP1? If there isn't a version of Microsoft's profiler, is there another free profiler that I could use that has similar functionality?
I just tried running CLR Profiler with a WPF application, and it works fine. It takes a while for the application to start (longer than with non-WPF applications, it feels like), but it works.
Update: just to keep the answer up to date; according to the comments below, the solution was to run the CLR Profiler with administrative rights.
CLR Profiler 4 is released by microsoft on Jan 31, 2011.
This version supports .NET frameworks 2.0 to 4.0 as well as support for WPF and Silverlight.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=be2d842b-fdce-4600-8d32-a3cf74fda5e1
Note that it requires .NET framework 4.
Regards
The CLR used in 2.0 framework and 3.5 framework differs only by a service pack. The CLR has the version 2.0 and 2.0SP1 for the respective versions. The CLR profiler will work against the 2.0SP1 version of the CLR.
Small Correction: There is no 3.5 version of the CLR. The most recent versions are 2.0, 2.0SP1 and 2.0SP2 (associated with .Net Framework SP1).
I've just used the CLR profiler 2 with my .NET 4.0 WPF application. It could launch the App but when click on "Show Heap Now" or any items under "View" menu it showed report windows with empty figures. So I wonder if anyone already tried it successfully? Or it is just not supports for .NET WPF apps.
I made the mistake of running the x86 version of CLR Profiler for .NET Framework 2 on my 64-bit machine, which just showed the "Waiting for application to start common language runtime" message permanently. If you have a 64-bit machine, you probably have to run the version of CLR Profiler that matches the process you want to profile (i.e. normally the one in the "x64" folder)
For some reason WPF is extremely slow under the profiler.
Don't make the stupid mistake I did and try to use CLR profiler v1.1 – the correct one is CLR Profiler for .NET Framework 2.0 (even if you use .NET 3.5).