In visual studio, We have a solution that contains two projects. We need to build project A from a specific changeset, but project B with the latest sources. In TFS is there a way to achieve this?
If you just want to build yes , this can be achieved from what i know.You would have to get the project with the Specific build which you want and keep the other with latest build on your visual studio and build it... If you have all the references pointed out correctly then you can build. If you want to save this build in TFS then you can create a new branch on your project and save this there.
Related
Given an existing Android Studio (4.0.1) project that builds and deploys properly and that has an associated SVN repository, I would like to create a separate Android Studio project and get that to also build properly. The purpose is to 1) Prove that the SVN repository is complete (has everything needed to get a build working), 2) Document the steps required to get this Android Studio project out of SVN and building.
Selecting Get from Version Control from Android Studio's welcome screen, I can specify the SVN repository and checkout:
Take the default/latest format for SVN:
And indicate I'd like to make a project out of the contents of the SVN repository:
Then I'm presented with an option that I'm unsure how to answer:
I have tried them all, none successfully. Rather than go into the details of each here, I would like to learn about which option makes sense in which situation.
The original project was created 5 or more years ago with Android Studio's 'start a new project' wizard. I've use Android Studio's default build stuff all along, and upgraded Android Studio and the various plug-ins when nagged sufficiently. I'm not sure what the important build artifacts are (or artifacts critical to a clean import are), and if those artifacts are indeed in the SVN repository and up to date. I can copy the project in the file system and rename things to get it to build, but creating another instance is not the question; the source must be exclusively the SVN repository.
I'm eager to make this question complete, so please do me the favor of specific criticism in the comments so I may improve the question or remove it, as needed.
The optimal person to answer this question would know much more about how Android Studio builds work than I do. I have strictly "cookbook" level knowledge. So without significant study, I am unable to validate intricacies of the process without more knowledgeable people to help.
The last Import Project dialog from this SO question only appears if the contents pulled from SVN are not a complete project.
In other words, if what gets pulled is a complete project, the project just opens, without having to go through any other questions and/or selections. Otherwise, other logic takes over and Android Studio tries to create a legit project for you from the bits it finds.
The solution is to make sure that the check-in from the original working project is complete, including gradle files. If Android Studio is set to view the "Android" artifact view, then everything in the list should display in the VCS "included in source control" and "checked-in" font color.
We have a directory in TFS (a team project) where all our internals and third parties DLL are referenced. It's works great, all our project references these directory.
When I configure an automatic build of my project, I would like that TFS automatically download the latest version of this directory, before TFS do my build. I could configure it?
By the way: We use VS2012 and TFS2012.
Thank you.
In a XAML build, map the TFVC folder where those assemblies are stored under the "Source Settings" tab.
I have a team working on a client-side node.js application. The sources are stored in a source control. I'd like to modify and debug this application in Visual Studio 2015. They use other IDEs, and I would not like to add additional VS-specific files such as .sln to source control.
I'm able to clone the repository, create a separate empty solution and add the repository as an "Existing Web Site". However, Visual Studio do not recognize package.json, and do not install dependencies as it would for MVC6 projects. Consequently gruntfile.js would not work either.
Is there any way to make Visual Studio see and process package.json, or I'm on a wrong track here?
Instead of using the "Existing Web Site" option, create a new solution and add items to it. Web Site Projects types are a different, legacy project type.
I have my Visual Studio C# source code inside Microsoft Azure - Visual Studio Online (VSO), which is basically Team Foundation Server (TFS) 2013 in a Cloud. The Project was created using Microsoft Visual Studio Scrum 2013.3 Process Template.
I need to change process template from current (Scrum) to native Microsoft Visual Studio Agile 2013.3 Process Template.
Currently I do have only source code inside VSO and need to preserve all versions/check ins, with date/times and owners for whole team, there are NO any work items (tasks, bugs etc.)
One solution is to open a new Project inside VSO with Agile template, however how to migrate my code? or how to make simple / easy changes to current VSO project to change process template?
Create a new project and branch your code to the new project. The old project must remain to maintain history
use the TFS Integration tools to replay history against the new location.
(recommended) Switch to Git and use Git-TF to pull the history into git.
check out the tip and check into the new project.
The only option here that adds future value is to move to Git. Once there your history will be forever portable.
When Visual Studio publish feature is used, it does not publish the css files created by dotless.
E.g. I have a less style sheet named Site.less and upon build it will create Site.css. However as the Style.css file is not included in the project it will not get published.
Appreciate any ideas.
Found it...http://haacked.com/archive/2009/12/01/t4-template-for-less-css.aspx
Add this template to you project. It will compile on change rather than on build.