How to migrate your existing projects and Windows Store apps to the latest release of the Windows Library for JavaScript When you uninstall the Visual Studio Extensions for the Windows Library for JavaScript through Programs and Features, the components will be uninstalled automatically.
To optimize your setup experience, we strongly recommend that you install the latest updates and patches from Visual Studio Update and Microsoft Update and close Visual Studio before you begin installing the Visual Studio Extensions for the Windows Library for JavaScript. This release replaces the following versions of the Visual Studio Extensions for the Windows Library for JavaScript: This release supports the following version of the Windows Library for JavaScript: The installer contains resources in all languages supported by Visual Studio 2012 and Blend 2012.
For more information, see Writing code for Windows Store apps.įrom this page you can download the current version of the Visual Studio Extensions for the Windows Library for JavaScript that was installed by Visual Studio, or for use with a different development environment. The Windows Library for JavaScript is a set of JavaScript controls, objects, and helper APIs and patterns, as well as a number of CSS styles that make it easier for you to create highly responsive, reliable, and touch-enabled Windows Store apps using JavaScript, HTML, CSS, and the Windows Runtime. The Visual Studio 2012 Extensions for the Windows Library for JavaScript contain resources that enable you to more easily build Windows Store apps using Visual Studio 2012 and Blend, such as files to supplement debugging and IntelliSense, templates for projects in Visual Studio, and design-time resources for Blend. One you’ve done the pre-requisites above run your complete Bundle (or script if you’re on a different systems management product) and you should have a working installation.If you're using Visual Studio 2013 and Blend 2013, a new version is available.
Msiexec /i SSCERuntime_圆4-ENU.msi /qn End result and return codes Installation goes something like this (for an 圆4 system)
The most bizarre thing about installing SCCE is that if running a 64-bit OS you need to install the 32-bit version of the package first otherwise it won’t work! Certainly not the standard behaviour you’d expect. The easiest way around it is to install SCCE before the Visual Studio setup process and then disable it in the AdminDeployment.xml file (browse down the file and you’ll see where you can configure each component to enable \ disable the installation) We narrowed the problem down to the SQL Server Compact Edition (SCCE) component and soon found other people having the same issue, eventually confirmed by Microsoft that they had in fact borked the installer but weren’t rushing to fix it ? This is meant to get passed to each component as the setup goes along. Once this component was installed we got a bit further but then found the installation rebooted half way through with no way to stop it, not good! One issue down one to go… Issue #2 – SQL Server Compact Edition ignores norestart commandĪs you may have noticed above the Visual Studio installer runs as an exe and gives the option to suppress reboot behaviour via the /norestart parameter. $\Temp\dotnetfx45_full_x86_圆4.exe /passive /norestart Using Zenworks we copy the installer into a temporary folder to run it e.g.
Download the full installer from Microsoft then run the silent installer (you can get away with suppressing the reboot at completion). Without this installed Visual Studio is going nowhere. The installer gave us hope initially, ran for about 10 minutes then promptly fell over at the end (after you’ve tried and failed with this multiple times you’ll understand the title of the article!) After digging through logs and a spot of Googling we found the first problem… Issue #1 – you need. Next we edit the AdminDeployment.xml file to enable the NoWeb flag as per in the Microsoft instructionsįinally we run the executable with the correct switches C:\VS2012\vs_professional.exe /adminfile AdminDeployment.xml /passive /norestart In theory it seemed simple, run setup.exe and set required modifications in an XML file… but true to form there’s some irritating bugs to iron out as well.įirst step is to copy the deployment files down to the local machine (or run from network share but we had some issues with this so went local to make it more reliable) Starting off today is how to get Visual Studio 2012 to behave itself and install silently for deployment with your systems management tool of choice.
Sometimes in IT you get tasks that can drive you to the brink of madness, fortunately this series of posts should help before you end up like the chap on the right >Ĭredit for the R&D on this one go to my colleague Barry Whitehouse who had a lot of fun working on this