Skip to content

Commit b7b9c0b

Browse files
committed
[mac] custom analytics metadata
1 parent 5f65546 commit b7b9c0b

10 files changed

+97
-103
lines changed

mac/create-offline-installer.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
---
22
title: "Create an Offline Installer for Visual Studio for Mac"
3-
description:
3+
description:
44
author: asb3993
55
ms.author: amburns
66
ms.date: 04/14/2017
77
ms.topic: article
8+
ms.technology: vs-ide-install
89
ms.assetid: 5CA4B8C1-2D01-46EA-A6B2-8573B324509B
910
---
1011

@@ -46,4 +47,4 @@ For basic offline installs, do the following:
4647

4748
8. Select **Build Offline Installer** to save the location of the offline installer and start building it.
4849

49-
![Start building installer](media/create-offline-installer-image6.png)
50+
![Start building installer](media/create-offline-installer-image6.png)

mac/customizing-the-ide.md

+5-11
Original file line numberDiff line numberDiff line change
@@ -87,9 +87,9 @@ Pads may also be opened automatically by various commands, such as the **Find in
8787
Pads can be moved and arranged throughout your workflow in whatever way is most useful to you. For example, they can be docked on any side of the document editor, adjacent to another pad, above or below another pad, or as a set of tabbed pads enabling you to quickly switch between them.
8888

8989
For frequently used pads, you can also completely detach a pad from the Visual Studio for Mac window, and create a separate window for that pad.
90-
90+
9191
Pads can be hidden and closed by the toggles in the top-right corner of each pad:
92-
92+
9393
![Hiding and Closing Pads](media/customizing-the-ide-image5a.png)
9494

9595
Auto-hidden pads are docked to the sides of the workspace making them easily accessible when they are required. Hovering over the pad will display it again, and it will be hidden when the mouse and keyboard focus leaves it.
@@ -111,23 +111,17 @@ However, it is possible to create a new layout by using the **View > Save Curren
111111
![Save Current Layout](media/customizing-the-ide-image6a.png)
112112

113113
### Side-by-side editing support
114-
114+
115115
Visual Studio for Mac allows you to open text editors side-by-side, or to have an editor as a detached floating window.
116116

117117
2-column mode can be enabled through the View menu item by selecting **View > Editor Columns > 2 columns**, or by dragging an editor tab to one of the edges of the editor area, as shown below:
118118

119119
![Two column side-by-side mode](media/customizing-the-ide-sbs.png)
120-
120+
121121
Editor tabs can be dragged out of the document area to create a floating editor window. This floating window also supports side-by-side editors, and can contain several editor tabs:
122122

123123
![Create new window](media/customizing-the-ide-sbs1.png)
124-
124+
125125
![Two column side-by-side with additional tabs](media/customizing-the-ide-sbs2.png)
126126

127127
To revert to a single open editor, select **View > Editor Columns > 1 column**.
128-
129-
130-
131-
132-
133-

mac/data-visualizations.md

+12-13
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ author: asb3993
55
ms.author: amburns
66
ms.date: 04/14/2017
77
ms.topic: article
8+
ms.technology: vs-ide-debug
89
ms.assetid: 527E6BEC-EF15-4002-ACB5-62AE1C16F6B7
910
---
1011

@@ -15,25 +16,25 @@ Visual Studio for Mac includes UI support for the debugger, allowing visualizati
1516
Visualizers in the debug **Local** pad can be displayed by clicking on the preview icon that appears to the right of the value, when the user hovers over the row:
1617

1718
![Local Pad](media/data-visualizations-image9.png)
18-
19+
1920
The list below looks at many of the new visualizations available when debugging in Visual Studio for Mac.
2021

2122
## Point
2223
A Point/PointF, or CGPoint in iOS and Mac, will render as a tuple showing the X and Y values in the debug pad:
2324

2425
![Point Visualization](media/data-visualizations-image10.png)
25-
26+
2627
## Size
2728
A Size/SizeF, or CGSize in iOS and Mac, will render as a rectangle. It is drawn to scale until a dimension grows past 250px, at which point it will scale the rectangle with the largest dimension as 250px:
2829

2930
![Size Visualization](media/data-visualizations-image11.png)
30-
31+
3132

3233
## Rectangle
3334
A Rectangle/RectangleF, or CGRect in iOS and Mac, will display the dimensions and origin. Similar to Size, it is drawn to scale, until a dimension grows past 250px:
3435

3536
![Rectangle Visualization](media/data-visualizations-image12.png)
36-
37+
3738
## Coordinate
3839
Coordinates are plotted on a map, with the location pinned to the center:
3940

