I have a project that I need to publish (run) this publish an IIS site.
I tried dotnet run, this starts the project but does not publish the website, any idea on how can I do this or how to log what happens when I click "RUN" on visual studio?
Related
I am using Visual Studio 2017.
Everything was working fine, i.e all my C# codes and projects were executing fine. But now when executing any project by clicking on the green icon/F5, it shows loading mouse symbol. And cant run the project. Can build and rebuild the solution. And also can run the project with "Browse with" option. I have tried by deleting '.vs' folder. But have no effect.
I have a UWP app project that was created using Visual Studio 2105. I have started using the same solution in Visual Studio 2017. However, I have noticed that the app is removed and reinstalled on each deploy. So, all my pinned tiles, registered background tasks, app states are reset on each deploy making it difficult to debug.
I ensured that "Uninstall and then re-install my package." is unchecked in the project properties. I cannot find any other configuration controlling this behaviour. How do I solve this?
Edit: Here is the build output from Visual Studio while deploying the app in Debug configuration.
On the StartUp project - right click and select properties. Select Debug tab.
Untick "Uninstall and then re-install my package. All information about the application state is deleted."
According to this Microsoft article on VS2015 there should be a "Run tests after every build" option in the test explorer. There is not. Any idea how to enable it?
I am running VS2015 Update 2, but perhaps there are some additional settings I need to enable?
The referred article in your question has a note on the availability on that feature:
Warning
Running unit tests after every build is supported in Visual
Studio Enterprise.
I use Community at home and Professional at work and don't have that feature in either of them.
I am using Visual Studio 2017 Professional and I really want to run tests after build, a feature is only available in Visual Studio Enterprise and currently in Visual Studio 2019 Professional Preview as well. Visual Studio 2019's IntelliSense doesn't do "code completion" well, so I still mainly use Visual Studio 2017.
A work-around to run tests after build in VS 2017 is to run the test from the command line using dotnet vstest.
Simply create a batch file to run dotnet vstest [Your Test Project].dll and add to Project Properties > Build Events > Post-build event command line: call $(ProjectDir)YourBatchFile.bat > Run the post-build event: On successful build.
Below is a sample Output after the build:
So I'm attempting to check in from visual studios to deploy my code to an azure web app, however I cannot for the life of me find the check in option. I'm connected to the Visual Studios Online repo and can view the web app in the server explorer. Googling this has found me nothing so either this is a clearly labeled feature I'm blind to or support for the feature has been dropped from visual studios and everyone simply knows this.
You can use the build-in build step in Visual Studio Online: Azure Web App Deployement.
In your build definition click on Add Build Step
In Deploy Category you will found the step: Azure Web App Deployement
Click Add
In Visual Studio 2015, you must do a power Shell script to deploy it.
You can find more information at this address:
Web Deploy command line
Deploy with PowerShell
We are setting up a Team City build server. On previous VS 2008 projects a full version of Visual Studio has been installed on the build server.
We are now starting a VS 2010 project.
Is it possible to run MSTest tests on the Team City build server without installing Visual Studio?
Download the Visual Studio Agents 2010 ISO: http://www.microsoft.com/en-us/download/details.aspx?id=1334
Mount/Extract the files and copy them to the agent server
Run AutoRun and select to install Microsoft Visual Studio Test Agent 2010
Install using the default settings
Cancel out of the "configuration" dialog (you don't need the actual Agent running, just the installed libraries)
Your MSTest build step should run just fine now.