The final release of Visual Studio 2013 became available for download on October 17, 2013, along with .NET 4.5.1. Visual Studio 2013 officially launched on November 13, 2013, at a virtual launch event keynoted by S. Somasegar and hosted on events.visualstudio.com. \"Visual Studio 2013 Update 1\" (Visual Studio 2013.1) was released on January 20, 2014.Visual Studio 2013.1 is a targeted update that addresses some key areas of customer feedback.\"Visual Studio 2013 Update 2\" (Visual Studio 2013.2) was released on May 12, 2014.Visual Studio 2013 Update 3 was released on August 4, 2014. With this update, Visual Studio provides an option to disable the all-caps menus, which was introduced in VS2012.\"Visual Studio 2013 Update 4\" (Visual Studio 2013.4) was released on November 12, 2014.\"Visual Studio 2013 Update 5\" (Visual Studio 2013.5) was released on July 20, 2015.
Boost your productivity with cost-effective, easy-to-use automation software that transforms virtually any business or IT process and brings together the applications that keep your business running.
Verify that the Office application that you want to automate is installed on the local computer. Make sure that you can run the application. To do this, click Start, clickRun, and then try to run the application. If you cannot run the application manually, the application will not work through automation.
Test for possible corruption of the Normal.dot template or of the Excel.xlb resource file. Problems may occur when you automate Microsoft Word or Microsoft Excel if either the Normal.dot template in Word or the Excel.xlb resource file in Excel is corrupted. To test these files, search the local hard disks for all instances of Normal.dot or of Excel.xlb.Note You may find multiple copies of these files. There is one copy of each of these files for each user profile that is installed on the system.Temporarily rename the Normal.dot files or the Excel.xlb files, and then rerun your automation test. Word and Excel both create these files if they cannot find them. Verify that the code works. If the code works when a new Normal.dot file is created, delete the files that you renamed. These files are corrupted. If the code does not work, you must revert these files to their original file names to save any custom settings that are saved in these files.
Examine the version numbers for the OLE system files that manage automation. These files are typically installed as a set. These files must match build numbers. An incorrectly configured setup utility can mistakenly install the files separately. This causes the files to be mismatched. To avoid problems in automation, examine the files to make sure that the files builds are matched.The automation files are located in the Windows\\System32 directory. Examine the following files.
To examine the file version, right-click the file in Windows Explorer, and then click Properties. Note the last four digits of the file version (the build number) and the date that the file was last modified. Make sure that these values are the same for all the automation files.Note The following files are for Windows 10 Version 1709, build 16299.431. These numbers and dates are examples only. Your values may be different. 1e1e36bf2d