I have an existing Azure Devops Team Project (Project A). I also have a Visual Studio solution on my local machine that I want to start tracking in Project A.
When I went to add my source code to Project A's repo from Visual Studio, I inadvertently created a new blank Team Project in Azure Devops (Project B). So now I have two Team Projects. Project A has all my work items, etc. and Project B has my source code.
In Visual Studio, I've tried editing the "Remotes" setting to the correct repo location, but that doesn't seem to have worked. I went to Team Explorer -> Settings -> Repository Settings -> Remotes -> Edit to make the change.
I want to change my visual studio solution to publish my source code to Project A instead of Project B.
Related
I am trying to deploy a wpf application with an embedded rdlc report using clickonce. The previous version of report viewer (in VS2015) was built-in so it was easy and convenient to use and I had no issues deploying this project.
Now since easy and convenient is not the goal anymore, in vs2017 after a failed deploy with an error message that gave me absolutely no help, I have come to realize that apparently you have to install 2 additional VS extensions and a report viewer runtime on every machine where an app uses and rdlc reports (feels like crystal reports all over again) and you have to exclude the automatically included Chinese localization files in your clickonce deployment (which cause a manifest parse error). Anyway, the instructions on MS website say that click once should have a "Microsoft Visual Studio Report Viewer" prerequisite option to select as requirement of installing your app. However, after installing the runtime on my development machine, restarting visual studio, this option is not available. Does anyone know how to get this to work?
I used Project|Manage NuGet Packages to add this package to my project.
https://www.nuget.org/packages/Microsoft.ReportViewer.Runtime.Common/12.0.2402.15
If you search with Manage NuGet Packages, there's quite a few ReportViewer related items. I'm not sure which ones are appropriate to your WPF app.
Anyway, the deployment project picked up the various ReportViewer assembly dependencies and everything seems to be working without the EXE redist from MS.
I am trying to take an existing .net core API project and run it as a lambda function (Which should be possible).
I have installed the VS 2017 SDK for AWS. While following tutorials, I am supposed to be able to right click my project and select deploy to AWS Lambda. The only option I have is "Publish To Elastic Beanstalk"
However, when I create a brand new empty function in Visual Studio (New Project). I do have the ability to Publish To Lambda
But I can't seem to figure out the difference between the projects. Every nuget/tooling reference between the two projects is identical when it comes to AWS Packages.
My answer was the following, in my csproj I had the following line :
<DotNetCliToolReference Include="Amazon.Lambda.Tools " Version="1.5.0" />
Notice there is a small space after Tools. No complains from VS though so it was super hard to spot, and only exists because you have to edit the csproj manually when adding DotNetCliTools.
I've found a couple of similar questions on Stackoverflow, but the answers do not solve my issue. (For example the issue would be fixed in previous version. OpsHub TFS 2010 to Visual Studio Online)
Also I experience different behaviors on multiple environments so I think it's a new question. I hope someone can help me.
I have some projects on a TFS 2012 with the standard Scrum 2.2 template. I created a Visual Studio Team Services environment on my personal account for testing the migration. I created a project based on the default Scum process with the same name as the project in TFS. When I use the OpsHub tool (version 2.0.0.004) to migrate the work items to VSTS it works as expected.
screenshot of working migration
Now I create a new project on my companies VSTS environment with the same name and the same Scrum template. Apply the same rights, and try to migrate the same project to companies VSTS, validation fails with the message that "template customization or template mismatch". Details "Code Review Response - Reviewed By"
screenshot of failed validation
I exported the scrum process templates for both environments and compared the contents but they are identical.
So I have 1 project on TFS and 2 projects on VSTS with identical templates. One migration works, the other does not. I'm stuck. Any tips would be very welcome!
Thanx
I got an email from OpsHub with the solution! They released a new version (2.0.0.005) and after clearing the cache, it works! Thank you, OpsHub.
Refer this to download the latest version.
Perform following steps:
Close the OVSMU Tool if running.
Installed the latest version OVSMU-V2.0.0.005
Clear the following cache folder:
Close the OVSMU Tool as well as any instances of Visual Studio (ie. TFS related applications)
Clear the contents of the following folders (whichever ones you have)
%localappdata%/Microsoft/TeamFoundation/3.0/Cache
%localappdata%/Microsoft/TeamFoundation/4.0/Cache
%localappdata%/Microsoft/TeamFoundation/5.0/Cache
%localappdata%/Microsoft/TeamFoundation/6.0/Cache
Launch the newly installed OVSMU Tool & Configure the migration again.
I have started using the preview of Microsoft Team Foundation Service (TFS in the cloud, henceforth TFService) for a small project, and I'm currently setting up builds using the online build service included with TFService.
What I want to do is to add an installer of some kind. I've previously worked with InstallShield Limited Edition, WIX and Inno Setup and would like to keep using one of those if possible.
I've previously integrated Inno Setup as part of a build process (TFS 2010). This involved installing Inno Setup on the build computer, and adding a custom build task for running an inno setup script. The last part should be possible with TFService as well, because it's possible to create custom build process templates.
However, I realize that installing anything such as Inno Setup or InstallShield will not work with TFService, since it's not possible to install any 3rd party software on the build computer (it's just a cloud service running on some unknown virtual computer which I cannot access).
So my question is; is there a way to automatically create an installer as part of a build process running on TFService? For example, is the build service capable of building installshield projects out of the box (there's a license included with Visual Studio after all)? Or are there other ways to do this?
I have some experience with this trying to get WiX and InstallShield to work with Microsoft TFS Preview cloud service using their managed build agents. On these agents, you don't have administrator rights and you can't install software.
This currently rules out InstallShield which must be installed.
It is however possible to check the WiX binaries into source control and pull them down as part of your build.
WiX uses .wixproj files (MSBuild) to define their project compile activities. This references a targets file and other properties ( referencing registry values ) that won't exist when you deploy this way. A small bit of hacking will get all of these properties to resolve to workable values.
The one problem you may still have though (and I'm thinking TFS managed build environment ) is that you may have to configure your projects to skip MSI ICE validation suites. On the build machines, I played on the windows installer service was outright disabled and this prevented the tests from running.
I'm trying to set up a build definition in TFS 2010. The options for this seem very limited, for instance I have 5 solution files in my source control and I don't seem to be able to specifiy which one to use. I've selected a workspace from my deployment server (which does a TF get every 10 minutes so I know it's a valid workspace), but when the build runs it gives me an error complaining about the mapping - and it seems to have made it's own mapping up from somewhere.
Mapping I set: $/InteractV4/Dev/IV4ProductionSR/
Error: There is no working folder mapping for $/InteractV4/Dev/IV4Support/iv4ProductionSR.sln.
There are 2 issues with this error. 1: it's not the workspace I was trying to use. 2: It's wrong and there is a working folder mapping for this source, both on my local PC and on the deployment pc, but NOT on the build server. Do I need to set up a load of folders and mappings on the build agent server? Or on the main TFS (source) server?
Thanks.
TFS-Builds operate on private Workspaces that get generated during the build process, so using a custom-Workspace is without tweaking impossible.It's possible to keep TFS from regenerating a new Workspace with each Buid, by going to Build Definition edit "Process":"2.Basic":"Clean Workspace" and changing default value All into either Outputs or None.The mappings are set for each Build Defition where various pairs exist:
Source Control Folder | Build Agent Folder
$/foo/bar | $(SourceDir)\somewhere
The $(SourceDir) is substituted during Build and it gets its value from the Build Agent Settings. If you go to the TFS Admin Console & select "Build Configuration", you 'll be presented with a list of Build Agents running on the Server (there might be additional Agents in other Servers). Clicking on "Properties" of an Agent, pops up a Window like that: This entry "Working directory" is the one that resolves & substitutes $(SourceDir) during build.For example, an entry $(SystemDrive)\Builds\$(BuildAgentId) could resolve into something like C:\Builds\88.So, for a TFS Build running on this Agent, you should expect all Sources that stand in source control under $/foo/bar to be found under C:\Builds\88\somewhere
EDITAccording to your comments you have now a mapping like this:
$\InteractV4\Dev\IV4ProductionSR | $(SourceDir)
Your build fails, as "There is no working folder mapping for $/InteractV4/Dev/IV4Support/iv4ProductionSR.sln".
Is this source control directory $/InteractV4/Dev/IV4Support mapped in your Build Definition?