In previous versions of VS, we were having Create Unit test Wizard option, which actually uses the dll and create basic test methods for each classes.
But that option is not available in VS 2013.
So is there any template which i need to download to get that option back into the VS2013.
1)I think this vs2013 extension can help you:
https://visualstudiogallery.msdn.microsoft.com/45208924-e7b0-45df-8cff-165b505a38d7
Or:
2) If you have resharper , it is built in function there too.
Or:
3) Another option is to solve the issue using this workaround:
http://dl.my/2013/create-unit-tests-function-not-available-or-disabled/
Let me know if it helps you... if not, I'll try to support with a different answer.
Related
Thank you for taking some time to check my question,
so I need to build corelDraw 6 add-in using VB.NET
so I take 2 ways (1) just try to use VSTA editor ,but didn't work :( I got this error, try to switch .NET version to 3 or 2 but didn't work too, just show the following message >>>>>>>>>>
CorelDRAW
Unable to attach. Check for one of the following.
The application you are trying to debug uses a version of the Microsoft .NET Framework that is not supported by the debugger.
The debugger has made an incorrect assumption about the Microsoft .NET Framework version your application is going to use.
The Microsoft .NET Framework version specified by you for debugging is incorrect.
Please see the Visual Studio .NET debugger documentation for correctly specifying the Microsoft .NET Framework version your application is going to use for debugging.
any advice ...?
(2) I used my VS 2010 and created a class library project ,then used the code in the VSTA and inserted all related references to corelDraw -> build -> all goes well I got my dll file :( but how to make it work as add-in inside corelDraw 6
any advice ...?
Thank you So much,
Ooh I just solve it :)
I copy the dll file which I did using VS2010 in C:\Users\\Documents\Corel\VSTA\CorelDRAW\Addins
re-open corel and it just worked, thank you all
any idea answer about way (1) will be reate too, thank you
I am creatinig Managed Extensibility Framework extensions for some program. That program uses dll files witch i create. I dont have visual studio project of that program, but i have that program. I can run these extensions using that program, but cant debug them properly.
Is it possible to use visual studio debugger to debug my code?
I found solution to this, thanks!
I found solution to this by my self, but thanks for sugestions.
I can use that app for which i am creating this extension, class libary project.
I press properties on project, then select debug tab and set "start external programm" an set it o that main app. then i press f5 and that app starts and when it uses my extension i can debug it using visual studio debugger. And i forgot to tell that i am creating this in C#.
http://msdn.microsoft.com/en-us/library/68c8335t.aspx
I believe what you are looking for can be found here:
http://msdn.microsoft.com/en-us/library/0bxe8ytt.aspx
According to this article, you could use the "Add Existing Project" dialog in you solution (for your DLL) to add the executable that you do not have the solution for. Because you are using MEF, it might get a bit tricky and you might want to create a new solution for debugging instead. However, this seems to be the general way to handle your situation. Since you have the source code for your DLL, I believe it should allow you to step through your code fully at the very least.
Note: You will need to make sure you have Visual C++ installed in your development environment.
If you are trying to debug the assembly code, then you can use the technique discussed by #BiggsTRC, if you are simply trying to identify why parts aren't being loaded, you could consider looking at the Composition Analysis Tool (mefx). This is a command-line tool for analysing a set of parts and finding out where failures may occur during composition.
In my solution (under VS2008) I have few web projects, few class libraries, unit test project.
It seems like during solution conversion to VS 2010 the target framework for UnitTest projects was changed to .NET 4.0
When I try to change it back (I need to check how system works in .NET 3.5 and compare with current behavior) I am receiving the following error:
Attempted re-targeting of the project has been canceled. You cannot change the specified .NET framework version or profile for a test project.
Why I can't change it? How can I do?
Thanks a lot!
Unfortunately, found a negative answer:
http://connect.microsoft.com/VisualStudio/feedback/details/483939/unable-to-change-target-framework-version-on-unit-test-projects
closed as "Won't fix"
http://connect.microsoft.com/VisualStudio/feedback/details/514130/visual-studio-2010-beta-2-silently-upgrades-mstest-test-projects-to-net-4-0
clase as "by design"
:(
P.S. I like one of the suggested workarounds: don't use MS Test :)
I have installed VS 2010 and want to migrate all code written in VS 2005 to VS 2010.
Please note that we do not have VS 2008, all code are in C# 2.0 and Asp.net 2.0 only.
Can anyone please tell me now what all points need to be considered while migrating.
Update:
I have set target framework to 2.0 for all of my Libraries and web projects. It complies without any error!
However, when site opens in IE (Set to default.aspx), it gives me error as below:
InternalXmlHelper.vb(9) : error BC30560: 'ExtensionAttribute' is
ambiguous in the namespace 'System.Runtime.CompilerServices'.
<Global.System.Runtime.CompilerServices.ExtensionAttribute()> _
Keep all the target framework settings to .NET 2.0. This way, there should be no compilation problem at all.
The changes that you should see are the solution and project files only.
Start with known good solutions in source control (and label—you shouldn't need to go back, but easy to add an extra safety net).
Open each solution in VS2010, allow the conversion wizard to do the conversion.
Resolve any issues.
Honestly, if you're just upgrading VS 2010 you don't really need to consider much. Just keep backups (any real SCM product will do) and you're good. You don't have to upgrade your applications' runtime targets at all if you don't want to.
If you're building with CAS policy, you might run into issues with using MSBuild 4.0 to build you 2.0 applications. If you don't know what I'm talking about, never mind.
My advice is to make sure everyone's "checked in" to your source code provider, and run the conversion wizard and see how it goes.
I am hoping someone can help me with this. What I have been looking around for but can't seem to find is if there is someway to add an event, or anything else that will allow a visual studio plug-in to watch for an external reference to be added to a currently open solution / project?
Or even better yet would anyone happen to know of an add-in that automatically adds all controls from a referenced dll into the visual studio toolbox?
Thanks.
Not exactly what you asked, but I've written a Visual Studio 2008 Integration Package, and if I recall correctly I could override the "add reference" method, as well as inherit the "reference node" and thus change its behavior, for example its constructor.
This functionality might be missing from an add-in (which is more limited than an integration package), so you might consider writing a package instead.
I have written a macro that will change a file reference to a project reference if you add the project to the solution (and vice versa), but I don't think that's what you want?