You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/articles/launcher/launcher.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,3 +49,30 @@ External modules are integrated with the `<embed>` tag; the external web-page mu
49
49
}
50
50
51
51
````
52
+
53
+
### Region
54
+
55
+
To define a region in the launcher configuration, you can use the `Regions` property. This allows you to specify
56
+
which region should be loaded and where it shoud be placed in the launcher.
57
+
58
+
The region must define its own size using `css`, if that's a requirement for you. Otherwise the launcher will set an automatic size based on
59
+
the available space.
60
+
61
+
````json
62
+
{
63
+
"Regions": [
64
+
{
65
+
"Region": "Right",
66
+
"Name": "MyRegionName"
67
+
}
68
+
]
69
+
}
70
+
71
+
````
72
+
**Note**: This will work under the following conditions:
73
+
1. You have created an [ASP.net Partial View](https://learn.microsoft.com/en-us/aspnet/core/mvc/views/partial?view=aspnetcore-10.0#declare-partial-views).
74
+
2. You used the `LauncherRegionAttribute` in your partial view.
75
+
3. The name you used in your `LauncherRegion()` is the same in the configuration.
76
+
4. You have placed the partial view inside a folder called `Pages`.
77
+
5. The project in which you defined your partial view support Razor Pages and references the Launcher package or project.
0 commit comments