I'm developing an Eclipse application that allows to develop PDE modules. Note that this application has an own workspace.
I have the following question for you:
Is possible to open a GraphicalEditor in debug mode, using all plugins projects that are in the application workspace?
If yes, how can i do it?
thanks in advance
Mirko
You cannot use an instance of Eclipse debug the same instance...
But you can run a new instance of Eclipse with you extra plug-ins and debug that. Simply, select the plug-ins in question, right-click, "Debug As..." -> "Eclipse Application". You can adjust the used plug-ins and/or features later for a faster start-up...
Related
I'm using IntelliJ IDEA 2022.3 and Maven for building my project. I've set "Delegate IDE build/run actions to Maven".
Is it possible to automatically open a Build tool window when I build the project or a module?
Something like "open run/debug tool window when started" option on application run configurations.
I went with the solution floating-cat provided:
I think the IDEA doesn't have this feature. But you could try to record a macro which shows the Build tool window first and build this project.
I'm working at a colleagues PC. When I right click on a .Net Gadgeteer 4.2 project in our solution and select "Set as StartUp Project" I expect Visual Studio to set the build configurations so that the new start-up project is deployed to the device on start, as it does on my PC. But instead I need to open the configuration manager and manually deselect the previous start-up project and select the new one. Why? How can I swap (back) to using Visual Studio to manage deployment without the additional step in the configuration manager?
========== EDIT ==========
#john-saunders comment below makes me think I've misworded my question.
I have a solution containing multiple projects, many of which are .Net Gadgeteer projects.
On most of my machines if I right click on Project A in the Solution Explorer and select Set as StartUp Project then when I debug the solution (i.e. hit F5) Project A and any of its required dependencies are built and deployed to the Gadgeteer device and the debugger gets attached. If I then right click on Project B in the Solution Explorer and select Set as StartUp Project then when I debug the solution Project B and any of its required dependencies are built and deployed to the Gadgeteer device.
But on one machine this is not happening. Instead when I right click on Project B in the Solution Explorer and select Set as StartUp Project when I debug the solution Project A is deployed to the Gadgeteer device. To ensure that Project B is instead deployed I have to manually edit the configuration.
Why? How do I get this one machine to behave like the others?
I downloaded the source code of a Visual Studio 2010 project, and since I have to analyze it for my University I'd like to be able to debug with breakpoints
Problem is, my Configuration popup only shows Release as option, there is no Debug option and so my breakpoints are always ignored
This is the first time I try to use VS, I always used Eclipse as IDE and I really don't know how to solve this - I tried to search the web but it didn't help
So, how can I run a VS project in debug with my breakpoints?
Thanks in advance
If it can help, here's the project - http://scene.sourceforge.net/download.html
EDIT
If it can helps, when I try to debug in existing configuration a pop up warns me that ( loosely translated from italian, not the exact sentence ) "Debug informations related to project not found. Binary not compilated with debug informations".
A VS project can hold many configurations, not just the default Win32 Debug and Release. It's also possible to delete existing configurations which is probably your case.
You can add the Debug configuration by right clicking on the solution within VS and select Build Configuration. Select new and ask to copy from Release.
Manually change the build options to a debug build which time consuming BTW. You'll need to go over each and every option.
Is it possible to change some setting so that Visual Studio always use the "release" configuration when publishing?
I use debug mode when i develop to clear some caches and stuff like that and i also have different web.configs for release and debug. Sometimes when i publish i forget to change the configuration to release and i end up with a broken website ;)
I understand i can do this with MS Build or something but publish working fine except for this. Any tips?
In Solution Explorer, select the project.
On the View menu, click Property Pages.
Click the Build or Debug tab, in a Visual C# or a Visual F# project, the Compile or Debug tab, in a Visual Basic project, or Configuration Properties, in a Visual C++ project.
In the Configuration drop-down list, click Debug or Release."
Steps provided by:
http://msdn.microsoft.com/en-us/library/wx0123s5.aspx
As of at least VS 2017, the web publish settings now include a setting for which configuration to publish, which defaults to Release, so you can publish the release build even when VS is still in Debug configuration.
I just wish that they had also done this for regular Click-Once applications as well...
anyone knows how to do this automatically/programmatically? I mean, when I switch my solution from Debug to Release, I want my main project to change from Console to Window automatically.
I thought to use vb script, but I want to know if anyone has a better solution before.
Console/Windowed subsystem is a per-project per-configuration setting. You can change it separately for Debug & Release configurations via project properties dialog - so you can just setup your Debug/Release configurations once (the settings are stored in the project files).