I couldn't find anyone saying they had this problem, but this is both a question and a workaround I thought I'd share.
When I launch Test Studio and navigate in IE to our silverlight application, all I get is a white screen. (Right clicking displays the "silverlight" menu.) Looking at the log in Test Studio, it is looking for an old silverlight version that doesn't exist on my PC, I assume because the Silverlight player in IE claims that is the version it is running.
I have been able to work around this by copying the current Silverlight installation folder and duplicating it with the old version number. It eventually gets deleted by Windows updates or some other process though. Maybe I am missing something?
Installed I have
C:\Program Files (x86)\Microsoft Silverlight\5.1.20913.0\
So I copy that folder to be
C:\Program Files (x86)\Microsoft Silverlight\5.0.61118.0\
and funny enough that works, for awhile anyway. Why would the browser (IE and Chrome) want to run an old version? I asked our development team and they didn't know either.
When I launch Test Studio and navigate in IE to our silverlight application, all I get is a white screen. (Right clicking displays the "silverlight" menu.) Looking at the log in Test Studio, it is looking for an old silverlight version that doesn't exist on my PC, I assume because the Silverlight player in IE claims that is the version it is running.
I have been able to work around this by copying the current Silverlight installation folder and duplicating it with the old version number. It eventually gets deleted by Windows updates or some other process though. Maybe I am missing something?
[01/02 10:05:05,IEXPLORE.EXE(3772:1),Framework] SilverlightUtils.AppendAutomationExtension() : EXCEPTION! (see below) Situation: Unable to inject System.Windows.dll Outer Exception Type: System.IO.DirectoryNotFoundException Message: Could not find a part of the path 'C:\Program Files (x86)\Microsoft Silverlight\5.0.61118.0\System.Windows.dll'. HRESULT: 0x80070003 (Official ID (if app.) = 2147942403, Error Bit = FAILED, Facility = FACILITY_WIN32, Code = ERROR_PATH_NOT_FOUND) Call Stack: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at ArtOfTest.WebAii.Silverlight.SilverlightUtils.MemoryStreamFromFilename(String filename) at ArtOfTest.WebAii.Silverlight.SilverlightUtils.AppendAutomationExtension(MemoryStream originalXapFile, Boolean forceUpdate)Installed I have
C:\Program Files (x86)\Microsoft Silverlight\5.1.20913.0\
So I copy that folder to be
C:\Program Files (x86)\Microsoft Silverlight\5.0.61118.0\
and funny enough that works, for awhile anyway. Why would the browser (IE and Chrome) want to run an old version? I asked our development team and they didn't know either.
1 Answer, 1 is accepted
0
Hello Dan,
Thank you for the report and the information. First I'd like to clarify that it isn't the browser that's trying to run an older version of Silverlight. The error message you posted is from Test Studio while it's attempting to inject our automation hooks into your Silverlight application. Systems.Windows.dll is one of the files our automation hooks relies upon. Apparently for some reason Test Studio is looking for that file in the wrong location. Why it's doing that is a mystery.
We'd like to try and reproduce this problem so we can understand it. is there some way we can get direct access to this application (a publicly accessible URL)? If you're concerned about the sensitivity of this information you can create a support ticket (support tickets are always private) to hand us this information.
The next best thing is to get a Fiddler trace of your application running normally in a browser and send us the trace file. We can use that to simulate your web server so that we can try to reproduce the problem. Be sure to check "Decrypt HTTPS traffic" and "Store binaries" before taking the trace.
Regards,
Cody
Telerik
Thank you for the report and the information. First I'd like to clarify that it isn't the browser that's trying to run an older version of Silverlight. The error message you posted is from Test Studio while it's attempting to inject our automation hooks into your Silverlight application. Systems.Windows.dll is one of the files our automation hooks relies upon. Apparently for some reason Test Studio is looking for that file in the wrong location. Why it's doing that is a mystery.
We'd like to try and reproduce this problem so we can understand it. is there some way we can get direct access to this application (a publicly accessible URL)? If you're concerned about the sensitivity of this information you can create a support ticket (support tickets are always private) to hand us this information.
The next best thing is to get a Fiddler trace of your application running normally in a browser and send us the trace file. We can use that to simulate your web server so that we can try to reproduce the problem. Be sure to check "Decrypt HTTPS traffic" and "Store binaries" before taking the trace.
Regards,
Cody
Telerik