I try to get a asp.net5 Project to build with Visual Studio Online and deploy it to azure from there. I created the project with Visual Studio 2015 RTM.
I use the guide at msdn. The guide uses a msbuild target "FileSystemPublish" to get the build to azure. But I get the error that this target does not exist:
xxxx.sln.metaproj(0,0): Error MSB4057: The target "FileSystemPublish" does not exist in the project.
Does anyone know how I get this target working or how I can deploy without this target?
I found my mistake. I missed one step. I still tried to build the sln, but you need to build the xproj file:
7.Select the Visual Studio Build step and in the Solution input browse to the .xproj. Select it and click OK.
Related
We are trying to generate a click once application using azure devops pipelines.
During this, we publish the project to create a setup.exe. All the pre-requisites required are ticked, the project builds and publishes the setup.exe without any issues.
However, every time the setup.exe is run we see the prompt in Image 1.
Image 1
We have ensured the installURL is correct, and the .NET Framework 4.7.2 is on the build machine and install machine.
When we publish the project in visual studio, the setup.exe does not show this prompt.
Does anyone have any idea how to stop this prompt showing or what we could try next?
In your Visual Studio build task in your pipeline, make sure you have Visual Studio 2019 selected due to a bug in earlier versions of VS.
https://developercommunity.visualstudio.com/content/problem/743594/dotnetfx472-and-dotnetfx48-not-finding-information.html
After setting up the release definition with tasks exactly like those in this document:
https://learn.microsoft.com/en-us/azure/devops/test/run-automated-tests-from-test-hub?view=azure-devops
I am continuing to get the error:
Selected environment does not have the right version or settings of the Visual Studio Test task to run tests.
My current configuration can be seen below.
Link to screenshot of VsTest task.
Has anyone experienced this problem before? If so, how can I resolve it?
Make sure you have installed Visual Studio on the agent computer, otherwise you must add the Visual Studio Test Platform Installer task to the pipeline definition.
I am using TFS 2012 build option to build my web application. I have couple of console application in the solution. I want the console application output to be copied to the bin folder. In visual studio, I am doing this by using the copy command in the Post build event command option. But this does not work in TFS builds. The generated exe is not copied to the _PublishedWebsites folder in the BuildAgent directory
Possibility duplicate to Problems with MSBuild OutputPath and OutDir in TFS2010 .
Also give a try wiht this NuGet package, you can install it which will do this.
With TFS 2012 build process template, you need to custom build process template to run the script after building, like the post-build scripts feature in TFS 2013 build process template.
You can refer to this article to custom build process template to achieve your requirement.
I'm trying InstallShield project to create an installations using Visual studio TFS 2012. But, setup file is not being generated. When I looked into the error log, it says "isproj is not supported by MSBuild and cannot be built"
Let me know what is the fix for this issue.
For VS2010 and before I was utilizing Web Deployment Projects (WDP) to help package my website for production deployment. I had a MSBuild script that compiled the solution in release mode. An output of that was production ready website files compiled and cleaned by the WDP.
I see for 2012 WDP have been removed, and a new tab has been created in the properties for the web application. The options are the same, but now the invocation of this is done via the Publish option (before you just compiled in release mode).
So the question is this. From an MSBuild script, how do I invoke a Publish operation? I found some old posts that...
msbuild /target:publish
would do the trick. But that doesn't seem to work in 2012.
Also, I tried in my msbuild task...
<MSBuild Properties="Configuration=Publish;"
StopOnFirstFailure="true"
Projects="$(BuildDirectory)\MySolution.sln"></MSBuild>
...but msbuild just reported "unknown configuration".
How can I have msbuild run the publish option from the command line?
It appears that there are now some other options for publishing from the command-line. Specifically something along the lines of the following seems possible now with some RC updates to Visual Studio 2012.
msbuild mywap.csproj /p:DeployOnBuild=true;PublishProfile=MyProfileName
For more details check out this post by Scott Hanselman and check out the section on Publishing.
I wasn't able to get the publish to run, but looking at the output from Visual Studio I think I have found an alternate solution. Turns out the obj\Release\AspnetCompileMerge folder has a deployable and clean version of the project. It contains byte identical files to the final output folder.
I did have to change my msbuild script to include the DeployOnBuild option...
<MSBuild Properties="Configuration=Release;DeployOnBuild=True;"
StopOnFirstFailure="true"
Projects="$(BuildDirectory)\BigWave.ALL.sln"></MSBuild>