Is it possible to import Visual Studio Power Tools settings? - import

Recently I've upgraded from VS2013 to VS2015. I've imported my settings file from 13 to 15. Now I would like to import my settings for the extension 'Visual Studio Power Tools'. Specifically the document well regex settings. I use this to color my tabs differently in each of my three environments, for each of the file types. I was able to find where these settings are stored thanks to this question:
Visual Studio Productivity Power Tools configuration settings
I've located these settings, but now my question is: how do I import them into VS2015? I'm not very experienced messing with the registry and don't want to muck something up. So far I was able to export the specific reg settings for my VS2013 colors. I also found the location of the color settings folder (in the registry) for vs2015. Is it possible to somehow take that .reg file I exported and import it into the settings for vs2015? Thanks for any help. It's greatly appreciated!
Edit: So it's been a week or so and I've gotten no responses to the question :(
I suppose another way to ask this would be: "is there a way to import registry settings?"

In Visual Studio 2015 those settings are stored under a registry key:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\DialogPage
Assuming that the plugin didn't change the way its color settings are stored, it should be enough to edit the .reg file that you exported from Visual Studio 2013 in a chosen text editor (notepad.exe will do) and replace all ocurrences of \12.0\ (which is version number of VS2013) with \14.0\ (which is version number of VS2015).
Then you may open the .reg file to import settings.
By the way, if you would like to include registry settings like this in your backup plan, you might easily export registry keys from a command line with something like:
regedit /e d:\VSPowerToolsColorSettingsBackup.reg "HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\DialogPage"

Related

PhpStorm Formatter failed to format the document

Similar questions have been asked, but what makes mine different is that I seem to have the configuration correct. Here is my configuration (my name has been redacted, for privacy reasons).
What I know is that my PhpStorm IDE has not been activated yet; is that required or is my configuration incorrect, despite the folder and file being at these places?
So you're trying to use PhpStorm from within VSCode to format your files. Which means: calling PhpStorm as a command-line app.
I'm pretty sure that PhpStorm has to have a valid active licence or be in the evaluation period (so it has be "activated" in some way). I remember seeing tickets with similar issue when using PhpStorm for code inspections in Continuous Integration tools.
In any case:
Check what command VSCode is trying to execute here, then open your OS console and try to run it there -- will you see any errors/warnings in the output?
If you do not see any such messages there then check the idea.log file -- the IDE will write everything there for sure.
On Windows it would normally be in the C:\Users\USERNAME\AppData\Local\JetBrains\PhpStorm2022.2\log folder (for the current 2022.2 version). Other OS / cusom location -- check https://www.jetbrains.com/help/phpstorm/directories-used-by-the-ide-to-store-settings-caches-plugins-and-logs.html#logs-directory
...or is my configuration incorrect, despite the folder and file being at these places?
As per docs the Code Style settings file can be located anywhere: it can be in the default place as well as any other as it can be passed as an argument in the command line (-s parameter). So keeping the file with Code Style settings in the VSCode extension folder is OK as long as that parameter is used.

Visual Studio Code debug mode issue

I'm sorry to bother , I don't know if I can ask this
Visual Studio Code, suddenly can't use debug mode to set interrupts to test.
It seems that it is talking about the folder name problem, but after accessing the folder, it will not be renamed. How can I solve it now? I can't upload photos so I'm capturing the important parts.
i.e.: the module "queue" could not be imported because it is shadowed by:
/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/queue/__init__.pyc
Please rename this file/folder so that the original module from the standard library can be imported.
Not sure how to change folder name or duplicate name, these actions are forbidden after accessing the folder, or is this some other problem?
This looks like an actual issue in VSCode - https://github.com/microsoft/debugpy/issues/886
In case you're using python 2.7, Downgrading the python VSCode extension should help.

How to Import/Export live code template in android studio?

In Eclipse there is simply option to import or export code template. I want to do same in android studio but there is not any direction option to do so.
I have create one template and now i want to apply it to all my other system so i need to export & import.
I have one option to do but i just want to know that is any other way to do.
Create your code template file in eclipse and export.
Exported file will be XML.
Now copy that XML file and move to ..//.AndroidStudio/config/templates
Restart Studio and Use it.
Can you please help me out.
Thanks for your time.
System-independent solution:
Go to File -> Export Settings, choose only Live templates, and export it to a file.
Then you can use File -> Import Settings and provide this file to import live templates.
(I haven't tested it myself so I'm not sure how exactly the Import Settings works. I don't know if it merges the settings with your current ones or swaps it entirely. Bare that in mind when trying...)
System-specific solutions:
Mac OS:
Go to /Users/<username>/Library/AndroidStudioX.X/templates/.
There's where user.xml file containing your Live Templates should be.
Linux:
The templates are saved inside ~/.AndroidStudioX.X/config/templates/Android.xml

How to avoid necessity of writable .vbg in Visual Studio 6?

I have a Project Group in Visual Studio 6 (.vbg). The projects are under source control (TFS). When I start debugging Visual studio there is an error Path/file access error: Path/name.vbg and dialog for "Save Project Group As" follows when canceled debugging runs without problems. To circumvent this annoyance I need to have the group file checked out or mark as readable just by file attribute. Is there a way how to avoid this behavior?
Notes: Situation was the same when Visual Source Safe was used. By my observation .vbg is not changed when the change is allowed. The problem can be connected with using English Windows with non English regional settings.
No. Just keep the VBG in version control, and make the files read-write in your local directory.
The easiest solution would be for you to save your VBG files to a folder outside of source control. It won't make a difference to the running directory - that is based on the EXE project (if any).

How to determine if a build is from the editor or command line?

I am building a C++ solution with Visual Studio 2005.
Sometimes I open the solution in Visual Studio and build it from within the development environment. Other times I build it from the command line using msbuild.exe. I'm wondering if there is a way that I can determine which of these two types of builds I'm using at compile time (for example, a macro or something like like that). I want to change the path of my output files based on this determination. So, if I'm building from within Visual Studio I would put my output files in FolderA but if I'm building from the command line I would put my output files in FolderB. Is this possible?
Perhaps you can pass in a command-line parameter when building from the command-line that would indicate you are building the solution from the command-line. Otherwise, you can assume you are building from within Visual Studio.
I don't have the answer to your general question, but in order to change the output path, have you thought of adding project configurations ? You could copy project configurations and update the output path of the new ones.