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: tree_structure.md
+18-29Lines changed: 18 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,52 +12,41 @@ tr td:nth-child(2) {
12
12
# Project Structure
13
13
| Description | File Structure |
14
14
|----------------|-------------|
15
-
||┣ GitPageBlazorWASM |
16
-
| The github page is aimed at this and gets the version from gh-page branch. .Client publishes a standalone wasm site here |    ┣ docs |
| Because its a spa we need to redirect 404 back to our index page parse them to take users to pages on refresh or if they go there directly |            ┣ 404.html |
| just for making wiki style site if we decide to use the .client for testing and for creating the github page site then we dont need this |    ┣ GitPageBlazorWASMProgressive |
| Bunit and E2E tests, the E2E none javascript tests require prerendering and hence the server wasm project for testing |    ┣ PlaywrightXUnitGoesHere |
|to keep the projects slim, and if we decide to have seperate programs for creating the sites we put the site in a seperate project that everything can use, this wouldnt be packaged|    ┣ SharedPages |
|we need this for prerendering this is the same kind of set up we would use when we consume our libraries (though see MVCBlazor project for actual setup)|    ┗ TestHostPrerenderWASM |
|the client is standalone on release and used by TestHostPrerenderWASM in debug for testing. Look for the release conditions to see how it does both|            ┗ TestHostPrerenderWASM.Client |
|if we put these in wwwroot then when running debug we would have two entry points so we keep them here and copy them on publish|                    ┣ GitPagesEntryPoint |
0 commit comments