I have a VS2015 c++ project I'm trying to set preprocessor settings for.
When I open the configuration manager and change the configuration to "Debug" and then set my preprocessor setting, when I click "Apply" and then switch the configuration to "Release", release adopts whatever I set the debug setting to.
Basically, VS is refusing to let me set different settings for different configurations. Is there some "share settings" option I've accidentally enabled somewhere? How do I get VS to stop sharing settings between configurations?
I managed to get property page settings to respect their configuration by adding "condition" tags to the .vcxproj file for those settings.
So
<AdditionalDependencies>math.lib</AdditionalDependencies>
became
<AdditionalDependencies Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">math.lib</AdditionalDependencies>
Now when I open VS and switch between configurations, the settings respect their configuration.
However, if anyone knows why VS isn't automatically adding these conditions itself I'd love to hear why.
Related
Each time I restart a Run/Debug Configuration, WebStorm opens a new Tab in Chrome, which is extremely annoying. Instead it should rerun the same configuration and use the same tab.
The WebStorm-debug-config documentation says, that you need to explicitly allow such behavior by setting the Allow running in parallel checkbox, which is off in my configuration.
Is there something else I am missing to prevent WebStorm from opening new tabs?
I am using the latest Chrome and Webstorm version on Windows
I had the same problem and could not find the right settings in Webstorm,
but if this is an option you could install, for example, chrome extension: "Clutter Free - Prevent duplicate tabs". It will prevent Webstorm from opening a new tab with the same URL.
In the Clutter Free settings also check the "Refresh existing tab" this way when you rerun your app, the changes in the code will be shown, but extra tabs will not open.
The solution is far from ideal, but it is better than the annoyance.
Need help with modify 'Security Settings' in AD's GPO.
The 'Administrative template' settings are stored in corresponding ADMX files. I'm able to change these settings using IGroupPolicyObject in C++.
I couldn't find the actual storage of 'Security Settings' in Windows / Active Directory.
I am trying to get the list of settings along with any/all properties programmatically. Any leads are appreciated.
Please check the below screenshot as a reference to Security settings.
I have decided to use WebStorm it seems good however most of the time if I go to Tools - Deployment the upper menu options are greyed out? I can configure and I can go to Options but I cannot download from the server? I can open the remote host just fine and scroll through documents that way but from what I understand WebStorm loses a lot of functionality if you develop this way.
I have no Git and am just working by myself so this workflow is fine for me right now.....if I can download from the server!
In my Deployment Menu from Tools all of the tests work and I can autofind my folder and all that. Whats going on?
Here is the Mappings section:
Your Local path has to be part of your current project (root or a subfolder).
The deployment path a folder of your server where it should be stored - if it should be stored on the root it is just a slash: '/'.
If your connection is successful you should be able to select a folder with the dialog (on the right).
Make also sure your server is marked as 'default' which is your default connection for this project - based on that link.
The projects has been indexed by WebStorm so you can easily refactor and other fancy stuff.
Every project has a root folder with a config folder .idea.
For those that are convinced their mappings are set up the right way, here's one key thing to check. It seems like their SFTP usage does not follow symbolic links (on the remote) correctly. And you can see that if you go to the Mappings tab and click on the "..." for the Deployment path - when it shows the list, symlinked dirs do not show up. By avoiding symlinks in the path, I was able to get the upper part of the Tools/Deployment menu to be active again (non-grey)
I was using PyCharm Pro 2017.3
I'm setting the teamcity.build.checkoutDir configuration parameter via the 'Run Custom Build' dialog as I want to control the build location.
When looking at the 'Build Parameters' page of the build, I can see the teamcity.build.checkoutDir parameter is correctly using my set value, but the 'Actual Parameters on Agent' value always remains set to the default checkout path.
I've tried setting the Version Control Settings->Checkout Directory to Custom Path and the teamcity.build.checkoutDir parameter still does not use my custom setting.
Please can someone help me with this?
Many Thanks!
You can't change the value of teamcity.build.checkoutDir. All the teamcity.build.* variables are read-only.
You can change the checkout directory by editing the VCS root settings.
Edit the build configuration
Select Version Control Settings
Next to Checkout Directory choose 'Custom Path' from the drop-down.
You can also set a custom path by using custom client mappings for the VCS.
When we set the addAspxExtension web.config setting to true for our website, debug mode stops working for all pages of our site except for the homepage. When I say that it stops working I mean that it displays the actual page but without the Sitecore ribbon and profiling information.
I guess we could apply this setting only in our content delivery environments and leave it on (addAspxExtension="true") for our content entry environment but I was wondering if anyone has managed to get around this issue?
Update
Until Sitecore resolves this issue I have decided to only set the addAspxExtension setting to "true" in our Preview and Production environments. That way the debug mode will still work in our development environment.
As of right now, this issue is a bug that Sitecore is aware of and should hopefully be fixed by the next update. There are basically 2 workarounds for it:
Set the addAspxExtension attribute to “false” value.
Manually write the .aspx extension to other URLs which are different from the home page.
Hope that helps..