Computing desk
< August 10	<< Jul \| August \| Sep >>	August 12 >

Welcome to the Wikipedia Computing Reference Desk Archives
The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages.

August 11

QuickTime for Windows 8

Is it possible to have QuickTime at Windows 8.1?--79.129.213.27 (talk) 09:13, 11 August 2014 (UTC)[reply]

It is on the Windows Store. Haven't tried it myself. -- Gadget850^talk 11:13, 11 August 2014 (UTC)[reply]

QuickTime is indeed compatible with Windows 8. So far the latest compatible version is Quicktime 7.0.4. According to the sources mentioned below. . If you are using the Quicktime plugin for an Adobe product (such as Premier Elements or Premier Pro 5+) then I would suggest using the third link that I have provided in order to verify that you version of that Adobe product is compatible with not only Windows 8, but with Quicktime 7 itself.

Below are links to three websites that confirm the answer. (1. Microsoft's own Windows Compatibility Center, 2. Apple Support Forums, 3. Adobe Support forums

 <http://www.microsoft.com/en-us/windows/compatibility/CompatCenter/ProductDetailsViewer?Type=Software&Name=QuickTime+Pro&ModelOrVersion=7&Vendor=Apple&Locale=&LastSearchTerm=&BreadcrumbPath=&TempOsid=Windows+8>

 <https://discussions.apple.com/thread/4599798>

 <https://forums.adobe.com/message/5697299>

Best J.B. Stallsworth (talk) 19:56, 28 September 2014 (UTC)[reply]

Switching from .NET 3.5 to .NET 4.0

Regarding my earlier question about implementing a custom XML serialiser in .NET WCF code, I received a suggestion about extending DataContractResolver. Now, it turns out that this whole class doesn't exist in .NET 3.5, only in .NET 4.0 and later. Visual Studio 2008, which is the latest version I have on my work computer, doesn't support it. My company might allow me to upgrade to Visual Studio 2010 (after almost a decade of using only Linux and free software at home, I'm becoming unaccustomed to the whole idea of for-pay, proprietary software, but that is beside the point). But I've found out that this will also mean upgrading the .NET Runtime from version 2.0 to version 4.0. Will this cause problems with legacy .NET or ASP.NET applications? Will they still work with the newer runtime or will they break? This is not so much a problem for me but for our customers. They are still using the old 2.0 runtime for web applications supplied by us and possibly our competitors, and I would rather want to avoid making them to abandon them. JIP | Talk 19:27, 11 August 2014 (UTC)[reply]

It should not be an issue— the application should select the version of .NET required, but I recommend testing. 3.5 is included in Windows 7, but 4.0 would have to be installed. Windows 8 includes .NET 4.5 but not 3.5. -- Gadget850^talk 21:00, 11 August 2014 (UTC)[reply]

I had a similar problem. The solution is this: http://msdn.microsoft.com/en-us/library/vstudio/a99txfy5%28v=vs.100%29.aspx In Win8.1 - Control panel - Program and Features - Turn Windows feature on/off - Enable .net 3.5 which includes 2.0 196.214.78.114 (talk) 07:20, 12 August 2014 (UTC)[reply]