Using gallio in visual studio - visual-studio-2013

Did anyone able to configure gallio in VS2013. I used it in VS2010.
But I am not able to use it VS2013. I googled a lot and didn't get any solution

As per my information, Gallio is not supported in VS2013.

Related

Visual Studio 2013 support for Parasoft C++Test 9.6

I'm a newbie for using Parasoft. We are planning to use Parasoft C++Test 9.6 version for Code Coverage. But, I'm not sure how to import a Visual Studio 2013 project into this. In the Advanced Settings I selected 'Visual Studio 12.0 Tool chain'. But, auto detect couldn't find the compiler and linker. So, I manually gave the path to the 'cl.exe' & 'link.exe' in the installation folder of VS2013. But, still it gives the error 'Cl is not in the PATH' while building.
Please let me know what I'm missing. At the basic, is it possible to import VS2013 project into this version of Parasoft?
Thanks in advance.
Gomu,
I suppose that you are using Parasoft C++test Eclipse edition (standalone), and it might be easier for you to get from Parasoft Parasoft C++test Visual Studio plugin.
Then you don't have to import Visual Studio project, but you will have whole functionality of C++test in Visual Studio.

Nunit tests are not shown in Test Explorer of VS2013 Express

I have visual studio 2013 express edition and I have referenced NUnit 2.6.2 version DLL, but I don't know why the Test Explorer is not showing the test cases.
I did searched for questions with similar problem and tried doing what suggested like the Nunit Framework from NuGet package and making sure the Nunit reference and adapter version are correct, etc. but none of them resolved the issue.
Right now I have cleaned up everything from my Visual Studio and have only Nunit 2.6.2 DLL added in reference.
Following is the out put from Package manager console.
PM> Get-Package
No packages installed.
Can someone please help me to know how to get the Nunit tests in my Test Explorer ?
You need the NUnit Test Adapter and not the NUnit 3 Test Adapter since you are using version 2.
Sorry... The NUnit Test Adapter and the NUnit 3 Test Adapter are both Visual Studio extensions. The Express editions of Visual Studio don't support extensions. Period.
You need to switch to either VS2015 or VS2017 Community Edition, which do support extensions. Then you can install either of the two adapters - depending on what version of the NUnit framework you are using.

TypeScript refactoring stopped working in VS 2013 RC2

I have just installed VS 2013 RC2 and TypeScript refactoring stopped working. It disappeared from context menu, and pressing Ctrl+R, Ctrl+R gives the following error message:
The key combination (Ctrl+R, Ctrl+R) is bound to command (.Refactor.Rename) which is not currently available.
I have tried restarting VS, didn't help. Any ideas, workarounds?
Edit:
I have submitted a bug to Microsoft. Please upvote it if you have the same issue:
https://connect.microsoft.com/VisualStudio/feedback/details/860463/typescript-refactoring-stopped-working-in-vs-2013-rc2
Microsoft posted the following answer to my question on MS Connect. Seems that while refactor/rename was available in VS Express Edition with TypeScript 0.9, in TypeScript 1.0 it's only available from VS Pro upwards.
Posted by Microsoft on 19/05/2014 at 09:25
Thank you for reporting this issue.
Refactor/rename and NavigateTo are features that are found in the Pro+
versions of TypeScript in Visual Studio 2013. The Pro+ tools are aimed
at helping users work with larger codebases, so there is a focus on
building up tools to help support those codebases in those versions of
Visual Studio. We're working to continue to refine to make the
experience best across both Express and Pro+, with the right features
to help users who want to learn TypeScript and those who want to move
to using TypeScript in larger projects.
For me it happened because of resharper conflict. I uninstalled resharper and restarted visual studio

Test templates missing in visual studio 2010 ultimate

Test templates such as Coded-UI testing and Web performance testing are missing.
I originally had visual studio 2010 professsional installed. I upgraded to visual studio 2010 ultimate just so that I wanted to use Coded-UI testing and Web performance testing features.
However, the options seem to be missing. It is as if the upgrade has not made a difference with regards to additional testing templates.
I have a visual studio 2010 ultimate evaluation version installed.
I have checked in Tools > Options > Test tools: but doesn't seem to have anything in here that I can change. Searched online too, everywhere seem to suggest that after VS 2010 Ultimate installed, you should be have the templates to create the additional tests.
If I go to menu, Test > New test > Add new test dialog,
Here I just have "Basic Unit test", "Ordered test", "Unit test", "Unit Test wizard"
Have also tried, Right click the Test project, Add > no option for Coded-UI test here!
Has anyone come across anything like this?
Any advice is appreciated,
Thanks, Fred
Edit 09:22 GMT 26-05-2012:
I used the visual studio ultimate web-installer. I double checked the options to select while installation. There is no option specific to testing here. So, selected Visual C# + Visual Web developer + Graphics library
I had this issue when upgrading from VS2010 Professional to VS2010 Ultimate. I think it may have been caused by having already installed SP1 in Professional. I solved it by doing the following:
Go into Windows Add/Remove programs and run a Repair against VS2010 (takes a LONG time).
You might need a reboot, do not skip the reboot if prompted.
Re-run VS2010 SP1 setup and run Repair when prompted (takes a LONG time).
That should do the trick! Run up VS2010 and the templates should now be accessible!
Good luck!

logging libraries for visual studio 2010

Visual Studio 2010
I was using log4net for Visual Studio 2005. However, I am now using visual studio 2010.
log4net is not available for that framework.
Is there any other logging libraries out there that I can use?
Many thanks,
Just to clarify, the IDE isn't really a factor here. That said, use Enterprise Library.
If you want to stick with log4Net, it may be as simple as changing your application's target framework. See this post that describes how the author was able to get log4Net up and running: http://krishnabhargav.blogspot.com/2010/02/using-net-35-clr-20-dll-inside-visual.html

Resources