Silverlight SOS 5.1.40620 for WinDbg is missing - silverlight

I already downloaded the latest SDK and Runtime. The older runtime 5.1.40416 contains the SOS extension. Where do i get the current one?
Is it possible to convince WinDbg to use the old one as an alternative?

Related

Cannot open any d files

I am using Monodevelop for writing D programs, and whenever I open a file I get this error. Does anyone know about this?
It is a common problem that happens when user has an older version of MonoDevelop (now Xamarin Studio).
You have two solutions:
Get the version of Mono-D that works with the MonoDevelop version you have installed on your workstation.
Install the latest Xamarin Studio version, and the latest Mono-D.
How to do the #1 is little bit tricky - you have to find the plugin file, and follow the "install from file" procedure. It is explained somewhere on Mono-D blog and I believe there is a link to a page where you can see all versions...

iOS: Is there absolutely no way to build for armv6 in Xcode 4.5?

Starting with Xcode 4.5 the possibility of building for armv6 devices is not given anymore (iPhone/iPod touch 1st and 2nd generation). This means no new versions of our app for iPhone 2G and 3G which is very unlucky. Does anyone know if there will be a workaround? I really don´t see any technical reasons for this.
You can have multiple versions of xcode installed. In the past, that has been the fix needing to use an older xcode feature.
It is a workaround, and the project files may eventually evolve in a way that no longer supports the older tools, but for the time being, that will allow you to build for older targets.
If you have a single project that you want to work with in both versions of XCode, then you may end up having to manage separate project control files via source control tricks and/or file shuffling.
I would also recommend that project structure changes and binary file management (e.g. Core Data models) happen via the old version, as XCode 4.5 will be backward compatible, but forward compat is rarely assured.
There's another solution I found in chpwn blog: Building for armv6 in Xcode 4.5.
This allows you to work with Xcode 4.5 but compile using 5.1 SDK.
The downside: you can’t use the iOS 6 SDK when using this trick, and you can’t build for armv7s.
Yes, there are workarounds. If you need to actually take advantage of new iOS 6 features, try either of the first couple answers to this related question. The first answer requires using both Xcode 4.4 and 4.5. If you never want to have to open Xcode 4.4, then use the second answer.
If you just want to be able to build an executable in Xcode 4.5 that works on armv6, armv7 and armv7s devices, without actually taking advantage of new iOS 6 SDK APIs, then you can see my answer to another question, which is much simpler ... but has the limitation that you can't take advantage of new iOS 6 features on iOS 6 devices.
You can add the string "armv6 armv7" as architecture. Do not select a predefined setting.

Silverlight application under IE attached to Windbg

Is it possible to attach Windbg to a Silverlight based application running under internet explorer ( or any other browser)? If its possible, then will I have to attach windbg to the browser and this will get me into that mini CLR under Internet explorer?
I am not an expert on Silverlight, but you can use WinDbg with Silverlight apps in the browser with some limitations. Also, since you stop the plug-in some browsers such as Chrome will constantly complain about the plug-in not responding.
The first thing you need to do is to make sure you load the correct version of SOS. Silverlight comes with its own version and that's the one you must use. To load the correct version use the CLR module to identify the associated version of SOS. The command is
.loadby sos coreclr
Notice the CLR module is called coreclr in Silverlight.
Use the .chain command to verify that you have the correct version of SOS loaded. If you already have a version of SOS loaded make sure to clear your WinDbg workspace first.
Following that you have access to the regular SOS commands. I've had limited success using some commands such as !clrstack and !dso, but others such as !threads and !dumpheap work as expected.
If you just attach, the !clrstack and !dso commands do not work as expected. However, if you set a breakpoint using !bpmd they will work in the context of the breakpoint. This is probably due to how code is run in a Silverlight app, but as I said I am no expert on Silverlight.
This applies to Silverlight 4.
Tess has a post about debugging Silverlight 2 apps in the browser.
This long post is also worth taking a look at.

Where to get a Compiled "Windows Ribbon for WinForms 2.2"?

I am just wondering whether anyone knows where I can get a compiled version of Windows Ribbon for WinForms 2.2? I can only download the source from the website and as I don't have the Windows 7 SDK (and can't download) I can't compile it.
Even if you could download the DLL (you can't), it is not going to help you. To create your own ribbon for use in your own application you must create a ribbon markup file. That file needs to be compiled by UICC.EXE, a tool that is only available in the Windows 7 SDK. Without that tool, you cannot create your own ribbon.
Downloading the SDK is required. Note that the SDK version that comes with VS2010 is not good enough, it is a sub-set of the SDK and does not include uicc.exe

Disassembling WPF4 beta2 DLLs with Reflector

I'm trying to disassemble some of the DLL of the new WPF4 Beta2 framework. However, all I have is empty methods for all types. I'm not having this problem for other DLL (for example mscorlib).
Do you have any idea what is causing this behavior ? Is this anything to do with type forwarding (I know that some WPF types have moved in System.Xaml.dll).
Actually I found the problem (however I don't really understand it...), I was not using the right DLL.
I was using DLL in C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.0 whereas I should use C:\Windows\Microsoft.NET\Framework\v4.0.21006\WPF
I personally am not sure, but Red-Gate does have a group they watch for Reflector:http://www.red-gate.com/messageboard/viewforum.php?f=85 you might try posting there if you don't hear anything back soon.
I would imagine that the problem is the fact that this relies on some of the new features of .NET 4.0. Support for these has just been added to the latest early access build of Reflector, which you can download from here:
http://www.red-gate.com/messageboard/viewtopic.php?t=10835

Resources