@@ -43,21 +44,21 @@ Coordinates are plotted on a map, with the location pinned to the center:
4344
This will display UIColor, CGColor, and Color properties, depicting the color preview, RGBA components, Hue-Saturation-Lightness values, and the hex value of the color:
4445

4546
![Color Visualization](media/data-visualizations-image14.png)
46-
47+
4748

4849
## Images
4950

5051
Media will be rendered to scale, up to a maximum dimension of 250px, and will be scaled to fit when the image exceeds 250px:
5152

5253
![Image Visualization](media/data-visualizations-image15.png)
53-
54+
5455

5556
## Bezier Curves
5657

5758
The visualizer will display an `NSBezierPath`:
5859

5960
![Bezier Curve Visualization](media/data-visualizations-image16.png)
60-
61+
6162

6263
## String
6364

@@ -70,23 +71,23 @@ A string of less than 100 characters will be displayed in full, without a previe
7071

7172
### Medium-length Strings:
7273
![Medium String Visualization](media/data-visualizations-image19.png)
73-
74+
7475
### Editor:
7576

7677
![Editor Visualization](media/data-visualizations-image21.png)
77-
78+
7879
## IEnumerable
7980

8081
IEnumerable enumerates all values; the values of each can be viewed by clicking the **Show** Values button. The IEnumerable option will not display values for objects such as `Array`, `ArrayList`, `List<>`, `Dictionary<,>` as these have their own debugger visualizers.
8182

8283
![IEnumerable Visualization](media/data-visualizations-image22.png)
83-
84+
8485
## Other Visualizers
8586

8687
Some other types that also have their own inline visualizers are listed below:
8788

8889
![Other Visualization](media/data-visualizations-image23.png)
89-
90+
9091
* **Primitives**
9192
* This will show the raw value of the primitive type.
9293
* **Enum**
@@ -99,5 +100,3 @@ Some other types that also have their own inline visualizers are listed below:
99100
* This will display a clickable hyperlink.
100101
* **IntPtr**
101102
* This will display a hexadecimal representation of the IntPtr.
102-
103-

mac/debugging.md

+8-9
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ author: asb3993
55
ms.author: amburns
66
ms.date: 04/14/2017
77
ms.topic: article
8+
ms.technology: vs-ide-debug
89
ms.assetid: BB7A084D-9AC2-48B5-8076-6C8518796BBA
910
---
1011

@@ -28,7 +29,7 @@ To start debugging any application, always ensure that the configuration is set
2829

2930
![Debug configuration](media/debugging-image_0.png)
3031

31-
## Setting a breakpoint
32+
## Setting a breakpoint
3233

3334
To set a breakpoint in your IDE, click on the margin area of your editor, next to the line number of the code where you wish to break:
3435

@@ -45,26 +46,26 @@ You can view all the breakpoints that have been set in your code by going to the
4546
To start debugging, select the target device or similar/emulator in your IDE:
4647

4748
![Select target device](media/debugging-image1.png)
48-
49+
4950
Then deploy your application by pressing the **Play** button, or **Cmd + return**. When you hit a breakpoint, the code will be highlighted yellow:
5051

5152
![Highlight showing breakpoint has been hit](media/debugging-image2.png)
52-
53+
5354
Debugging tools, such as the one used to inspect the values of objects, can be used at this point to get more information about what is happening in your code:
5455

5556
![Debug visualizations](media/debugging-image3.png)
56-
57+
5758
## Conditional breakpoints
5859

5960
You can also set rules dictating the circumstances under which a breakpoint should occur, this is known as adding a *conditional breakpoint*. To set a conditional breakpoint, access the **Breakpoint Properties window**, which can be done in two ways:
6061

6162

6263
* To add a new conditional breakpoint, right-click on the editor margin, to the left of the line number for the code you wish to set a breakpoint on, and select New Breakpoint:
6364

64-
65+
6566
![Breakpoint context menu](media/debugging-image4.png)
6667

67-
* To add a condition to an existing breakpoint, right-click on the breakpoint and select **Breakpoint Properties**, or, in the **Breakpoints Pad**, select the Edit Breakpoint button illustrated below:
68+
* To add a condition to an existing breakpoint, right-click on the breakpoint and select **Breakpoint Properties**, or, in the **Breakpoints Pad**, select the Edit Breakpoint button illustrated below:
6869

6970

7071
![Edit existing Breakpoint in Breakpoints Pad](media/debugging-image5.png)
@@ -73,7 +74,7 @@ You can also set rules dictating the circumstances under which a breakpoint shou
7374
You can then enter the condition under which you want the breakpoint to occur:
7475

7576
![Edit Breakpoint conditions](media/debugging-image6.png)
76-
77+
7778
## Stepping through code
7879

