Is there an Expression Tree Visualizer for VS 2012? Have had a search but have found the VS 2008 popping up all over the place, and the new VS 2012 doesn't have a Visualizers folder in the installation directory. Or, am I missing something that I should be able to switch on?
What you can do is fix the visualizer for vs 2010 so it works in 2012. This is very easy. Just get the source from this project : http://exprtreevisualizer.codeplex.com/ and change the DebuggerVisualizers assembly reference of the ExpressionTreeViewer project to :
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v2.0\Microsoft.VisualStudio.DebuggerVisualizers.dll
So that it works with the newest version of vs2012. After that copy the results to
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Packages\Debugger\Visualizers
and it should work
No but you have DebugView, in debug mode, there's a proxy for the class with the same properties and an added one DebugView. It's text like. Also Mono.Linq.Expressions has a text writer for expressions that makes C# code, check it out.
I seem to make bad *.dll's when this issue re-occurred for me. I started a GitHub repo with the solution. I included a built and the compiled *.dll which can be downloaded by clicking "View Raw" on this file.
Copy this *.dll to your visualizer directory of choice. I use C:\Users[CurrentUser]\Documents\Visual Studio 2013\Visualizers
(Disclaimer: I am the author of the visualizer in question.)
I've written a debugging visualizer for Visual Studio:
Related
I have visual studio express 2012
and it was working fine earlier I had run my solution once. But now when I do it, there appears a dialog box with the message!
the Microsoft.VisualStudio.Web.PasteJson.JsonPackage, Microsoft.VisualStudio.Web.PasteJson package did not load correctly.
the problem may have been caused by a configuration changhe or by installation of another extension. You can get more information by exmamining the file
C:\Users\AppData\Roaming\Microsoft\VWDExpress\11.0\Log.xml
continue to show this error message?
How do I get rid of this error?
I started to see this on the fresh windows & VS 2013 Ultimate with Update 2 installation.
To resolve the problem, close all Visual Studio instances head over to
C:\Users\<your users name>\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache
and delete all the files in the folder.
It worked fine for me. Thanks to this article.
Not relevant to VS 2012 express, but I experienced this problem with VS 2013 Premium. I had recently added the productivity power tools extension. To get back up and running, I loaded Visual Studio in safe mode:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE>devenv /safemode
And un-installed the productivity tools. The errors went away.
You need to clear the ComponentModelCache folder or rename it. For Visual Studio 2013, it’s located in the %LOCALAPPDATA%\Microsoft\VisualStudio\12.0 folder.
Refrence:
http://www.rajapet.com/2014/02/when-the-editorpackage-does-not-load-correctly.html
I had Visual Studio 2013 Professional and I got the same error. I couldn't remove it until I repaired VS installation. It took a while but now it works fine.
I had this problem as I had an older version of VS2012 Express (release on Web Platform installer dated 15/08/2012).
Try installing 'Visual Studio 2012 Express for Web (Latest)' with release date 22/10/2012 from the Microsoft Web Platform Installer.
That is all I did and I no longer get those messages.
I asked this question about VS2010, because the location changed from where it was in VS2008, and I couldn't find it.
Now they've done it AGAIN!!!
So where is it now?
Why have they done this again? Apparently just to keep us on our toes. Remember that it was under a folder in Microsoft Visual Studio 10.0 called VSTSDB? Well, that folder still exists in VS2012, but it is now vestigial. You have to look in another place. In fact it seems to have been migrated back to where it was in an earlier version of Visual Studio. Look here:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\SQLDB\Extensions\SqlServer\Items
Talk about a convoluted path.
I opened my vs2010 solution with vs2012 but it didn't make any conversion as from 2008 to 2010 was happening. So my solution still remains the same as 10 label on it. when I make a new solution of course it has 11 label on it. I haven't got any problem running like that but I am curious. Is there any difference? if yes, how to convert into vs2012 solution?
I managed to 'convert' the solution file to change the line containing '# Visual Studio 2010' to '# Visual Studio 2012' in the .SLN file.
Manual editing of the solution file is not necessary, or recommended. Simply open the VS2010 solution in VS2012, left-click the solution (at the very top of the Solution Explorer), then use File | Save As to overwrite the original file. This will effectively convert the VS2010 solution file to a VS2012 solution file.
There are some exceptions, but mostly you'll be able to open the same project and solution files files in both VS2012 and VS2010 SP1.
VS2012 may convert projects when you first open them, but the changes are (except noted in the document linked) backward compatible with VS2010 (ie using conditionals where needed to only apply to either version when loaded) Most project types will be left entirely untouched though.
It is about Visual Studio 2012 Compatibility
If you created your assets in Visual Studio 2010 with Service Pack 1 (SP1), many of them will load and run in Visual Studio 2012 without any further action on your part.
Many assets will also open again in Visual Studio 2010 with SP1 without any issues, even after you open those assets in Visual Studio 2012
For C++ projects it makes a difference, as the 2012 compiler (VC11) will only be used on projects that are explicitly 2012, not on 2010 projects opened in VS 2012. Some C++11 improvements are available with the VC11 compiler but not with VC10 (see this SO Answer for a summary), including:
Range based for-loops
New standard library headers (atomic, mutex, thread,...)
Smaller standard library container sizes
(And more to follow when the Nov 2012 CTP is delivered to VS 2012)
In order to convert from VS 2010 project to VS2012 there is no need to manually edit the solution file or 'Save As' over the existing project. Instead:
If you decline the update when first prompted, you can update the project later by opening the Project menu and choosing Update VC++ projects... [at the top of the menu options]
From MSDN's "How to: Upgrade Visual C++ Projects to Visual Studio 2012"
(This page was linked from #Joachim's MSDN link, but I wanted to have the answer here on SO since a number of other answers suggested manual workarounds instead of this VS 2012 feature)
In my case, I had some Visual Source Safe stuff (my project was created with Visual Studio 2003/2005, yes, very old!)
Once I manually removed the VSS stuff, the conversion succeeded.
PS: I know it's about VS2010, but maybe this helps others.
You can convert a project from VS2010 to VS2012 by doing the following:
Add the 2010 project to your VS2012 solution by right-click on your solution in the Solution Explorer and Select Add --> Existing Project...
The project will appear in the solution and will have (Visual Studio 2010) appended to its name.
Right-click on the added project and select Properties.
In the Configuration Properties --> General pane, change the setting in Platform Toolset field to Visual Studio 2012 (v110)
Repeat for each configuration type, e.g. Release and Debug.
I came across this question while googling for a solution to a specific problem: MSBuild was failing to execute the Publish target against a VS2012 solution that had started life in VS2010 when called from the command line (specifically through TeamCity):
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
MSBuild was looking for the Azure SDK 2.3 targets in the VS10 location (C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets). The cause is explained by Sayed Ibrahim Hashimi in a blog post and, as I understood it, boils down to some decisions they made while enabling cross-version compatibility for solution files. The solution was simple: add the VisualStudioVersion property to the MSBuild invocation, something like this:
msbuild.exe MyAwesomeWeb.sln /p:VisualStudioVersion=11.0
Practically speaking, this overrides the following in each csproj file:
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">10.0</VisualStudioVersion>
Presumably you could get the same result by editing all of these by hand to replace 10.0 with 11.0 but that might break backwards-compatibility -- I haven't tried it. I also haven't tried an update to VS2013 to see if the problem persists.
So to wrap this up by answering the question: yes, there are some differences before you "convert" (using any of the methods offered by other answerers) and some differences remain afterwards.
This is slightly different, but along the same lines so in case it helps anyone:
I was loading a project where it looked like it was loading and then kept showing all projects as unavailable. No errors were on the migration report. I tried reloading the solution and projects many times, using various methods including suggestions here.
Finally I found a "Resolve Errors" option when right clicking on the solution in the Solution Explorer. VS went through a load process again and it worked; no problems.
I don't know what it did differently that time, but apparently it made a difference.
it's to simple just edit the .sol file
change the version to 11
like this
Microsoft Visual Studio Solution File, Format Version 12.00
Visual Studio 2012
I am developing a command line application that creates a full Visual Studio 11 solution made of a single VC++ project and that tries to compile it in the end using MSBuild.
The problem I am facing is strange.
If I execute my command line program inside Visual Studio 11 it works; if I instead launch it outside the development environment it throws me the error:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(511,5): error MSB8008: Specified platform toolset (v110) is not installed or invalid. Please make sure that a supported PlatformToolset value is selected. [f:\ABC.vcxproj]
The command I am using is the following:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe f:\snake\W9A30040.vcxproj /property:PlatformToolset=v110;Configuration=Debug /v:quiet
But I have the feeling that PlatformToolset=v110 is ignored and MSBuild use v100 (Visual Studio 2010).
Do you have any suggestions how to tell MSBuild to compile for v110 Platform Toolset?
I ran into the same problem as well with the full release of VS 2012. You can also set the VisualStudioVersion as a property with MSBuild as opposed to dealing with environment variables as mentioned in the accepted answer. For instance:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe .\myproject.vcxproj /p:VisualStudioVersion=11.0
The environment variables approach I'm sure work just as well, I honestly didn't try that as I was trying to stay away from having to modify the environment variables.
Make sure that the top of your .SLN file looks like this:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012
When you double-click on the solution file, it's the # Visual Studio 2012 that controls which version of Visual Studio is loaded (and controls the icon displayed in Windows Explorer).
However, when you run MSBuild, it looks at the Format Version 12.00 part.
Confused?
This is confusing, since Visual Studio 2010 is version 10.0 and Visual Studio 2012 is version 11.0 (not 12.0), and using the version 12.0 solution file format causes MSBuild to (implicitly) set VisualStudioVersion to 11.0.
I found a workaround for this issue; could be a problem of Visual Studio 11 Beta that will be resolved before official release.
Anyway, if you are interestedm just set the environment variable "VisualStudioVersion" equal to "11.0" before calling MSBuild.exe.
In batch files
set VisualStudioVersion=11.0
or in VB.NET
Environment.SetEnvironmentVariable("VisualStudioVersion", "11.0")
Starting with Visual Studio 2013, MSBuild is now part of Visual Studio, and the correct path should be $(MSBuildToolsPath) (“C:\Program Files (x86)\MSBuild\12.0\Bin”). If you use msbuild.exe from the .Net framework folder (“C:\Windows\Microsoft.NET\Framework64\v4.0.30319”) it will not able to distinguish the vs2012 and vs2013 versions.
Use the menu based options to do this. From VC++2010 Express:
- Right click on the main file of the project (not the solution itself at the very top of the tree).
- Click General.
- Find Platform Toolset on the right side of the dialog, top half.
- Change from v110 to v100.
- Click OK.
----- Done ------
Microsoft provides a batch file to set all the EnvVars
You find it in the Start Menu under "Microsoft Visual Studio 2012/Visual Studio Tools" or in the Visual Studio folder ("C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\VsDevCmd.bat")
How can I do that ? Can I work in VS2010 IDE but have it compile with the VS C++ 6.0 compiler?
And can I work in VS2010 IDE and have it compile by using the the VS2008 compiler ?
you need the Daffodil extension
I know it is possible to achieve this with VS2008 IDE and I'm 99% sure it is the same with VS2010 (but I don't have one to try with). Make a batch file in which you first need to call VCVARS32.BAT file that is included with VC++ 6.0 and then start Visual Studio with "/useenv" switch. You will then use this batch file to start Visual Studio.
.bat file:
call "C:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32.BAT"
start "" "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" /useenv
NOTE: This is path to VS2008 IDE, you need to change path for VS10 by yourself (probably just needs changing number 9 to number 10). Also if you are using 64bit OS you will need to change both paths to use "Program Files (x86)".
Isn't possible.
You can use VS2010 C++ compiler to compile VS6 code w/o any problem.
take care about the solution will be migrated to new format (old one is saved as backup)
Here is link below which talks about visual studio 2008 but you can refer it to execute similar steps on visual studio 2010.
http://resnikb.wordpress.com/2009/10/28/using-visual-studio-2008-with-visual-c-6-0-compiler/