In Visual Studio 2013 I see there is new configuration for build (Release Pro).
When deploying in production, I normally choose Release. So not sure what this Release Pro and how it differs from Release
Will it increase speed?
Cheers.
I have no such new default configuration. Probably one or more of your projects have a custom configuration called RELEASE PRO with some kind of personalization (Conditionals symbols like #if DEFINE_CONSTANT to include/exclude piece of code is the most common reason).
You need to check the projects that are included in the solution to find the ones that uses this configuration and decide if you want to keep it for your building scenarios.
If the configuration is no more needed (Check with the uttermost attention your proejcts) you could use the Configuration Manager menu to remove it:
Build->Configuration Manager
Select Edit from the Active Configuration then Remove
This article on MSDN seems a good starting point to understand the need of a custom configuration Understanding Build Configurations
Related
IDE= Visual Studio 2017 Community
How can I setup a software project so that different cross compile targets for the project map to diff. TFS branches of a single project.
Another related query how to map debug and release versions for one compile target, taking into account previous query above, in VS hosted TFS online.
I assume you mean configuration and platform, you don’t need to do it, also it is based on the configuration and platform you selected in Visual Studio, you just need to change the configuration and platform before build the project.
Refer to these steps to configure configuration and platform for each project.
Right click solution > Configuration Manager
Choose configuration and platform for solution
Choose configuration and platform for projects
Change configuration and platform for solution in Visual Studio
Build the solution or just the project
I am so close yet so far from getting my Visual Studio (MVC) application released through TFS & Release Management. I am using Version 2013 and have my build definition setup as follows:
As you can see it is using the TfvcTemplate.12.xaml as its template, and as such I cannot see the options for Release as I have been finding in all other examples online - eg:
I have gone into Release Management and setup my Release Template to reference this build definition and selected 'Can Trigger a Release from a Build'... but I have nothing happen in RM when I Build in Visual Studio.
What I have also found is that because the application I am building is MVC with Windows Authentication - every time I run a manual release, the Web Site gets rebuilt (as per my release template), but the website is always rebuilt with Windows Authentication Disabled... Which is a pain as I keep having to go into IIS after every release to enable Windows Authentication.
So, my questions are...
1) What am I doing wrong with my version of the Build Definition setup that it will not prompt a release?
2) Do I have to Remove and Create my website on the Release Template... and if so...
3) How do I get around the fact I always have to revisit IIS to enable Windows Authentication after each release?
Thanks!
You need to switch your build template to ReleaseTfvcTemplate.12.xaml.
You can find that file in the folder:
Program Files (x86)\ Microsoft Visual Studio 12.0\ReleaseManagement\bin
You need to check that into your TFS repo, then switch your build definition over to use it.https://msdn.microsoft.com/library/ms181355(v=vs.120).aspx#add_template
I am using VS 2013 and created a custom solution configuration -- "Debug with Flag" - "Any CPU". We have central version control system, where we checkin our code. For some reason everyones' VS environment has this new configuration as active. I don't want this to show as active for others unless they explicitly change it. Also i didn't find option to set default active configuration on VS. Any ideas, why everyone is getting this new custom config as active one?
We've recently upgraded to Visual Studio 2013 and we're having some issues with the new way publishing is handled. Previously, (in VS 2010) every user had their own local publishing settings, but in VS 2013 it's changed to the idea of shared publish settings. This is causing problems with our environment because every developer has a different local dev environment (paths, connection strings, email addresses to send things to). I realize this is not the optimal way to have things set up, but that's the reality of our situation right now.
We use config transforms to handle the various web.config changes for different developers, so just running through VS doesn't work for us because it doesn't run the transforms. This also causes a problem with the VS 2013 publish settings because the last build config used is stored in the shared publish settings. In order to keep all our settings different, it looks like we're going to need to have a different publish setting for each developer now as well (such as "Local - Erik", "Local - OtherDev"). This is just going further down a path I'd like to get out of eventually.
So my question boils down to: Is it possible to somehow disable the shared profile settings? I thought of just not including them in version control, but then Visual Studio complains that the files are missing on other developers' systems.
Thanks for the help!
You can do this by excluding the profile from the project after you create it. The publish wizard looks for any profile on disk, but newly created ones are added to the project by default. If you then exclude the .pubxml file from the project and remove it from source control, it shouldn't bother you again.
I've do a small project, my application will release 2 version, each version contain different image resource, different Application setting file. I known that in the XCode, it's have a term call Target which allow developer config some folder which want to build for each version.
Can Visual Studio do the same thing like XCode?
Thank you!
I believe what you are looking for is solution build configurations, check this link out:
http://msdn.microsoft.com/en-us/library/kwybya3w(v=vs.110).aspx
Here is a good example of including a reference for a specific configuration.
Visual Studio Project: How to include a reference for one configuration only?
You will need to research the topic a bit, but here is how to get started:
1. Open your Solution
2. In solution explorer right click the solution
3. Select Configuration Manager
4. Create a new configuration or modify one of the default ones.
Example of a solution with many build configurations:
Each of these configurations have custom configs and some have different references based on the configuration.