Open port and closed Ports on a Netgear R6080 with Powershell

excluding folders for rapid republishing of a project

Close your ASP project, open the .vbproj file with notepad and modify the following line (Target your Release build as that’s the one that gets published)

Handling WebSockets without SignalR in ASP.NET 4

Add this line to allow current connections to be accessed.

Send data from another event to trigger to all connected websockets

One last thing, you may also need to enable websockets if your on an older version of a project. Add or merge these params below into your system.web tag

And below is a sample of a test client form to use on Desktop machines to communicate with the server if needed, just update the URL to point to your source.

one thing to note, is when dealing with Websockets in this way you must avoid using .Wait on the main thread to prevent deadlocks. When the function itself is called it will halt on the first await command and never return. I think this is because the report data is being processed through the main message pump of the main thread and gets locked by using the wait() command. Its best to check the status in a loop with application.doevents and add a sleep if needed.

Other useful links on this topic I found:

Use this if you’d like to connect with powershell!

Read the Stockmarket with YahooFinanceAPI and

Using without core to trigger Events on WebClient Javascript / RawSocket Client / and Server

With the following four blocks of code you can trigger events over an open connection through (without core) to EventSource Javascript objects or .NET Think clients. Below is an example on how I tackled this issue.

This code is responsible for accepting connections both from HTTP, JS EventSource Listeners and .NET Think clients.

The code below is used to trigger from an external source to send data to both JS EventSource listeners and Raw .NET thickclients using .Net WebClient. Below is for Server -> to JS Event Source & .NETClient

This can be triggered from a web event or from a method call.

The code below allows the server to handle incoming connections from a .NET Think Client sending POST EventTriggering Data

The code below allows the client to both send and receive event data from WebClient connections.