I have a application deployed to a Micro Cloud Foundry instance on my local machine. I can start, stop and update the application from within STS. For some reason, the debug options are disabled when I right click on the application or the server from within STS. What am I doing wrong?
The debug feature is introduced in MCF 1.2.0. Make sure you have the correct version of MCF.
When you add your MCF as a server, you can double click on it and have it open on the window as a tab. You then need to click on the Applications tab (which is on the lower left bottom of your MCF window). You should see a list of your pushed apps. Click on any and you should see the Debug button next to the Start button appear.
There isn't any flags to be set in order for debug to appear or not. It is there in MCF 1.2.0
Related
Following the steps at https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-cpp?view=vs-2019
I have completed the steps up to where I must click the Deploy checkboxes in the Configuration Manager, but they are greyed out.
This is a legacy MFC 32 bit application.
Am I missing something?
I have completed the steps up to where I must click the Deploy
checkboxes in the Configuration Manager, but they are greyed out.
1.Please make sure you've set the Debugger to launch to Remote Windows Debugger.
2.And after my check, you should configure the Deployment Directory so that the project is deployable and the Deploy Checkbox is able to click.
3.Also, please check the Configuration and Platform you selected in Project properties and Configuration Manager, they should be corresponding to work.
e.g:
If we complete the settings in this way:
In Configuration Manager,only when we choose Debug+X86(Active Configuration and Active Platform) the Deploy checkbox is available, and if we change the X86 to X64, the checkbox would be grayed.
Hope it helps:)
In Google Cloud Platform on my Windows Virtual Machine I can't download the Opera Browser and get a message that says:
Your current security settings do not allow this file to be downloaded
And I can't press certain buttons on some websites.
What do I do?
1.Click on Server Manager.
2.Local Server.
3.Please check your IE Enhanced Security Configuration.
4.Do a test by turning it off.
5.Reactivate after download if need be.
I've started a new project with Docker support.
How do I stop a browser window from opening when I start the project in Docker mode?
I hit F5 with "Docker" displayed next to the play icon on the tool bar and I always get a browser window open.
I've been into my project settings and turned off Launch URL for all project profiles.
I've also tried going into launchSettings.json and setting "launchBrowser": false, to try and stop it from happening. Note that changing the project properties does not seem to update the launchSettings.json file (annoyingly)!
This is really frustrating as for APIs I don't want a browser window to appear each time I start debugging. In fact, I don't want it for a website either as I typically have a window open that I refresh to see the changes.
How can I turn this off?
I found how to fix it.
In the VS solution there is a docker-compose project.
Right click on the docker-compose project and select properties.
In the General tab find the Launch Browser option and set its value to No.
By default in WebStorm if you hit "Run" or use the browser hover selection, it will launch the html file using http://localhost:????. I have added a test webserver http://test.mydomain.com to the deployment configs.
How can I now debug locally again?
Would you like to have your pages hosted on http://localhost:63342 by default despite having http://test.mydomain.com set up as a deployment server?
When you are using Open in browser action, or preview a file in browser using browsers bar in editor, or create a new Run/Debug configuration from .html file right-click menu, WebStorm uses URL from current Deployment entry (which is marked as Default) to build full URL. If you have no deployment entries defined, then built-in web server (http://localhost:63342) is used.
There is a feature request to optionally use built-in webserver for previewing files in browser regardless of deployment settings, WEB-18958.
For now, I can suggest the following workarounds:
Make your deployment entry non-default (right-click, Stop using as default)
Note that it will break auto-deployment (if you have it set up)
or, use Run configuration with the built-in server URL for running your application. But, as run configurations created from right-click menu always have the default server URL pre-configured, you need to edit created configurations in Run | Edit configurations... dialog, making sure that the built-in sderver URL is specified there instead of your deployment server URL.
I'd like to debug a simple Spring Boot application in Spring Tool Suite. It is a simple restful web service. I wanted to debug the controller and service class with embedded tomcat server.
Found this post how to debug Spring MVC application on Spring Source Tool Suite. I followed the steps:
Select Window-->Show View--> Servers.
Right Click on server in the Servers panel, select "Debug".
Add breakpoints in your code
Then right click on application, Select Debug As --> Debug on Server
After the first 2 steps, the output in console shows server has started up. However, I could find option of Debug on Server when I right clicked controller class. Application class is the only class that I could debug. However there is no way to "step into" Controller from Application.
Also, when should I launch browser and put in the request url?
First of all let's see how to launch you Spring Boot app in debug mode.
As you are using Spring Boot, you don't need an app server to run or debug it, as it is able to run in standalone mode by launching the Application class.
You have at least two ways to launch it in debug mode:
Right click on your Application class and select Debug as -> Spring Boot App. Debug as -> Java application will also work.
Open the Boot Dashboard view, right click on you application and select (Re)debug).
You can have more information about the Boot dashboard in this blog post: https://spring.io/blog/2015/10/08/the-spring-boot-dashboard-in-sts-part-1-local-boot-apps
Once the application is running in debug mode or before, it really doesn't matter, open the class (in your case the Controller) you want to debug and go to the line you are interested in. To add a breakpoint at that line, right click in the grey bar at the left end of the editor in that line and select **Toggle Breakpoint*, or just use Shift+Ctrl+B.
Then you can launch the browser and use the application. When the execution gets to the line where you have added the breakpoint, it will stop there.