When I use "Batch Build" in Visual Studio 2010 and select specific build and platform options there - in which file is this information stored?
I'm asking this because I have to add this file to version control system in order to not to configure the same again and again.
Solved, these information are stored in .suo file.
Related
We're working in quite a large project and is having a hard time getting people to configure their Visual Studio correct (tabs instead of spaces etc.). We found a great solution in using the EditorConfig extension for Visual Studio.
However there are still some developers that seems to ignore our request to install this extension to their Visual Studio and hence I'm wondering if there is any way to force an extension to be installed before a solution can be opened, maybe some setting in the .sln file?
No there is no such option built-in. If your machines are domain joined, you could push out the installer through System Center or domain logon scripts.
You could cheat and create a solution level pre-build step. Create a target file named: before.{solutionname.sln}.targets and store it next to your solution file. Check it into source control. In the targets file you can use standard MsBuild to see if the extension is installed (you'll need to check the file system probably) and if not present force the installation by calling vsixinstaller.exe to trigger the install.
I am using Visual Studio 2013, InstallShield Limited. One of the 'Predefined Folder' options available in InstallShield Limited, is "[MyPicturesFolder]". I need to be able to install to the user's MyDocuments folder (per company requirements). How can I accomplish this?
As noted by #JonathanHansen in the comment under the question, the [PersonalFolder] is indeed the My Documents folder. See: Personal folders overview
To set this as an output location, in Visual Studio, under Solution Explorer, navigate to the installer project, then under 2 Specify Application Data > Files, right-click the Destination Computer (under Destination computer's files on the left), and select Show Predefined Folder. Then, select [PersonalFolder]. Any files added here will end up under My Documents.
I tested this on Windows 7. A file that I put there ended up on the destination computer under: C:\Users\USERNAME\Documents\
Also see Destination Folders for more information.
Is there a way to disable the warning prompt that pops up when vs2010 finds a dll file locked by another user during a build? I'm using visual studio 2010 with TFS 2008.
By default, TFS disables shared check-outs for binary files - this is enforced for any user, including the build process.
If you wish to enabled shared check-outs for all files, you can update the file extension list for mergeable files: see the Managing File Types article on MSDN.
I'm gonna try Edward's solution once i have proper rights on the TFS but for now I've changed my settings as follows:
This way it avoids the prompt, and also checks out any files i edit once i save em.
Is it possible to add visual studio macros to a solution, so they would be checked in by svn ?
If not, how do you deploy your utilities/scripts with your developer team ?
Unless I'm mistaken, VS Macros are stored in a .vsmacros file as selected when you created the Macro project (I think the default location is C:\Users\yourname\Documents\Visual Studio 2010\Projects\VSMacros80), so just copy that file to your project's directory and add it to the project with no build action and you should be all set.
But that's just if you want to use those macros only with that project, most macros are useful in many projects and if so I'd recommend keeping them where they are rather than in the folder of just one project, and then just add the .vsmacros file manually to subversion to some suitable location (suggestion would be a Tools folder) and check in and out manually when needed.
I've got a Visual Studio solution containing a couple of console app projects, and used the solution property pages to launch both of them when debugging. For some reason, this setting isn't saved in source control so when I check out the solution on a different computer it has to be set up over again.
Where is this info stored and how can I add it to version control?
I believe it is in the Visual Studio User Solution User Options file *.suo. This file is hidden by default. Most source control providers ignore this file by default because it stores location specific paths.
You can install the SwitchStartupProject extension. This will create a file called YourSolution.startup.suo containing the startup projects, which you can check into source control.
See also their wiki for configuration instructions and other info.
According #dan-gpd answer, please use the following updated extension:
SwitchStartupProject for VS 2019