I have a VSTO Word add-in that is built with Visual Studio 2010, in C# targeting the .NET 4.0 framework.
I have Visual Studio Ultimate 2010.
I also have a bug that no one in QA for the life of them can figure out how to reproduce -- it just happens sometimes -- we're pretty sure it's our code that's causing it -- but yeah, that's that.
What do I have to do, to make IntelliTrace run on a machine without VisualStudio and attach it to my add-in which is loaded by Word at run time and have it produce .ITRACE files that I can open with Visual Studio 2010 so that I can step through the code and see what's going on?
Related
I have a project from VS Studio 2010 that I want to work with in VS 2015. When I start this Project with VS 2015 I receive an error saying something like "compatibility-Error (Version)".
How can I successfully convert a Visual Studio 2010 project to use with Visual Studio 2015?
Without you going into any more detail about the actual error. (error numbers / screenshot) it will be very hard for any of us to give a real answer. Therefore I am going to suggest you take a look at Troubleshooting Unsuccessful Project Upgrades.
Something else to check out might be the Porting, Migrating, and Upgrading Visual Studio Projects guide
One of the key things mentioned in the 2nd link I provided is:
The following list describes support in Visual Studio 2015 and Visual Studio 2013 for projects that were created in Visual Studio 2012 or Visual Studio 2010 SP
Therefore I'd recommend upgrading the 2010 version to SP1 first. (if this is still installed that is)
One further thing to note is that if you keep the old version of Visual studio installed you can import a project which is made with an older version and skip the update. Visual studio 2015 will then use parts of the older version itself to open the project.
For details you can read How to: Upgrade Visual C++ Projects to Visual Studio 2015 page and the equally useful Installing Visual Studio Versions Side-by-Side page.
It appears that there are issues when moving from VS 2010.Net to VS 2015.Net and may require that you build the project from scratch and copy the code over. VS 2015 requires a Namespace. There are a number of designer issues on control that require the style page be used since various attributes have been removed. Something still, however, do work but you need to review the HTML, specifically things like Font and alignment. While it's a pain it isn't a big deal since it requires mostly cut and paste.
If you are having issues converting web projects the projects may have originally been created as a "web site" rather than a "web Project" . Try opening the application as a web site and see what happens. At least that may help get you to the point you can actually get to the code to convert it in VS 2015. Hope this helps.
Try to Right-click the solution, then select "Re-target solution".
I recently started a new job, and got a machine with Visual Studio 2013 Proffesional installed. This would be great, except the colleague that I'm working with is using Visual Studio 2010. As far as I know, there is no way to work on the same project (or solution), without having quite a lot of issues, is this correct?
And if so, is it still possible to download Visual Studio 2010 (from a reliable source)? I cannot seem to find it anywhere in my MSDN subscriber downloads. All I can find is a stuff like service packs, tools, etc. Did they terminate the support of it?
You work on visual studio 2013 but there are option to select which version of visual studio you want select 2010 and run your project.
You should be able to open Visual Studio 2013 solutions in 2010, if you install Visual Studio 2010 SP1. There is a possibility that some project types won't be supported, but the solution should open.
I apologize as this may seem as bit of a general question.
I have developed a couple of VB programs using Visual Studio 2010 Professional and others on Visual Studio 2013 Ultimate. While I have not done any work in about a month with either version of Visual Studio, I thought I would go in and start work on a new project.
After entering some code in Visual Studio 2010 using WinForms, I found I was unable to run the code in the debugger (pressed the start button and F5).
It acted like it would start, then it just stopped and returned back to my code.
I thought I would try it on another program that was completed and working a couple of months ago, but I had the same issue present itself. Attempting to use Visual Studio 2013 had the same effect.
Any ideas from anyone? Has anyone else experienced this same issue recently? Once again, I do apologize for the lack of examples here, but I'm not sure what I can include to show the problem.
IMO, you should try resetting visual studio settings (and a restart may solve the issue)
you can try following
do it via visual studio -> tools -> import export settings
or you can run this command devenv /resetuserdata
or checkout this http://msdn.microsoft.com/en-us/library/ms241273.aspx
If Visual Studio includes Visual Basic, why can't I open a VB 6.0 file in Visual Studio 2010?
Because there's a difference between Visual Basic 6.0 and Visual Basic .NET which is what Visual Studio 2010 includes.
Darin is basically right but omits an important detail.
There's a difference between VB6 and VB.Net, and Visual Studio 2010 includes VB.Net
Earlier versions of VB.Net included an upgrade wizard to help convert VB6 code to VB.Net. This was dropped in Visual Studion 2010. You might want to use Visual Studio 2008 to help upgrade your VB6 to VB.Net, and then migrate to Visual Studio 2010 later. Upgrading VB6 to VB.Net can be a large task.
That's correct. I upgrade to 2008 then to 2010. You have to run the installed program from vb6 first then it will upgrade. You might have terminal failures from unfound assemblies. Go into the .vb form file with a text editor. REM out any failed to load assemblies from the fail report. Then you can re-write the VB code for code errors as the lingo changed. Next upgrade to vb 2010 using that wizard and re-write for new lingo again.
Form sizes are converted to vb6. in 2008, then that is scrapped in 2010, don't re-write that in 2008, if you're upgrading right away, you'll have to re-write in 2010 anyway.
Common file open/save/browse/color/font routines become vb powerpacks 10 which you load with your vb 2010 assembly. You have to re-insert the new common assemblies into the form from the toolbox and re-work the code. There's a bunch of stuff there, but it is do-able.
I have not used VS 2010, but based on my readings, the latest VB is effectively a new language altogether. Since introduction of VB .NET, VB 6.0 has become a stagnant language.
I've used TestDriven.NET in the past (with Visual Studio 2005), but now that I've got a new installation of Visual Studio 2010 on a different computer, I can't see either the Add-In Manager, or the TestDriven.NET stuff, even though I have them installed.
Help, please! It's making me bonkers.
Note: trying with current version (3.0)
This problem was due to the fact that I was using one of the free versions of Visual Studio, which did not allow for Add-ins.