I have a test scenario where i want to validate the 4.5.2 version .net framework is being installed on a fresh windows environment (Win7, 8.1 and 10 - both 32 and 64 bit) along with the .exe which is being installed (Installation being one of the critical test scenario). I did the scripting in MS CodedUI Test. I want this script to be distributed on different machines. For this, I am using Test Controller and Agent setup. I am using VS2015 and TestAgent 2015. As Test Agent 2015 comes with .NET 4.6, my script is getting failed. Can i use any older versions of test agent to accomplish this?
Surely, the installer should fail if 4.5.2 is not available on the target? Then there is no need to use CodedUI to validate it.
Related
I am working on Visual Studio for Mac.
I am using test project with
MSTest.TestAdapter
MSTest.TestFramework
The project target is .NET Framework 4.6.1
(I need .NET Framwork to use Xamarin.UITest)
I can run this test library in the IDE by right clicking the project and selecting "Run Item".
How can I run those tests via terminal on a Mac?
It's not working with:
dotnet test
because it is not .NET Core.
On windows there seems to be a MSTest.exe. I couldn't find it on the mac via the "which" command.
Is there a way to start this test on mono with an executable that runs the test adapter?
Like a mstest equivalent to nuint-console on a Mac.
Edit: The question: How to run Mstests on a Mac? doesn't work for this problem because (see above) the tests aren't able to run under .NET Core. They are targeting the .NET Framework.
Long time reader first time poster here.
I'm a Linux developer trying to get started on Windows development in my new job. I knew it would not be trivial but the first thing I'm trying to do is complete and integrate a netvmini port driver (started by a co-op student) into one of their C++ apps. I am struggling to get the build environment going...
The project was started in Visual Studio 2013 with a Windows 7 target. When I now open it in Visual Studio 2015 and try to build the solution I get:
"Unknown or unsupported property value Win7 for TargetVersion"
for each project. This also happens if I set the configuration to Win8 (both release and debug). If I set it to Win 8.1 I get:
"An SDK corresponding to WDK version '8.1' was not found. Please install the SDK before building"
I have installed every WDK and SDK I can lay my hands on from Windows 7 to Windows 10 using both the web and the VS2015 installer. I have even installed Visual Studio 2013 again but I can't even seem to get the WDK to integrate with that.
The end goal here is to be able to build this (and hopefully debug remotely in kernel mode) from my Windows 10/VS2015 workstation for targets from Windows 7-10. Any advice or documentation that details how to integrate new build platforms into VS would be helpful (all the MS documentation just tells me what I can do if I install this or that, but not HOW to do it)
I also had the same problem after running the Project Upgrade tool.
I discovered when making new configurations that "Win7" and "Win8" TargetVersion are now "Windows7" and "Windows8".
The upgrade tool does not make that change for you but I was able to manually edit my upgraded project with those changes and got it to build for all targets.
I discovered that the installer doesn't install the windows 10 SDK by default. So all the installing of other SDK's was useless. I Also found out that by installing the Win 10 SDK through the VS 2015 installer it integrates and allows me to build for targets back to windows 7 in VS 2015.
We've a solution (~200 projects + tests) which is running on Windows XP SP3, compiles in VS2010 32bit configuration.
The plan is to migrate to Win7, VS2013 and compile under 64-bit.
I know that there is a new MS Windows SDK available for Win7 and VS2013 must make use of it.
What is the most correct order of doing all this stuff - correct in a sense that it will cause minimum hassles, minimum number of repetative operations etc.
Maybe some useful tips..
Thanks
I would migrate to Visual Studio 2013 first, run a full suite of regression tests, and then port to x64.
I'm trying to set up continuous integration at my current place of work. It's not something I've done before so I'm fairly certain that there will be a few steps I've not done or things I'm un-aware of.
I installed TeamCity Professional 7.1.3 on a build server (Windows Server 2008 R2). I've created a simple .NET application that has no database connections and only three NUnit tests. This app uses .NET framework 4.
I set up a build step using NUnit and received a number of errors but I've now resolved them, basically by installing the .NET framework on the build server.
I'm now adding an extra step using Visual Studio but TeamCity now displays the warning 'No enabled compatible agents for this build configuration'.
This question looks similar to mine:
What do I need to install a Visual Studio 2010 (sln)-compatible Build Agent in TeamCity? and it helped me solve the problems I had with NUnit but not for this current problem.
Is there something I've missed during my set-up? If I'm building and running tests with NUnit do I need to bother with this second step?
You installed the full framework, correct -- not just the client pieces? Here's a TeamCity forum post on how to resolve the Unmet requirements:DotNetFramework4.0_x86 exists compatibility error when you've previously installed the framework.
How to develop app in Visual Studio and then deploy apps to Linux machine (OS - Ubuntu, web server - Nginx). Can any explain the steps, it will be a great help
I would say that there are three ways how you can develop apps for Linux using mono.
First is using only Visual Studio for development and from time to time deploy your app to Linux to see potential issues. I personally use this scenario because it's simple and when you are not messing with MS specific stuff or yet fully unsupported things then you shouldn't have problems (at least I didn't so far). Disadvantage is that you will discover mono specific problems only during runtime on Linux machine.
Second approach is using Visual Studio with Mono Tools. I tested it when it was in beta and it was sometimes quite handy (you will move the phase of discovering mono specific problems to your dev environment, however you can still have some certain issues on Linux machine), but since this tool doesn't support debugging for now I don't use it personally.
Third approach is to use only MonoDevelop on Linux (since debugging is now supported only in Linux). With 2.2 release this IDE becomes really good and suitable for development however I have tested only console and basic ASP.NET MVC apps so I can't tell you if it's ready for bigger projects.
Deployment to Linux is quite easy - I just installed proftpd on Linux machine, configured it and copied project there from Windows machine.
If you are developing an application for Linux in C (as Nginx is) or C++, you need to develop on Linux.
There are many IDEs for Linux that you can use for this.
You can also try to run Visual Studio in Linux using Wine.
Use Mono on Windows and compile your apps with it , I guess Apache is only supported ... Disclaimer - I do not have personally experience with it ...