Our test department has a series of web tests created using Visual Studio 2005 Team Tester Edition.
I would like to be able to execute these tests against my local machine. I attempted to use the mstest command line tool to accomplish this as described in this MSDN article. But I get the following error:
C:\WebTests\Participant>mstest
/testcontainer:AE_ActivityDue_Touch.webtest
Microsoft (R) Test Execution Command
Line Tool Version 9.0.30729.1
Copyright (c) Microsoft Corporation.
All rights reserved.
Loading
AE_ActivityDue_Touch.webtest...
AE_ActivityDue_Touch.webtest File
extension specified '.webtest' is not
a valid test extension.
Any hints on how I can get this to work? Eventually we want to work them into our CI process.
You need VSTS Test Edition. No bueno.
http://msdn.microsoft.com/en-us/vsts2008/test/default.aspx
Related
I am trying to install Visual Studio 2017 RC and I keep getting this error:
[2ea4:002f][2016-11-20T21:47:00] Package
'Microsoft.TeamFoundation.OfficeIntegration.Resources,version=15.108.25831.0,chip=x64,language=en-US'
failed to install. MSI:
C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.TeamFoundation.OfficeIntegration.Resources,version=15.108.25831.0,chip=x64,language=en-US\tfs_officeIntegrationCoreRes.msi,
Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1
MSIFASTINSTALL="7" USING_EXUIH="1" , Return code: 1714, Details: The
older version of Microsoft Visual Studio Team Foundation Server 2017
RC Office Integration Language Pack (x64) - ENU cannot be removed.
Contact your technical support group.
We were able to force uninstall the problematic package using this Microsoft tool, after which we were able to install VS2017 normally.
The package name in our case was: Microsoft Visual Studio Team Foundation Server 2017 RC Office Integration Language Pack (x64) - ENU
With my experience, this happens when Visual Studio 2017 setup cannot uninstall/repair/upgrade an existing package. Try this:
Quit the VS 2017 installer setup and go to this location "C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.TeamFoundation.OfficeIntegration.Resources"
There must be an .msi file with name "tfs_officeIntegrationCoreRes.msi" (based on your error message - it appears that you have office tools installed as part of previous VS installation)
Run that msi and remove the component (there must be a remove option). Once done restart the VS 2017 setup again and this time you shouldnt get this error at least.
Hope this helps.
after several tries, I had no solution. Then restarted the computer and run the installer again. No installation errors :)
I am testing Free and Open Source Software using Microsoft's Visual Studio 2015 Community Edition (and here) to ensure compatibility with the compiler and tools. The 30 day trial has expired, so I need to work from the command line because the IDE exists after telling me the trial has expired:
When I try to run msbuild from the command line, I get a couple of top level errors:
Test> msbuild cryptest.sln
Microsoft (R) Build Engine version 14.0.23107.0
Copyright (C) Microsoft Corporation. All rights reserved.
Building the projects in this solution one at a time. To enable parallel build,
please add the "/m" switch.
Build started 9/7/2015 7:58:54 AM.
Project "...\cryptest.sln" on node 1
(default targets).
ValidateSolutionConfiguration:
Building solution configuration "Debug|Win32".
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visua
l Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere. [...\cryptest.sln]
Done Building Project "...\cryptest.sln" (default targets) -- FAILED.
Build FAILED.
"...\cryptest.sln" (default target)
(1) ->
(cryptlib target) ->
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe
". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Vis
ual Studio 2005 or 3) add the location of the component to the system path if i
t is installed elsewhere. [...\cryptest.sln]
0 Warning(s)
1 Error(s)
The problems above are due to a down level (Visual Studio 2008) solution and project files.
The official docs are at How to: Upgrade Visual C++ Projects to Visual Studio 2015, but the page does not discuss a solution upgrade from the command line.
According to the VC++ Team Blog at Visual Studio 2010 C++ Project Upgrade Guide, there's a VCUpgrade.exe located in $(VSInstallDir)\common7\Tools. But: "... [VCUpgrade.exe is only] suitable for upgrading applications with only one project as it cannot take in solution file as input and parse solution information into project files."
I also found Upgrading Projects to Visual C++ 2010 at Building Applications that Use the Windows SDK. It tells me to use devenv.exe /upgrade. When I follow its instructions, it results in the following. There were no errors, but nothing was converted (and no log file was created).
!! From VS2015 Developer Command Line Prompt
cryptopp-5.6.3>devenv.exe /upgrade
cryptopp-5.6.3>dir *.vcproj *.vcxproj
...
09/07/2015 10:36 AM 81,845 cryptdll.vcproj
09/07/2015 10:36 AM 40,168 cryptest.vcproj
09/07/2015 10:36 AM 205,529 cryptlib.vcproj
09/07/2015 10:36 AM 8,885 dlltest.vcproj
Attempting to use VCupgrade.exe (even though its an incomplete solution according to the Microsoft docs) results in:
cryptopp-5.6.3>vcupgrade cryptest.vcproj
Microsoft (R) Visual C++ Project Convert Utility - Version 14.00.23107
Copyright (C) Microsoft Corporation. All rights reserved.
Failed to initialize the VCProjectEngine.
How do I convert a solution and project files from an earlier version of Visual Studio to Visual Studio 2015?
There's a few similar questions, but they don't cover the command line with errors like "Failed to initialize the VCProjectEngine" and the [unexplained] expiring trial. See, for example, Upgrade a visual studio solution on the command line with visual studio express.
Humorously (in a morbid sort of way), Microsoft calls Visual Studio 2015 Community a free dev tool, and does not state its an expiring trial at Overview of Visual Studio 2015 Products or Visual Studio Community pages. In fact, Microsoft tells us its fully featured and free for Open Source projects (which this project is).
I guess Microsoft lied and the lawyers buried it in the Terms of Service somewhere. More humorously, neither "trial" nor "expire" are called out or mentioned at the Terms of Service, either. See Microsoft's Visual Studio Community license terms.
Not so humorously, I declined a copy of Visual Studio Professional after reviewing Microsoft's marketing literature because I thought Community edition would meet the project's needs. I hope that does not turn out to be a $500 USD mistake...
It seems the best (and most supported) choice might be to just sign-in with a Microsoft account, so that you can use the free Community Edition license. This will allow you to open the development environment and upgrade the solution using the intended / most-well-tested upgrade process.
This doesn't answer all your questions, as I think the first question needs to be addressed to test and see if you need answers to upgrade your projects.
I have had similar error messages over time with VS. See this answer- Visual Studio 2013 Community weird errors Although this discusses VS2013 the same principles apply.
Visual Studio Community Edition is free.(Much like the express versions MS offers)
These are the license rights you have.
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT VISUAL STUDIO COMMUNITY 2015
These license terms are an agreement between Microsoft Corporation (or
based on where you live, one of its affiliates) and you. They apply to
the software named above. The terms also apply to any Microsoft
services or updates for the software, except to the extent those have
different terms.
IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE RIGHTS BELOW.
INSTALLATION AND USE RIGHTS.
Individual license.
If you are an
individual working on your own applications to sell or for any other
purpose, you may use the software to develop and test those
applications.
I recommend uninstalling VS and any associated dependencies. Download VS2015 CE from one of the links I've provided and reinstall from that exe. Allowing VS to configure the installation and it's dependencies.
For the trial to expire, it makes me think you didn't download the CE. This is why I suggest a fresh download.
Also, if you cannot run VS by opening it's shortcut, you're not going to be able to run it from the command line.
After getting it up and running, then see how your upgrades go. Also, remember if you have any errors about missing dependencies, download them.
Hope this helps some, I saw this was about to expire and you had no answers.
you could upgrade using the devenv.exe command: just invoke it with the “/upgrade” switch. The location of devenv.exe is specified by the DevEnvDir environment variable in the VS 2010 command prompt window.
Command:
a) To upgrade solution file: devenv.exe /upgrade <solution file (.sln)>; or
b) To upgrade project file: devenv.exe /upgrade <project file (.vcproj)>.
Ref: https://devblogs.microsoft.com/cppblog/to-the-command-line-enthusiasts-some-quick-know-hows-for-upgrading-to-vs-2010/
I am trying to write my first test case using TFS 2010 in VS2010 However Actions and Expected results columns won't allow me to add those steps ... any thing am doing wrong ?
http://www.microsoft.com/visualstudio/eng#products/compare
The link is referring to Visual Studio 2012 editions, but it is nearly the same with 2010. This means that those steps can only be done in Microsoft Test Manager, which is part of Ultimate and Test Edition in 2010. In 2012 it is also available in Premium edition.
To solve your problem you need to install the correct edition and than use the Test Manager. There should be also a button in Visual Studio which says "Edit with Microsoft Test Manager".
I developed a Windows 8 C# application using Visual Studio Express 2012 RC. I can run it on my pc. However, I want to create an executable so that my friends can also try the application. When I click the .exe file under bin/Release folder it says:
This application can only run in the context of an app container.
How can i create an app container manually or using Visual Studio 2012?
See here.
You need a developer license to develop and test Metro style apps
prior to certifying and deploying through the store. Visual Studio
2012 will automatically request a developer license when it is run for
the first time. To get a developer license without Visual Studio run
the show-WindowsDeveloperLicenseRegistration function in powershell:
C:\Windows\system32>powershell
Windows PowerShell Copyright (C) 2012
Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> Show-WindowsDeveloperLicenseRegistration
For
information on developer licenses see: Get a developer license (Metro
style apps) To deploy the app, build a package in Visual Studio from
the Store.Build Pacakage menu. Build it for local use. Copy the
resulting package to the target machine and run the included
Add-AppDevPackage.ps1 file. See also Sharing an app package locally.
--Rob
Is there a way to disable Visual Studio for prompting to upgrade an older solution file?
I'm opening the project in VS2010, yes I want you to actually open it, and no I don't want your backup.
Is there some way I can permanently bypass this and just have this work?
You have limited options here. You could start devenv.exe with the /upgrade command line option to perform an upgrade. That just upgrades the solution and doesn't actually start the IDE. The backup is always made without an option to skip it. Useful in batch conversion scenarios. Copied from the console window:
C:\projects\ConsoleApplication7>devenv /upgrade consoleapplication7.sln
Microsoft (R) Visual Studio Version 10.0.40219.1.
Copyright (C) Microsoft Corp. All rights reserved.
Upgrade completed successfully. Results can be seen in the
upgrade report:
C:\projects\ConsoleApplication7\UpgradeLog.XML