Skip to content

Commit 3011681

Browse files
authored
Update README.md
1 parent f2eab49 commit 3011681

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

README.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,25 @@
1-
# Plugin based .NET Core Blazor Demo
1+
# Plugin based .NET Core 3 Blazor Demo
22
This project shows the possibility to load external razor libs as plugins to a Blazor App.
33

44
# Goals
55
The aim was to be able to load external assemblies into existing app and be able to use razor pages and components defined in those libs. I also took the time to investigate patterns for moving the layout files into a common lib (Layout), That way if I was to create another host (Razor web app) i could reuse the layout and have a seamless look and feel between the apps.
66

7-
## Solution projects
7+
## Blazor Demo
88
- Host1 (Website)
9-
- McMaster.NETCore.Plugins (External, https://github.com/natemcmaster/DotNetCorePlugins)
10-
- McMaster.NETCore.Plugins.Mvc (External, https://github.com/natemcmaster/DotNetCorePlugins)
11-
- Layout
12-
- HostBase (Library)
13-
- PluginBase (Library)
14-
- Plugins (Folder)
15-
- Plugin1 (Razor library)
16-
- plugin2 (Razor library)
9+
- McMaster.NETCore.Plugins (External, https://github.com/natemcmaster/DotNetCorePlugins)
10+
- McMaster.NETCore.Plugins.Mvc (External, https://github.com/natemcmaster/DotNetCorePlugins)
11+
- Layout (Razor library)
12+
- HostBase (Library)
13+
- PluginBase (Library)
14+
- Plugin1 (Razor library)
15+
- Plugin2 (Razor library)
1716

1817
# How to run
1918
Build solution
2019
- Plugin1 and Plugin2 have AfterBuild targets to CopyOutputToDestination "Host1\Plugins"
2120

2221
Set Startup Projects to "Host1"
2322
Run application using, Run->Host1.
23+
24+
#Prerequisites
25+
- .NET Core 3 SDK

0 commit comments

Comments
 (0)