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: README.md
+77-23Lines changed: 77 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,5 @@
1
-
# SignalR-Web-Client
1
+
SignalR-Web-Client
2
+
======================
2
3
This is a JavaScript based SignalR Web Client.
3
4
4
5
It is a debugging tool to test ASP.Net Core SignalR hubs. This is a UI based SignalR client. Using this tool, we can send the data to the SignalR hub and receive the response from the SignalR Hub. This tool is design for dotnetcore developer to make their life easier when they work with SignalR.
@@ -8,32 +9,86 @@ It is a debugging tool to test ASP.Net Core SignalR hubs. This is a UI based Sig
2. Once the cloning is done, go inside "SignalR-Web-Client" folder.
55
+
```
56
+
cd SignalR-Web-Client
57
+
```
58
+
3. The tool need to be run under some server. This is one of the requirement of SignalR library. So, if you already have a running server, then copy the content of "SignalR-Web-Client\dist" folder and put it on your server.<br/>
59
+
If you don't have server or wants to run the tool in different server, no worry.<br/>
60
+
Will tell you two approches to run this tool.
61
+
1. Using http server(npm). Here, we will use the published files and run under the server.<br/>
62
+
```
63
+
npm install http-server -g
64
+
```
65
+
Then go to "SignalR-Web-Client\dist" folder, and run the below command:<br/>
66
+
```
67
+
http-server
68
+
```
69
+
It will start the http-server and host the application.
70
+
```
71
+
Starting up http-server, serving ./
72
+
Available on:
73
+
http://192.168.1.5:8080
74
+
http://127.0.0.1:8080
75
+
http://172.18.96.166:8080
76
+
Hit CTRL-C to stop the server
77
+
```
78
+
79
+
2. Using npm. Here, we will build the tool and then run under the server. If you wants to customize the tool, then you can you this approch.
80
+
```
81
+
npm install
82
+
npm run dev
83
+
```
84
+
It will start the webpack-dev-server and host the application.
85
+
```
86
+
> signalr-web-client@1.0.0 dev C:\demo\SignalR-Web-Client
87
+
> webpack-dev-server --content-base dist --hot --mode development
88
+
89
+
i 「wds」: Project is running at http://localhost:8080/
90
+
i 「wds」: webpack output is served from /
91
+
```
37
92
38
93
# How it works?
39
94
@@ -88,8 +143,6 @@ It has all the functionality which basic view provides, also it has additional f
88
143
89
144
<imgsrc="./src/images/2.PNG" />
90
145
91
-
## Browser Support
92
-
Currently it supports only chrome browser.
93
146
94
147
### Reporting Issues
95
148
@@ -110,16 +163,17 @@ Then, just open a [new clear and descriptive issue](../../issues/new).
0 commit comments