I set up a new machine this week. It is running Windows 7, 64 bit.
I installed Visual Studio 2010 Professional, then Resharper 5.0, rapidly followed by Resharper 5.1 when it came out soon after.
Since I have a project with tests in MbUnit, I have installed MbUnit/Gallio, using the 3.1.397 version x64 msi installer from here.
I was expecting to see the green gutter icons that Reshaper puts next to my tests, but I do not. I tried removing Gallio and installing the 32 bit version. No change. I re-installed both Resharper as Gallio as per this question, but this produced no change. In this procedure, %APPDATA% is set to C:\Users\Me\AppData\Roaming, so I deleted C:\Users\Me\AppData\Roaming\JetBrains. I have also tried unstalling both Reshaper and gallio, deleting all Resharper and Gallio data from AppData\Roaming, AppData\Local, and C:\Program Files (x86), and then installing again from a cmd running as admin, but again, no change.
Resharper has no plugins listed in the Plugins dialog, and in the Resharper|Options|Unit testing item the "unit testing providers" listed are MSTest and nUnit.
Visual studio has two other Add-ins listed: ".Net Reflector" and "Visual Git".
What do I have to do to get MBUnit working in Resharper?
Which of these two tools provides the integration? Should I install Resharper or Gallio first?
Where do the integration files or settings go? It has been suggested that I should have a "resharper plugins directory" in C:\Program Files (x86)\JetBrains\ReSharper\v5.1\Plugins or similar but this is not present at all.
R# 5.1 RTW is supported by Gallio/MbUnit starting from v3.2.512. You can download the latest binaries of the Gallio bundle in the daily builds repository. v3.2 is not officially released yet but it is very stable already.
UPDATE 1: R#5.1 officially supported.
UPDATE 2: Gallio v3.2 RC with R# 5.0 and 5.1 support.
Related
I am getting build errors while compiling POCO first time with VS13. I think it is not compatible with VS13. Any idea, how to fix this without downgrading my Visual Studio?
C:\Users\as\Documents\Visual Studio 2013\Projects\poco-1.4.6p4> buildwin.cmd 110
error MSB8020: The build tools for Visual Studio
2012 (Platform Toolset = 'v110') cannot be found. To build using the v110 build tools, please install Visual Studio 2012 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Upgrade
Solution...". [C:\Users\asjaiswal\Documents\Visual Studio 2013\Projects\poco-1.4.6p4\Net\samples\WebSocketServer\WebSocketServer_vs110.vcxproj]
Thanks.
Version 110 is Visual Studio 2012. VS 2013 is version 120 and those projects are not available in the releases yet.
VS 2013 support has been introduced in develop branch, which also has (in addition to the old batch files) the PowerShell build script (see announcement) which automatically detects available VS version if present.
EDIT: VS2013 projects are available now.
Background
I am open sourcing a few old Visual Studio applications I created a while back. I have created new solutions using my new VS2012 environment for them and have gotten the projects set up as git repositories. I got everything working fine in Visual Studio 2012 with no changes to the source code, all I needed to do was make sure I was linking the proper libraries in the new project configurations.
I would like to configure these projects as to have maximum compatibility for others downloading the project from Github. On this machine I have VS2010 installed alongside the latest VS2012 version. After I got everything working right for both of the projects in VS2012, I tried to open them up in VS2010.
When I tried to build I got a single error:
Specified platform toolset (v110) is not installed or invalid.
Please make sure that a supported PlatformToolset value is selected.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets 518
What I Tried
So I opened up the properties for the project, went to Configuration Options --> General and the Platform Toolset was indeed set to Visual Studio 2012 (v110). This input is a drop down box and the v110 value is not listed, instead I get two choices:
v100
v90
These correspond to VS2010 and VS2008 respectively. If I change the value to v100 and rebuild I get no errors and my program runs just fine in my Visual Studio 2010 environment.
When I open the project back up in Visual Studio 2012, if tells me that I have an old project file and asks if I want to upgrade, I say yes and it upgrades. I rebuild and run to make sure everything is still working. When I open the configuration options in VS2012 the Platform Toolset is set back to `Visual Studio 2012 (v110) but clicking the drop down input there are several more choices listed:
Visual Studio 2012 (v110)
v110_wp80
Visual Studio 2012 - Windows XP (v110_xp)
Visual Studio 2010 (v100)
Visual Studio 2008 (v90)
‹inherit from parent or project defaults›
My Questions
This has led me to several questions. I am going to pose them all. It would be nice to get as much information as I can, but a good answer to just one of them would probably solve my problem.
If I'm not using features specific to newer versions of Visual Studio, is it possible to set up a solution which can be opened and run without modification in as many versions as possible (ie. 2008, 2010, or 2012)? If so, how?
If I set the Platform Toolset to v90 (VS2008) from within Visual Studio 2012, and it's able to build and run, does this mean that it will build and run for users with VS2012, VS2010, and VS2008?
What exactly does the <inherit for parent or project defaults> option do? What would the project defaults be set up as? Can this be used to tell Visual Studio to try to using whichever installed Platform Toolset will work.
Are there any other options besides Platform Toolset in Visual Studio that I can set to increase compatibility with others' development environments?
This is a somewhat tricky situation. One of the underlying problems here is that VS2010 and VS2012 use MSBuild to build C++ projects, but VS2008 farmed it out to VCBuild instead. You can see this by comparing the project files. VS2010/VS2012 use .vcxproj, while VS2008 uses .vcproj.
If I'm not using features specific to newer versions of Visual Studio,
is it possible to set up a solution which can be opened and run
without modification in as many versions as possible (ie. 2008, 2010,
or 2012)? If so, how?
For maximum compatibility, you want to target the lowest common denominator (i.e. vc90 in this case). Note that when you do the upgrade, the solution file and project files get upgraded to the latest version, which may break compatibility with older versions of Visual Studio.
If I set the Platform Toolset to v90 (VS2008) from within Visual
Studio 2012, and it's able to build and run, does this mean that it
will build and run for users with VS2012, VS2010, and VS2008?
Not really, due to the .vcxproj / .vcproj conflict stated above.
For example, I currently have a set of .vcxproj files and a solution designed for VS2010. I use VS2012 as my IDE, so when I open the VS2010 solution in VS2012, I choose to NOT upgrade it and simply open it as is. VS2012 and beyond should be backwards compatible back to VS2010 as far as project files go.
For maximum compatibility in development environments, my recommendation would be use VS2010's solution as the baseline, targeting v100. Developers can use any version newer than that and it should all work together gracefully.
I have installed VS2012 Ultimate on a fresh PC. I tried adding the Crystal Reports file in my project but there is no crystal report .crt Item avaliable into Add New Item menu of the VS2012
Is there a version for VS2012? or do I have to install an extra setup file for crystal reports which is redundant since I already have VS2012 installed.
Here it is! - SP 25 works on Visual Studio 2019, SP 21 on Visual Studio 2017
SAP released SAP Crystal Reports, developer version for Microsoft Visual Studio
You can get it here (click "Installation package for Visual Studio IDE")
To integrate “SAP Crystal Reports, developer version for Microsoft Visual Studio” you must run the Install Executable. Running the MSI will not fully integrate Crystal Reports into VS. MSI files by definition are for runtime distribution only.
New In SP25 Release
Visual Studio 2019, Addressed incidents, Win10 1809, Security update
This post is right from SAP on Sep 20, 2012.
In short, they are still working on a release of Crystal Reports that will support VS2012 (including support for Windows 8) It will come in the form of a service pack release that updates the version currently supporting VS2010. At that time they will drop 2010/2012 from the name and simply call it Crystal Reports Developer.
If you want to download that version you can find it here.
Further, service packs etc. when released can be found here.
I would also add that I am currently using Visual Studio 2012. As long as you don't edit existing reports they continue to compile and work fine. Even on Windows 8. When I need to modify a report I can still open the project with VS2010, do my work, save my changes, and then switch back to 2012. It's a little bit of a pain but the ability for VS2010 and VS2012 to co-exist is nice in this regard. I'm also using TFS2012 and so far it hasn't had a problem with me modifying files in 2010 on a "2012" solution.
There is also someone who managed to modify CR for VS.NET 2010 to install on 2012, using MS ORCA in this thread: http://scn.sap.com/thread/3235515 . I couldn't get it to work myself, though.
"SP25 work on Visual Studio 2019" is an exaggeration. It is extremely unreliable and should be avoided at all costs. I currently have to maintain a second development environment with V2015 for report development.
I have installed full version licensed Visual Studio 2010 Professional, .Net 4.0 on my system. Now I am trying to install Active Reports 6 on it and facing the error "no compatible version of visual studio net found on system". My Active Reports build is 6.0.1.1797.0.
So, do I need to install framework 3.5 before installing? I have not installed Service Pack for visual Studio for now.
Thanks.
Active reports 6.0.1797.0 does not support Visual Studio 2010. Active reorts 6.1.2577 or later supports Visual Studio 2010. And any how, Express edition of visual studio does not support active reports.
So my solution, enhances...I installed the later versions...but unfortunately I am getting some errors in my application because of Active reports version change as my application was made in previous version of Active Reports. So, what I did is, installed the latest version, uninstalled it and again installed 6.0.1797.0 version, and it was installed successfully and my application was also working fine.
#rapsalands...You are correct in understanding that support for Visual Studio 2010 started only after build 6.1.2577.0 was released. Also express edition of Visual Studio is not supported. The first thing to note here is that whenever you install/uninstall ActiveReports 6 from your machine, there should be no running instance of Visual Studio as it affects proper integration of ActiveReports with itself.
Also the errors which you were getting are more likely appearing because of the incorrect references in your project. Whenever you open an existing project after upgrading ActiveReports build, you should remove all the ActiveReports references from the project, re-add them (making sure they point to the version currently installed) and finally rebuild your project.
I think you can also check the blogs for ActiveReports as you might find some useful information about different topics there.
I'm trying to install Moles (without Pex, since Pex is only available for free for non-commercial purposes) using the downloads found here (that's the x86 version, I've tried the x64 version as well).
The installer(s) run without errors, and inform me that Moles have been installed correctly. But when I start Visual Studio, I see no trace that this add-in should be installed. It doesn't show up among the installed extensions in Extension manager, and I can't add any Moles items into my projects.
Is there some installation step that I'm missing here?
To check if moles is installed go to:
--> Help --> About Microsoft Visual Studio
If it is in the list, it is installed. To use moles you have to create a test project and go to the reference in the test project you want to mole. Right click and Add Moles Assembly.
I see some posts of VS.NET SP1 with moles. So installing is possible.