I'm using VS2017 - is there any way to get webtests working without installing VS2017 Enterprise? All I need is mstest.exe - not the GUI or IDE.
No, for unit test you can install Agents For Visual Studio 2017.
But for Web Load & Performance Testing, it is only supported in Visual Studio Enterprise 2017, So you need to install Visual Studio Enterprise 2017 with Web Performance and Load testing tools.
More information about VS 2017 supported features, you can refer to: Compare Visual Studio 2017 IDEs
Reference below threads:
Getting error: File extension specified '.webtest' is not a valid test extension
Can I use mstest.exe without installing Visual Studio?
Related
I have a solution that contains a .deployproj type of project. It seems that Visual Studio 2019 is not able to load that project. The detailed error message is the following:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- Provisioning.Arm, "C:...\Provisioning.Arm\Provisioning.Arm.deployproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
What can I do in order to load the project within Visual Studio 2019?
It seems that you need to install the Azure Development workload in order for Visual Studio to be able to load .deployproj projects.
So just modify the current installation to also contain this workload. (I don't know exactly what individual component needs to be installed for this to work, I just installed the entire Azure Development workload).
Came across this blog => https://devblogs.microsoft.com/devops/cloud-based-load-testing-service-eol/ saying that - When Visual Studio 2019 Preview 1 shipped in early December, Microsoft announced the plans to deprecate the load test functionality in Visual Studio. Visual Studio 2019 will be the last version of Visual Studio with web performance and load test features.". Have below questions about this:-
Does this mean the existing load tests written using the perf testing agents will not work any in Visual Studio?
Or does that mean engineers will not be able to use load testing features in Visual Studio 2019 onwards?
If you have a big amount of tests I would recommend staying on your current version of Visual Studio as 2019 will not have load testing features.
For new machines / load generators you should be able to install older versions of Visual Studio
For new tests development Microsoft Recommends JMeter and BlazeMeter as Preferred Load Testing Tools
My project need to be run with MSbuild 14.0(visual studio 2015) but this is taking only Visual Studio\2017\Community\MSBuild\15.0\Bin\msbuild.exe .
I have installed visual studio community 2017,VS 2015 web and Desktop express on my Build Agent.
Capabilities of build agent-
Task Configuration -
This configuration giving me the warning -
[warning]Visual Studio version '14.0' not found. Falling back to version '15.0'.
How can I use MSBuild 14.0 with Visual Studio build task .?? This is running with MSbuild task..
Thanks in Advance ..!!
[warning]Visual Studio version '14.0' not found. Falling back to version '15.0'
Since I do not install Visual Studio 2015 Express for Desktop and Web on my build agent, I am not sure whether Visual Studio 2015 Express for Desktop and Web is compatible with build agent.
But I found a thread about it, you can check the comment on the accepted answer:
That's it! For some reason VS2015 Express does not install the ShellFolder or InstallDir keys! I was worried that the agent script recognised it but refused to register it because we are not allowed to use it for automated builds. I feel more comfortable with it now.
It turns out that is not the full story. When I add the "Visual Studio
Build" task to the process, it now executes, but if I look more
closely at the log, I can see the following message:
"##[warning]Visual Studio was not found. Try installing a supported
version of Visual Studio. See the task definition for a list of
supported versions." And then it falls back to building with MSBuild.
It works because I am building a .sln; let's just hope I don't have to
build a .proj.
So, it seems that Visual Studio 2015 Express is not compatible with build agent. you can try to install the Visual Studio community 2015 instead of it, which I can build it without any issue.
Again, you can check if there is a parameter about Visual Studio on your Capabilities of build agent when you use Visual Studio 2015 Express:
if not, build agent will throw that error.
Hope this helps.
I have a Jenkins server setup to build a mixed C++/C# application. I've got Visual Studio Test Agent 2017 and Visual Studio Build Tools 2017 installed but I can't build the Visual Studio test projects. The error I get is:
error CS0234: The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft'
It looks as though the appropriate assemblies are not available.
I'm using this SDK to install tools for Visual Studio 2015 which is possible with the 2017 SDK and that part works fine - I can build VS 2015 projects. Except for test projects.
Is there some extra package I need to install in order to make this work? My alternative is to install NUnit but that means rewriting the unit tests.
My solution was to use NUnit, since I was unable to find the right SDK to install VS Test without Visual Studio itself.
NUnit required changes to Resharper, file handling and changing the attributes on the test.
I'm encountering an issue when trying to build .modelproj projects using msbuild via Visual Studio 2017 Build Tools.
This is the error I see:
...[ProjectName].modelproj error MSB4057: The target "Rebuild" does
not exist in the project.
I have found this thread relating to some issues opening .modelproj files via the IDE in VS2017 - Visual Studio 2017 not opening .modelproj - however is there a way to get this fix onto just Build Tools rather than the full IDE? Ideally we'd like to avoid having to install the full IDE when all we require are the Build Tools on the server.
however is there a way to get this fix onto just Build Tools rather than the full IDE? Ideally we'd like to avoid having to install the full IDE when all we require are the Build Tools on the server.
You can not build Modeling projects using msbuild via Visual Studio 2017 Build Tools. Because starting with Visual Studio 2017, the UML Designers have been removed from Visual Studio, If you are a significant user of the UML designers, you can continue to use Visual Studio 2015 or earlier versions.
You can get the detail information from Port, Migrate, and Upgrade Visual Studio Projects and Microsoft Application Lifecycle Management：