I'm evaluating ReactJs.Net for server side rendering and I'm a bit confused as to how you can debug the server side rendered react\javascript code. Can someone explain what the options are or point me to a resource?
Related
I am trying to implement Signalwire calling in a react-native app. I am facing issue in connecting ice servers. Sometimes it connects and calling between two persons get successful. But most of the time it throws error
"Cannot set properties of undefined (setting 'onicecandidate')"
I have tried to search a lot but could not succeed. Can you please guide me how this issue can be resolved? I am using following iceservers:
iceServers = [
{urls: ['stun:stun.l.google.com:19302','stun:stun1.l.google.com:19302','stun:stun2.l.google.com:19302']}
];
I have tried to find iceserver associated with my signalwire account but could not find, Please guide me how to get ice/turn/stun server urls and credentials. I am using Relay SDK for reactnative
It's not possible from this post to tell if you're using the SignalWire SDKs exclusively, if you're working from third party tools, or if you're doing your own setup. There are also a few variables in terms of how you've set up your app, what errors you're seeing from the SignalWire side, and the config of your ice servers.
With all that in mind, if you could reach out to SignalWire support (from your SignalWire space, select 'Help and Support' at the top right and then Submit a New Support Request) we can take a look at your setup and work through this with you.
I have this problem with VS 2019 and IIS Express: we have a setup with an ASP.NET Core web app as backend and an Angular front end. How we develop is using VS Code for Angular app (served on localhost:4200) while running backend from VS 2019 using IIS Express.
What I noticed after I upgraded to VS version 16.11.5 (wasn't updating for months prior to this) is that IIS Express won't stop after I stop debugging on VS.
For example: I hit break point in POST method on BE but I don't want to continue and I just want whole thing to end (e.g. don't want to modify my test data) however angular app makes second call to the method (because that's what it do) and request is processed.
Meaning even when I stop debugging IIS Express still goes on. This is very uncomfortable to me especially when I need to trace bug in my code without doing mess in my data. I tried many suggestions like this however without any luck.
I have a widget and a page layout that are not working as they should on the development server. The development server is hosted on Azure. On my local machine, it is working properly. I'm at a lost on what the issue is.
Does anyone have any suggestions on what to check/test? Is there any way I could test/debug this better?
I reached out to Sitefinity to support and they pointed me in the right direction. I inadvertently had the wrong namespace in the widget. Unfortunately, the widget didn't display an error message. I had to go to the log files to find the issue.
I am trying to debug client side Blazor app in Edge Chromium or even Chrome. I ran Edge with this command :
"C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe" --remote-debugging-port=9222
But when I hit the keys Shift + Alt + D
When it tries to connect :
http://localhost:64589/_framework/debug?url=http%3A%2F%2Flocalhost%3A64589%2F
I am getting this error : This localhost page can’t be found
Project is compiled in debug mode, it is actually the Blazing Pizza from the Blazor workshop provider by Microsoft.
When I just run the Blazor client project without the Server side I can actually connect to debugger but nothing happens ont the Client as the server is not running.
Any ideas ?
This question was answered in this Github Issue:
Looks like BlazingPizza.Server lacks a call to app.UseBlazorDebugging(); inside the if (env.IsDevelopment()) block in Startup.cs.
Afternoon All,
Here is my context:
I am setting up an existing worklight project with App Envs for IPhone, Android, and Mobile Web.
When using the Worklight Console to preview the apps, I get context root errors from the iPhone app only. (I get the Error: The Server was unable to process the request from the appl...)
When I open the browsers JS console, I see the problem is that the app is requesting the wrong context root. It is accessing the /worklight/ context, which is not there.
The contextroot that does work is the following:
http://localhost:8080/apps/services/api/[APPNAME]/iphone/init
The Context root that the iphone is trying to hit:
http://localhost:8080/worklight/apps/services/api/[APPNAME]/iphone/init
Here is the weird part. The context root is fine for the Android, and Mobile Web environments. Only the iPhone environment is having context root issues.
All three environments are sharing the same application-descriptor.xml file and same server.
Below are some file outputs.
Files below:
/server/conf/worklight.properties
publicWorkLightHostname=localhost
publicWorkLightProtocol=http
publicWorkLightPort=8080
publicWorkLightContext=/worklight/
/apps/[APPNAME]/application-descriptor.xml
<worklightServerRootURL>http://localhost:8080</worklightServerRootURL>
So a couple of questions.
1) When setting the context roots, what is the relationship between the client and server. Do the context roots have to match between the two? Is one a master and the other simply slaves from that and does not need settings?
2) (Somewhat unrelated) While debugging this issue I have come across zero documentation about how to go about "un-deploying" the server in the Eclipse dev ide. (un-deploy the server is right from IBM's documentation) I need to know how to redeploy the server when I make changes to the server settings (worklight.properties). I have seen references to cracking open the war manually, to just stopping and starting the server in the IDE.
Any help is greatly appreciated.
If you are using a context root, it must exist in both worklight.properties and application-descriptor.xml. make sure both match, then re-build and deploy and see if the problem persists.
When using the development edition of Worklight, your server is based on Jetty which is run within Eclipse (it is bundled with the Worklight Studio plug-in you have installed in Eclipse). You do not need to "undeploy" anything. Simply make the changes to worklight.properties and application-descriptor.xml and re-build your application. The changes will make their way to both the server and client.
Do note, though, that using a context root is mainly for when using application servers such as Tomcat, Liberty or WAS.