I have installed Azure funciton v4 and ie the default runtime for the azure function core tools. But while debugging the azure funciton using VS 2022 for Mac it is starting the azure function v3 and while looking at the source it seems it is using different azure CLI from addins come with part of visual studio 2022. Anyway we can select our own version of azure function runtime like how VS code provides instead of relying on VS 2022 mac provided azure function is not latest ?
VS 2022 for windows is taking care of this automatically if I specify below in csproj, expecting the same from VS 2022 for ma
<PropertyGroup>
<TargetFramework>net6.0</TargetFramework>
<AzureFunctionsVersion>v4</AzureFunctionsVersion>
</PropertyGroup>
In the logs I can see that VS for Mac is trying to load different Azure CLI : '/Applications/Visual Studio (Preview).app/Contents/MonoBundle/AddIns/MonoDevelop.AzureFunctions/azure-functions-cli/
It is bad that Visual Studio is not upto date with Azure Function core run times and hence it should have some feature like VS Code to choose whichever azure function run time.
Related
I use Microsoft Test Manager - Desktop Application to run tests. In the past - Clicking on Run button Causes that a new window appear and the tests start work.
Recently I updated OS to Windows 10 and after updating the OS, Click of Run button is not responding.
Anyone have any idea what can do the cause?
Thanks
First to say, we strongly recommend you use Azure Test Plans or the Test hub in TFS (a fully featured Test management solution) over Microsoft Test Manager for all your test management requirements.
There will be no new versions of Microsoft Test Manager. Microsoft Test Manager 2017 (which shipped with Microsoft Visual Studio 2017) is the last version.
Please kindly take a look at our official tutorial-- Guidance on Microsoft Test Manager usage
This link will help you understand why Azure Test Plans or the Test hub in TFS is a more comprehensive solution for manual testing compared to Microsoft Test Manager.
If you insist on using old MTM(Microsoft Test Manager) with your TFS. Please try to install the latest version Microsoft Test Manager 2017 (which shipped with Microsoft Visual Studio 2017). Definitely work with windows10, this may do the trick.
Visual Studio Professional 2019 looks to be all set for use of Azure DevOps.
We are using Azure DevOps but also have a large code base still in TFS.
I was using Visual Studio 2017 Enterprise (with TFS) but it seemed this was a 90 day trial.
I have now been issued with Visual Studio Professional 2019.
I should be able to connect Visual Studio Professional 2019 to TFS also ?
How do I do this?
Richard suggested:
Team | Manage Connections then click on manage connections, from where you can connect to servers. "Connect to a Project" form/dialog ..
thanks for this comment !
i.e. in Visual Studio Pro 2019, the option is "Add Azure DevOps Server" even though wanting to add TFS server.
i.e.
In Visual Studio Pro 2017, it looks like this:
At first I have tried (successfully) File, Source Control menu options.
i.e. File | Source Control | Advanced | Open From Server ..
Question then was: "How do I switch Visual Studio Pro 2019 from TFS back to Azure DevOps?"
I have been using Git Gui and Git Bash for working with Azure DevOps so this wasn't so important.
I worked out how to switch between TFS and Azure DevOps projects also via use of this dialog form:
Recently we have upgraded our TFS server to the latest 2019 version.
As the Admin, I was trying to install the downloaded Test Manager extension just like we did in TFS2017 and TFS2018.
However, I was unable to install it even with full access and TFS test plan subscription.
This extension does not support the version of the Server you are
currently using. See Works With for supported Server versions.
What should I do, am I missing something? Why it not work with TFS2019? Appreciate your help.
This is the expected behavior when you try to install the extension in Azure DevOps Server 2019. You do not need to install extra Test Manger for Azure DevOps Server 2019.
The official link is also clearly: This extension does not support the version of the Server you are currently using. See Works With for supported Server versions.
It only work Works with
Team Foundation Server 2017
Team Foundation Server 2018
Note:
Manual testers do not need this extension and can execute tests as a
Basic user in an Azure DevOps organization/collection. Read more on
this here.
This extension is available out-of-the-box in Azure DevOps Services and Azure DevOps Server (2019 onwards) and hence doesn't need to be acquired for them.
We strongly recommend you to use Azure Test Plans or the Test hub in Azure DevOps Service/Server (a fully featured Test management solution) over Microsoft Test Manager for all your test management requirements. There will be no new versions of Microsoft Test Manager.Microsoft Test Manager 2017 (which shipped with Microsoft Visual Studio 2017) is the last version.
More details please take a look at our official tutorial here.
Besides, to use Azure Test Plans in Azure DevOps service you need some License requirements
Azure Test Plans uses an access level called Basic + Test Plans, which is available from Azure DevOps.
For the Manual testing permissions and access suggest refer this link: https://learn.microsoft.com/en-us/azure/devops/test/manual-test-permissions?view=azure-devops#license-requirements
Hope this helps.
As mentiond in the Extension page:
This extension is available out-of-the-box in Azure DevOps Services and Azure DevOps Server (2019 onwards) and hence doesn't need to be acquired for them.
So you don't to install it, it's exist :) just go to the "Test Pans" tab in the left menu (maybe you need give permissions in the settings).
We're deploying a set of Build Controllers and Agents throughout our infrastructure to build Web/MVC applications and deploy them using Release Management through TFS 2013.
I read that we need to have Visual Studio installed on the build machines to compile properly, and would like to know if we are able to use Visual Studio Shell (Integrated? Isolated?) or if we need to dedicate a full (Ultimate or Professional) Visual Studio to it.
Thanks in advance--
==Update 10:33 5/5/2014==
Due to the security restrictions placed on our development group, we are unable to use off-premise resources.
==Update 12:47 5/5/2014==
Installing the MSBuild Redistributable (via Erik Funkenbusch) was a good start, and following Jimmy's advice sealed it. Thanks!
The components needed to build Web Applications (of which MVC is a subtype) are in \Program Files (x86)\msbuild\Microsoft\VisualStudio\v12.0\WebApplications (or whichever version of VS you're building against). While these are installed by VS, you can just xcopy them to your build servers without the rest of the VS installation.
No, you don't need Visual Studio installed on the build machine, and wherever you read that... run far away, because they don't know what they're talking about.
In fact, it's explicitly recommended to NOT install Visual Studio on the build machine.
Microsoft has a full MSBuild redistributable with 2013 components. MVC is installed as part of the build via Nuget (along with other components).
http://www.microsoft.com/en-us/download/details.aspx?id=40760
In past years, you had to install the Windows SDK, and do a lot of manual configuration, and that was a pain. With 2013, they've made this much simpler.
I believe the Release Management should also have an installation setup file to install components for build servers....
You don't need Visual Studio for just doing compilation as part of the build process. If you have unit test cases which needs to be run then you need Visual Studio.
I am trying to build a project using TFS2010 Build.TFS resides on its own server, and i am trying to build to a directory on the same machine. The Server does not have VS2010 installed on it.
When the build runs it fails and gives me this error:
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1558): Task failed because "AxImp.exe" was not found, or the correct Microsoft Windows SDK is not installed. The task is looking for "AxImp.exe" in the "bin" subdirectory beneath the location specified in the InstallationFolder value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A. You may be able to solve the problem by doing one of the following: 1) Install the Microsoft Windows SDK. 2) Install Visual Studio 2010. 3) Manually set the above registry key to the correct location. 4) Pass the correct location into the "ToolPath" parameter of the task.
Then I get a whole bunch of errors saying the namespaces of the project I am building cannot be found. I am not sure if that is all linked to the above mentioned error however.
Thank You!
It is recommended to have Visual Studio 2010 installed on your build machine but it is not a requirement. Since the error message indicates that it didn't find AxImp.exe, can you verify if this file exists on the build machine? The location is C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin (if you're on a 64-bit Windows).
If the file doesn't exist, installing .NET Framework SDK will probably help to resolve that specific error.
Regarding installing Visual Studio on the build machine, Visual Studio is licensed per user, not per machine, so as long as the build machine owner is licensed, you should not need extra license for Visual Studio. But you probably should look at the licensing papers for your edition of Visual Studio 2010 to make sure.
Here's a table in the white paper on licensing:
You need to have the same software running on the build server as you would if building locally. This means you need Visual Studio 2010, and possibly even the same edition of Visual Studio 2010, depending on what you're trying to build.
IMPORTANT REMINDER: Visual Studio is licensed PER USER. This means that as long as you as a user have a license, you can use that SAME LICENSE on your build Machine.
The only "problem" would be if you actually had "No licenses" - meaning you do not own a copy of Visual Studio at all, but have a legal copy of TFS.