Skip to content

Commit 275a64c

Browse files
author
Greg Van Liew
committed
Revert "Merge pull request #265 from preemptive/jpierce/unity-dotfuscator"
This reverts commit f807f1b, reversing changes made to cffb0d4.
1 parent f807f1b commit 275a64c

File tree

2 files changed

+7
-14
lines changed

2 files changed

+7
-14
lines changed

docs/cross-platform/using-visual-studio-tools-for-unity.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Using Visual Studio Tools for Unity | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "07/06/2017"
4+
ms.date: "11/04/2016"
55
ms.reviewer: ""
66
ms.suite: ""
77
ms.technology:
@@ -29,7 +29,7 @@ translation.priority.ht:
2929
- "zh-tw"
3030
---
3131
# Using Visual Studio Tools for Unity
32-
In this section, you'll learn how to use Visual Studio Tools for Unity's integration and productivity features, how to use the Visual Studio debugger for Unity development, and how to use Dotfuscator to protect Unity apps from piracy and tampering.
32+
In this section, you'll learn how to use Visual Studio Tools for Unity's integration and productivity features, and how to use the Visual Studio debugger for Unity development.
3333

3434
## Unity Integration and Productivity
3535
Visual Studio Tools for Unity integrates with the Unity Editor to help you be more productive. These productivity-enhancing features automate common scripting tasks and bring information from Unity into Visual Studio so that you don't have to switch to the Unity Editor to find it.
@@ -196,11 +196,4 @@ In this section, you'll learn how to use Visual Studio Tools for Unity's integra
196196

197197
The PDB files are needed for debugging because they contain the DLL's debugging symbols, and map the DLL code to its source code form. Visual Studio Tools for Unity will use information from the DLL and PDB to create a DLL.MDB file, which is the debug symbol format used by the Unity scripting engine.
198198

199-
4. Debug your code. You can now debug your DLL source code together with your Unity project's source code, and use all the debugging features you are used to, such as breakpoints and stepping through code.
200-
201-
## Unity Protection with Dotfuscator
202-
203-
As with all platforms that use intermediate code, the compiled C# code in Unity apps is susceptible to reverse engineering and tampering, which can result in piracy and intellectual property theft. To help mitigate these threats, Visual Studio includes a free obfuscation utility, [PreEmptive Protection - Dotfuscator](https://www.preemptive.com/products/dotfuscator/overview), which can protect Unity apps that target Android, iOS, UWP, and desktop platforms.
204-
205-
To start using Dotfuscator to protect Unity apps, see [the instructions in the Dotfuscator User Guide](https://www.preemptive.com/dotfuscator/pro/userguide/en/getting_started_unity3D.html). Depending on your Visual Studio version, you may need to install the latest version of Dotfuscator, available on the [PreEmptive Solutions Dotfuscator Downloads page](https://www.preemptive.com/products/dotfuscator/downloads).
206-
199+
4. Debug your code. You can now debug your DLL source code together with your Unity project's source code, and use all the debugging features you are used to, such as breakpoints and stepping through code.

docs/cross-platform/visual-studio-tools-for-unity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Visual Studio Tools for Unity | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "07/06/2017"
4+
ms.date: "11/04/2016"
55
ms.reviewer: ""
66
ms.suite: ""
77
ms.technology:
@@ -47,8 +47,8 @@ In this section, you'll learn about Visual Studio Tools for Unity, a free Visual
4747
[Getting Started](../cross-platform/getting-started-with-visual-studio-tools-for-unity.md)
4848
In this section, you'll learn how to install Visual Studio Tools for Unity for your version of Visual Studio, and how to start using Visual Studio with your Unity project.
4949

50-
[Using Visual Studio Tools for Unity](../cross-platform/using-visual-studio-tools-for-unity.md)
51-
In this section, you'll learn how to use Visual Studio Tools for Unity's integration and productivity features, how to use the Visual Studio debugger for Unity development, and how to use Dotfuscator to protect Unity apps from piracy and tampering.
50+
[Using Visual Studio Tools for Unity](../cross-platform/using-visual-studio-tools-for-unity.md)
51+
In this section, you'll learn how to use Visual Studio Tools for Unity's integration and productivity features, and how to use the Visual Studio debugger for Unity development.
5252

5353
[Programming Visual Studio Tools for Unity](../cross-platform/programming-visual-studio-tools-for-unity.md)
5454
In this section, you'll find examples for using the Visual Studio Tools for Unity API.
@@ -57,4 +57,4 @@ In this section, you'll learn how to use Visual Studio Tools for Unity's integra
5757
In this section, you'll find solutions to common issues with Visual Studio Tools for Unity, descriptions of known issues, and learn how you can help improve Visual Studio Tools for Unity by reporting errors.
5858

5959
[Change Log](../cross-platform/change-log-visual-studio-tools-for-unity.md)
60-
In this section, you'll learn about new features, bug fixes, and other changes in each version of Visual Studio Tools for Unity.
60+
In this section, you'll learn about new features, bug fixes, and other changes in each version of Visual Studio Tools for Unity.

0 commit comments

Comments
 (0)