I have created a JavaFX 2.2 application that I am trying to deploy using web start. I singed the application with a proper certificate (not self-signed) which I actually use for another Swing application for another client of mine. I used this certificate because I still don't have the new one for this client and I wanted to test the process.
I use Netbeans 7.3, JDK 7_21 and JRE 7 _21. I pack the application using Netbeans with all the necessary settings for a web start application. I can run my application locally on my and others PCs and its working fine.
The problem starts when I upload the application on the clients website. Website link works fine, JNLP is downloaded fine but when I run it I get a Runtime error. Click here for details but there are no actual details in the console. Any ideas would be much appreciated
Thanks
Nevermind whoever took the time to read my question. I wasn't including the codebase setting in my jnlp. Added and working fine.
Thanks for your time
Related
I have basically installed the default Blazor WebAssembley template, with .Net Core server.
Ran the app, worked fine, comes with the initial migration for identity which ran and created the database tables so I could create an account login etc.
Changed 1 view file razor file and now the app will not run. In debug mode I can see the it seems to be empty, so the application falls over when it tries to connect to the DB with an empty connection string.
I just ran through the exact same steps on another machine and the same result, yet the only files changed are the appsettings.json and a razor file.
appsettings worked fine, then without changes no longer works. Any suggestions on where to investigate would be appreciated - this is my first step into .Net Core.
So just in case anyone else comes across this problem. I had the application open in another browser window, although I was not interacting with it.
Once I closed all the browser windows and ran the application again I no longer had the issue.
One thing to note, I am running IIS Express with the option "Do not start browser" so that VS does not keep closing and opening a new browser window.
I have built a web app in VS2019 that is a .netcore 2.1 application. It builds and runs fine locally in debug and release mode.
I have bought space from a hosting site on there server and have a registered a domain, they stated that they can run .netcore apps.
I have deployed the web app to the servers file server, I have used Visual studios publish functionality and used filezilla, my site is in its httpdocs folder which is where there sample html index file was before I deleted them, now in this It has the webroot folder and the dll's here.
When I look up the website online it shows a 500 error.
I have never set up this type of thing before, am I missing steps, Is there something that I have missed.
Just to note, I have looked up other similar questions regarding this but havent helped.
Assuming you are trying to host this inside IIS, you need the followings to be installed on the server. You can download the same from here.. Please make sure you choose the correct hosting bundle for your application.
Once that is installed, make sure to open IIS and create an apppool. Make sure you select No Managed code.
Then you can add the web site, and assign the above apppool to the website.
Hope this helps. Happy coding <3
I had Application Insights running smoothly on an Azure Web App via the AI SDK, reporting to an AI instance hosted in Azure.
The only niggle was it didn't show detailed dependancy diagnostics, according to this page this was because I was using the SDK only, I needed to "Instrument your web app on the server", which looking at the docs can't be done if you already have an instance of AI running....helpful!
Reluctantly I deleted the AI instance, stripped the SDK from my code so I was starting fresh, and followed the steps, however as soon as I finished the process in the previous link my website broke and now responds to every single request (MVC5 and Web API) with an empty 404 request
The AI status page is showing green ticks for everything, and I can't discern anything from diagnostic log dump from KUDO or manage to remotely debug the site.
Deleting the AI extension under Web App -> Extensions in the Azure portal and then restarting the web app fixes the problem.
I've run out of ideas on how to fix this, is there anything else I can do to get to the bottom of the problem?
To fix this problem, delete the following 2 files from your web app's (or slot's) filesystem:
D:\home\siteextensions\Microsoft.ApplicationInsights.AzureWebSites\Instrumentation32\ProductionBreakpoints_x86.config
D:\home\siteextensions\Microsoft.ApplicationInsights.AzureWebSites\Instrumentation64\ProductionBreakpoints_x64.config
You can do this easily through Kudu.
Edit: Apparently this is/was an issue with the ProductionBreakpoints interacting with precompiled views. Microsoft has informed me a fix should be out within the next couple days. The version of Application Insights extension I have now that is still broken is 2.4.6 - I will post the "fixed" version when I can confirm it.
Edit 2: Confirmed this is fixed in 2.4.7 which is out now.
I made an asp.net application on my development box which was deployed on production.
I can see my application on production URL with public domain such as https://www.myapp.com ( sample).
Is it possible to debug the application by attaching the process using from my Visual studio development environment by following - Go to debug and then attach the process by selecting the browser displaying https://www.myapp.com ?
I tried it and its attaching the process but it does not hit the debug points in VS2010 . Can anyone please let me know if its possible to do this way ?
Thanks in Advance! Junni
It sounds like you are just debugging your browser. If you want to debug a remote machine you need a debug version of your code running on that machine and MSVSMON.EXE running on the remote machine. You would be best servered by reading http://msdn.microsoft.com/en-us/library/bt727f1t.aspx
then researching MSVSMON questions here.
I've got a small WCF service I've created.
I can edit it and get it working great on the localhost, but my PC is not where this application is going to be run from. It is going to run on our Server.
However, every time I try making any kind of change to the project that points it to our server, the entire project goes to crap: I can no longer view the project in a browser and my test console application can not connect to it. I try changing it back to using the local IIS web server, but then the local machine does not start up IIS whenever the project is started so it doesn't work either.
I can debug and troubleshoot for a day or so to get it working again on the local machine, but then I'm back to Square 1 where I need to deploy my application onto our Server.
This is freakin' maddening!
My project works, but I can't seem to get it from Localhost to a real Server.
All the examples I find online show how to do this using Localhost. Does no one ever deploy their projects?
Where is the Guide for getting me from Development stage to Deploy?
Some nice tutorials here
http://www.dotnetspider.com/forum/193466-Deploy-Wcf-service-IIS.aspx
http://wcftutorial.net/WCF-IIS-Hosting.aspx
also on SO Deploy WCF Service to IIS when it only has an App.config
Also a video on youtube http://www.youtube.com/watch?v=mX8quq7MoeI