When you install Rapise onto a computer that does not have Visual Studio or the Microsoft Script Debugger installed you will get a message to install the debugger. This article provides the download link to the necessary debugger.
When running or recording tests with Rapise on a computer that does not have either Visual Studio or the Microsoft Script Debugger installed, you will get this message when you try and use the ‘Internal Debugger’ option:
The solution is to download the script debugger from this location and install on the Rapise computer. You can also install a recent version of Microsoft Visual Studio if you prefer.
- Microsoft Script Debugger 10.exe
Selected files will be attached to any email sent on saving ticket.
file selected
files selected
()
Delete Selected
Select files to upload
Or drag and drop files here
Uploading
…
There was an error.
Try again?
Save to upload the selected file(s)
Spira Helps You Deliver Quality Software, Faster and With Lower Risk
And if you have any questions, please email or call us at +1 (202) 558-6885
Где скачать и как установить Debugging Tools for Windows
Решение написать данный пост появилось из-за того, что разобраться в том, где скачать Debugging Tools for Windows, не так то просто.
Так как следующую статью планируется написать на тему анализа дампов, то необходимо было облегчить для нашего читателя задачу скачивания и установки необходимого для анализа инструментария. В данном случае это только официальный отладчик Debugging Tools for Windows.
Содержание
- 1 Как скачать и установить отладчик WinDbg?
- 1.1 Скачиваем пакет SDK.
- 1.2 Устанавливаем Debugging Tools for Windows из пакета SDK на Windows 10.
Как скачать и установить отладчик WinDbg?
Отладчик Debugging Tools for Windows содержится в пакете SDK (от англ. software development kit). SDK (от англ. software development kit) — набор средств разработки, который позволяет специалистам по программному обеспечению создавать приложения для определённого пакета программ, программного обеспечения базовых средств разработки, аппаратной платформы, компьютерной системы, игровых консолей, операционных систем и прочих платформ.
Источник: WikipediaПри скачивании пакета можно выбрать только нужный вам софт отцепив всё лишнее.
Скачиваем пакет SDK.
Для каждой версии Windows имеется своя версия пакета SDK. Скачать загрузчик для скачивания пакета SDK Windows 10 можно по этой ссылке. Для остальных версий Windows загрузчик можно скачать на странице архивов Microsoft. Самая старая версия ОС здесь — Windows 7.
Про иные способы скачивания пакета можете почитать на этой странице (если конечно владеете английским языком 🙂 )
Устанавливаем Debugging Tools for Windows из пакета SDK на Windows 10.
Нажав на ссылку Скачать программу установки > вы получите файл загрузчика пакета SDK — winsdksetup.exe.
- Запустите файл загрузчика winsdksetup.exe.
- Загрузчик предложит 2 способа доставки пакета. В первом случае (Install the Windows SDK to this computer — в переводе: Установите Windows SDK на этот компьютер) выбранный софт из пакета SDK сразу устанавливается в систему. Во втором (Download the Windows SDK for installation on a separate computer — в переводе Загрузите Windows SDK для установки на отдельный компьютер) дистрибутивы для установки выбранного софта будут скачаны в указанную вами папку. Здесь рекомендую вам выбрать второй вариант, так как скачанный отладчик, можно будет потом установить и на любой другой компьютер. Тут же рекомендую сменить папку куда будет загружен пакет.
- На следующем шаге вас спросят разрешения отправить анонимную информацию об установке на серверы Microsoft или нет. Здесь выбирать вам
- Далее необходимо выбрать, что вы хотите установить из списка программ. Чтоб не устанавливать лишние программы снимаем все галочки и оставляем только одну Debugging Tools for Windows и жмем кнопку Download.
Будет загружена папка Installers, где находим файлы:
► X64 Debuggers And Tools-x86_en-us
► X64 Debuggers And Tools-x64_en-us
Прежде чем начать установку узнайте разрядность операционной системы и затем уже выберите правильную версию.
Запустив файл установки нужной версии, останется чуток подождать и Debugging Tools for Windows будет установлен. Запустить его можно через кнопку Пуск.
Теперь, когда вы знаете где скачать отладчик, можно смело приступать к анализу файла дампа. Об этом как раз и будет следующая статья на сайте.
Если вам понравилась эта статья, то пожалуйста, оцените её и поделитесь ею со своими друзьями на своей странице в социальной сети.
(4 оценок, среднее: 4,75 из 5)
Загрузка…
I encountered the same issue after I’d installed MS Office 2010 on Windows 7 HB. MS Script Editor included in Office 2000 through 2007 only. So to make debug possible you still can install it from any of that packages. The example below is for Office 2003 installer on Windows 7:
Launch the installer, choose custom type of installation:
Uncheck all applications and check choose advanced customization:
Disable all components:
Go to Office Tools — HTML Source editing — Web Scripting and select Run from My Computer option for Web Debugging item:
Then finish the rest installation process. After that you can debug the scripts with Script Editor debugger.
There is the same version of Script Editor in Office 2003 and 2007 installers that I checked:
I should say I havn’t tested that on Windiws 10, seems Office 2003 is not certified compatible with Windows 10 but might work using compatibility mode, and Office 2007 have been confirmed to be compatible.
BTW, if you are using Notepad++, it may be handy to setup shortcut for launching the script with debugger. Enter "C:WINDOWSSysWOW64cscript.exe" //x "$(FULL_CURRENT_PATH)"
into The Program to Run field while creating shortcut (you can find description here).
Download PC Repair Tool to quickly find & fix Windows errors automatically
When it comes to script debugging in Windows, you have a variety of options to do. Internet Explorer itself is a good way to carry out script debugging. Personally, I use it to debug scripts, and it works great in this field. But yesterday, my friend installed Visual Studio on my machine. Visual Studio, on its own set itself as the default debugger. Now the issue was that I was not aware of how to debug using Visual Studio at the moment. And there was some urgent debugging work I had to carry out.
So the question was, how I could deselect Visual Studio as the default debugger and choose the native Microsoft Script Debugger, in using which I was comfortable. Then I did the registry trick mentioned below which helped me significantly in achieving my objective. Using this trick, you can easily select any program as a script debugger, make sure it can do so.
1. Press Windows Key + R combination, type put Regedt32.exe in Run dialog box and hit Enter to open the Registry Editor.
2. Navigate to the following location:
HKEY_CLASSES_ROOTCLSID
3. In the left pane of this location, right-click over key CLSID and select New -> Key. Name the newly created key as:
{834128A2-51F4-11DO-8F20-00805F2CD064}
Now create the subkey to this newly created key and name it LocalServer32.
Now came to the right pane of this subkey LocalServer32 or registry location:
HKEY_CLASSES_ROOTCLSID{834128A2-51F4-11DO-8F20-00805F2CD064}LocalServer32
Double click on the (Default) string (REG_SZ) there. The Value data of this string manages the default script program for Windows. You’ll now get this:
4. In the above box, put the Value data as the file location of the program which you desire to be as default script debugger.
For example, to restore native Microsoft Script Editor, I put the Value data as C:Program FilesMicrosoft Script Debuggermsscrdlbg.exe.
Here C: is necessarily the system root drive. When you’re done inputting Value data, click OK and you may now close the Registry Editor and reboot the machine to get results.
Trust it helps you someday!
Read: A debugger has been found running in your system.
An Electrical Engineer by profession, Kapil is a Microsoft MVP and a Windows Insider MVP. Please read the entire post & the comments first & create a system restore point before making any changes to your system.
Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.
Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You’ll have a chance to have your questions answered in a live Ask Me Anything format.
Livestream from
Thursday, 06 October 2022
We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we’ve added to this release.
Watch On-Demand
Webinar Replay from
Wednesday, 30 March 2022
At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!
Watch On-Demand
Livestream from
Thursday, 9 June 2022
Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.
Watch On-Demand
Livestream from
Thursday, 04 August 2022
Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We’ll talk about some cool new features, long term asks from Customers and Community and how you can get involved!
Watch On-Demand
Livestreams from
October 2022
For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.
Watch On-Demand
Livestream from
Thursday, 03 November 2022
Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!
Watch On-Demand
Livestream from
Tuesday, 29 November 2022
Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.
Watch On-Demand
Webinar from
Tuesday, 13 December 2022
Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.
Watch On-Demand
by Radu Tyrsina
Radu Tyrsina has been a Windows fan ever since he got his first PC, a Pentium III (a monster at that time). For most of the kids of… read more
Updated on July 31, 2021
XINSTALL BY CLICKING THE DOWNLOAD FILE
This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:
- Download DriverFix (verified download file).
- Click Start Scan to find all problematic drivers.
- Click Update Drivers to get new versions and avoid system malfunctionings.
- DriverFix has been downloaded by 0 readers this month.
The Debugging Tools are essential for Windows 10 and Windows 8.1 developers that are looking to create apps and submit them to the Windows Store, free of serious bugs and glitches. Here’s more about it and where to download.
Debugging in Windows 10 / 8.1, just like with any other operating system, means to find and reduce the number of bugs and defects, to make the app behave as expected. For that, developers have at their disposal the Debugging Tools set.
With the launch of the Windows 8.1 SDK, the Debugging Tools has been made part of it, as this was one of the new features and updates brought by Microsoft.
However, if you’re interested only in the Debugging Tools for Windows 8.1, when installing the Windows 8.1 SDK, you can select only the box for Debugging Tools, leaving others unchecked. As far as we know, this is the single way to install the standalone Debugging Tools for Windows 8.1 component, as there are currently no individual download links for that.
What you can download, though, as a standalone file is the Windows Remote Debugging Client for Windows 8.1. You can use it to work remotely with developers from Microsoft by using the Kernel Debugger (KD).
Follow the links from below to download the Windows 8.1 SDK where you’ll need to check only the Debugging Tools for Windows 8.1, if you need that, and the Windows Remote Debugging Client for Windows 8.1.
- Download Debugging Tools for Windows 8.1 included in Windows 8.1 SDK
- Download Windows Remote Debugging Client for Windows 8.1
Debugging tools for Windows 10 (WindDbg)
Analyzing crash dumps, examining the CPU registers as code executes, debugging kernel and user mode code, all have been made possible with the Windows Debugger (WinDbg) for Windows 10 developers.
A new version of WinDbg was released in 2017 for Windows 10 developers and came with more modern visuals, faster windows, a full-fledged scripting experience, built with the extensible debugger data model front and center.
Read more about WinDbg Preview and find out the new features and updates.
- Download WinDbg Preview from Microsoft Store
- Get Debugging Tools for Windows 10 (from SDK)
RELATED ARTICLES TO CHECK OUT:
- Visual Studio Code gets a useful Java debugging extension
- Microsoft’s Windows PIX debugging tool now available for games
- The Project Scorpio Xbox Developer Kit is the most powerful game creation tool