7980
When a breakpoint has been reached, the Debug tools enable you to get control over the program’s execution. Visual Studio for Mac will display four buttons, allowing you to run and step through the code. In Visual Studio for Mac, they will look like the following:
@@ -96,5 +97,3 @@ Since this feature consumes more memory during debugging, it is turned off by de
9697
To enable this feature, browse to **Visual Studio for Mac > Preferences > Debugger** and ensure that the "**Debug project code only; do not step into framework code.**" option is **unselected**, as illustrated below:
9798

9899
![Do not step into framework code option](media/debugging-image8.png)
99-
100-

mac/docfx.json

+2-2
Original file line numberDiff line numberDiff line change
@@ -36,8 +36,8 @@
3636
"manager": "crdun",
3737
"ms.topic": "article",
3838
"audience": "developer",
39-
"ms.prod": "",
40-
"ms.technology": "",
39+
"ms.prod": "visual-studio-mac",
40+
"ms.technology": "vs-ide-general",
4141
"searchScope": ["Mac"]
4242
},
4343
"fileMetadata": {},

mac/extending-visual-studio-mac-walkthrough.md

+13-12
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,16 @@
11
---
2-
title: "Extending Visual Studio for Mac Walkthrough"
2+
title: "Extending Visual Studio for Mac Walkthrough"
33
author: asb3993
44
ms.author: amburns
55
ms.date: 04/14/2017
66
ms.topic: article
7+
ms.technology: vs-ide-sdk
78
ms.assetid: 7D00512B-9688-4D8D-87A7-F04F207E3D02
89
---
910

1011
# Extending Visual Studio for Mac Walkthrough
1112

12-
This topic guides you through building [a simple extension package](https://github.com/mjh4/AddIns/tree/master/DateInserter). The extension package will create a new Command in Visual Studio for Mac’s Edit menu that allows the user to insert the current date and time into an open text document.
13+
This topic guides you through building [a simple extension package](https://github.com/mjh4/AddIns/tree/master/DateInserter). The extension package will create a new Command in Visual Studio for Mac’s Edit menu that allows the user to insert the current date and time into an open text document.
1314

1415
This example uses the Add-in Maker. The Add-In Maker creates a new Project template and populates it with the required files for our custom extension package.
1516

@@ -37,7 +38,7 @@ This example uses the Add-in Maker. The Add-In Maker creates a new Project templ
3738

3839
7. Remove the template code in `Manifest.addin.xml` and replace it with the following:
3940

40-
```xml
41+
```xml
4142
<?xml version="1.0" encoding="UTF-8"?>
4243
<ExtensionModel>
4344
<Extension path = "/MonoDevelop/Ide/Commands/Edit">
@@ -78,7 +79,7 @@ This example uses the Add-in Maker. The Add-In Maker creates a new Project templ
7879

7980
}
8081
}
81-
}
82+
}
8283
```
8384

8485
We’ll expand these two placeholder methods later.
@@ -103,7 +104,7 @@ This example uses the Add-in Maker. The Add-In Maker creates a new Project templ
103104

104105
12. At this point, you should have a working extension package. You can test it out by saving your work and running the application. The IDE will launch a new instance of Visual Studio for Mac with the new extension package installed. If you navigate to the **Edit menu**, you’ll see that Visual Studio for Mac has a new option called **Insert Date**, as illustrated by the screenshot below:
105106

106-
![Insert Date Command](media/extending-visual-studio-mac-addin11.png)
107+
![Insert Date Command](media/extending-visual-studio-mac-addin11.png)
107108

108109
Note that selecting Insert Date from the menu has no effect as the current implementation only has placeholder methods.
109110

@@ -119,14 +120,14 @@ This example uses the Add-in Maker. The Add-In Maker creates a new Project templ
119120
14. Update the Command’s `Run` method to insert the date and time with the following code:
120121

121122
``` cs
122-
protected override void Run () {
123-
var editor = IdeApp.Workbench.ActiveDocument.Editor;
124-
var date = DateTime.Now.ToString ();
125-
editor.InsertAtCaret (date);
126-
127-
}
123+
protected override void Run () {
124+
var editor = IdeApp.Workbench.ActiveDocument.Editor;
125+
var date = DateTime.Now.ToString ();
126+
editor.InsertAtCaret (date);
127+
128+
}
128129
```
129130

130131
15. Finally, let’s run our extension package to test it. In the new instance of Visual Studio for Mac, select **Edit > Insert Date**. The current date and time is inserted at our caret, as illustrated by the screenshot below:
131132

132-
![Insert Date Screenshot](media/extending-visual-studio-mac-addin12.png)
133+
![Insert Date Screenshot](media/extending-visual-studio-mac-addin12.png)

0 commit comments

Comments
 (0)