The SL app works just fine rendering all the pushpins only when executed thru VS2010. When I deploy the app to a local web server, the Map comes up but no data is rendered. Any ideas?
Is your silverlight application connecting to a localhost web service for the data? Have you used Fiddler to verify that your web service calls are going to the production server? This setting is in your ServiceReferences.ClientConfig file in your Silverlight project. You can also unzip your xap to verify the configuration.
Derek, yes. I have a DEV key for the map. Then I tried changing the Key type but that did not work.
Andy, yes I did use Fiddler but did not tell me anything :)
The SL app within the SLN connects to the WS as a project ref. When I deployed locally, I did deploy the SL and the WS. The WS works just fine locally (localhost). After I deployed the SL app, I had to change URL in the Service Ref file. I initially changed it to the localhost location and that is when I posted the question originally.
Then, I changed the URL to the Hosted version of the WS and it now works. So the fact that works is good; but still wondering why the SL app pointing to the working version of the WS (localhost) does not work.
Related
I’m trying to deploy a basic react app to Azure app services, but I cannot get it to work.
The app itself is the initial app created following npx create react app my-app command. I want to get this one working first before trying to deploy my actual react app.
The Azure App Service is a Linux setup, using node 16.
I’ve added “pm2 serve /home/site/wwwroot --no-daemon” as the startup command. I’ve also added PORT 3000 and WEBSITE_PORT 3000 in app settings.
Lastly I’ve added a web.config file to the react app itself.
Nothing I do seems to work though as it is not loading at all. I just get ‘application error’ if I try to open the app.
The only two errors i can see in the logs are:
“…didn't respond to HTTP pings on port: 3000” and “… did not start within expected time limit”
My deployment is set as continuous via git hub, though as this is building without an issue I think the problem must be something in the Azure App Service settings but I’m lost as to what.
Does anyone have any ideas to fix this?
It could be that there is no access to port 3000 in the app service.
It depends on how you have set it up what needs to be fixed. It could be the network settings on the app service. If your app service is on a VNET then it could be the settings on the VNET that need to be updated.
I'm trying to change the entry web page that gets launched in my Google App Engine deployment. It's a simple J2E web project, using IntelliJ with Cloud Code plugin. The default deployment points to 'index.jsp', which gets automatically created with the project. I want to change that, to point to a custom form I have built, e.g. 'form.xhtml'.
Steps I've been through so far...
Created base Google App Engine (Standard)
Configured GAE localhost
Configured GAE deployment server
I can do this easily on the localhost server, by just changing the server URL, e.g. from http://localhost:8080/ to http://localhost:8080/Ex_1.xhtml
I can't work out how to change this on the deployment server though. There's no URL option like there is with localhost. As a result, when I deploy my code it still just launches the default index.jsp.
I've looked through the GAE deployment descriptor documentation, but it doesn't mention how to do this. I'm sure it's a very simple change, I just can't put my finger on it.
Can anyone help?
I've resolved this, in case anyone else has a similar issue. You need to add the 'entry page' into web-xml, using the 'welcome-file-lists' tag. For some reason Eclipse adds this automatically but IntelliJ doesn't. If this isn't added, the App Engine deployment server points to the default index.jsp
<welcome-file-list>
<welcome-file>my-entry-page.xhtml</welcome-file>
</welcome-file-list>
I'm very new to ReactJS and am trying to test deploying to a web server.
It's just one component that says hello, to make sure everything is working.
It works fine on local host, but when I upload to my webserver, which is configured for SSL, it does not work.
Works: http://careigniter.com/x/test/
Does Not work: https://careigniter.com/x/test/
Is there something special you have to do if you are going to serve the entire app under SSL?
Thanks!
The issue is that server has wordpress and some caching, that is probably what is going on. I should have just started on a fresh server to begin with.
I'm developing a silverlight application that uses a web service. It works just fine when I run it on my local machine but when I publish it to a remote server, it fails because it is looking for a a crossdomain.xml policy at localhost:4689 instead of the websites root directory. How do I fix this?
Thanks for the help!
When you add the service reference, the host--in your case, localhost--is included as part of the generated code, and is the default endpoint when you create the service client on the Silverlight end with no constructor parameters.
Use the constructor overload of the service client class that accepts a Uri parameter to specify the correct hostname (and path to the .svc file) on your production server.
You need to edit your ServiceReferences.ClientConfig because when you deploy your project it's still using the endpoint address of your local computer.
I am having a silverlight pivotviewer control in a sharepoint page. This Pivotviewer talks to a web service hosted under sharepoint to fetch cxml/dzi/dzc. Everything is fine as long as its in http. Once on https - the CXML and dzc responses come out fine, but the dzi never happens - no images come up.Can anyone let me know why this is happening - and how to fix this?
Note: The Image directory is also under the same Sharepoint site - its a virtual directory. So even this is under ssl. If I configure the image path {for forming dzi} to another http virtual directory, everything works fine. But it simply doesn't work for a https virtual directory under the SP site.
This should definitely work as I've done exactly that (using https) for http://percollate.com. Is it possible that https is bound to something unexpected on your IIS server? Have you tried using Fiddler to see what's happening?