Not sure if this is a problem with my build, a problem somewhere else, or not a problem at all...
I've installed the latest internal build 2009.2.724.1020 and have replaced all my Q2 2009 (2009.2.701.1020) references with references to the internal build dlls. This all looks correct, and I can see the correct build number when I look at properties of the references in VS.
However I'm doing debugging of a WCF/Web service issue using Silverlight Spy, and I noticed that the object browser of this tool, which presumably shows whats actually running inside the Silverlight app, reports all the Telerik components as the original build number.
Is this expected, or does it mean that I am not actually running the latest internal build at all?
This tool (Silverlight Spy) looks very promising by the way!
Tom
I've installed the latest internal build 2009.2.724.1020 and have replaced all my Q2 2009 (2009.2.701.1020) references with references to the internal build dlls. This all looks correct, and I can see the correct build number when I look at properties of the references in VS.
However I'm doing debugging of a WCF/Web service issue using Silverlight Spy, and I noticed that the object browser of this tool, which presumably shows whats actually running inside the Silverlight app, reports all the Telerik components as the original build number.
Is this expected, or does it mean that I am not actually running the latest internal build at all?
This tool (Silverlight Spy) looks very promising by the way!
Tom