I got a copy of a Visual Studio 2005 project from a friend. The project referenced the DLLs Microsoft.ReportViewer.Common and Microsoft.ReportViewer.WinForms. On my machine I have Visual Studio 2012. I upgraded the project. The references to these DLLs are broken, understandably, because they are Windows locations, not in the VS project. So, I want to delete the references and re-create, but I cannot find the DLLs on my machine. Do they not get installed with Visual Studio 2012? Can I download them?
I got a copy of a Visual Studio 2005 project from a friend
Which explains the problem, the target .NET version of your project is 2.0. The ReportViewer included with VS2012 requires at least 3.5.
Fix it with Project + Properties, Application tab, Target Framework combobox. You'll then find the ReportViewer control back under the "Reporting" header in the toolbox.
These have been replaced by Report Server. Though if you'd copy them over from your VS2005 machine you should still be able to use them as binary references in your solution. You can download the binaries from the MSDN Download site.
Though there should be binaries for Visual Studio 2012 as well. I suspect they will get installed when you install the SQL Server Development tools, which include the SQL Server Reporting Server components.
You can try to use the Redistributable package for Visual Studio 2010.
Related
I installed VS 2022 Community and am trying to work on a project that was developed on VS 2008 Pro. VS is giving me this report:
How do I force VS to make whatever upgrades it needs in order to run this program? I can provide more info if needed.
MS in their wisdom, dropped support for the Setup & Deployment project, can't remember when exactly, then after a bit of an uproar re-instated it through the Visual Studio marketplace https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2017InstallerProjects
Since your project has a file .vddproj, it might be a Smart Device CAB project.
It is not supported by later versions of visual studio.
It is recommended that you open it with VS2008.
I would like to upgrade a project which uses RDLC to create reports. The solution uses Report Viewer 2010SP1.
I installed successfully the report viewer 2012 runtime, however the component does not appear in the add references windows of visual studio.
I also checked the NuGet-Packages and there I found a “Report Viewer”-package 11, but while installing this version, only the web-component but not the WinForms-component has been installed.
On the web I have seen some workarounds changing the registry, but is it really necessary to manually change the registry to have this done?
One way, probably not the best, is selecting the component directly with the "browse"-option.
In the “Add Reference” dialog, browse to “\Program Files (x86)\Microsoft Visual Studio 12.0\ReportViewer” and select there the component "Microsoft.ReportViewer.WinForms.dll"
I am adding this custom build task to my TFS 2010 build workflow, however when attempting to add it (ColinsALMCorner.CustomBuildTasks.dll) to the toolbox, I get error:
'Could not load file or assembly file 'ColinsALMCorner.CustomBuildTasks.dll' or one of its dependencies. Operation is not supported'.
I have added all of its dependencies to (I admit, this is probably redundant):
1) the same location where the ColinsALMCorner.CustomBuildTasks.dll resides, which is ..\BuildProcessTemplates\CustomActivities
2) in the Public Assemblies folder: Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies
And I have the build definition xaml file correctly importing the ColinsALMCorner.CustomBuildTasks namespace
Although the activity is set to target .Net 4.5, the documentation says that TFS 2010 / .Net 4.0 is supported, so I assume this should all be possible.
My Questions:
Is this possible with TFS 2010 / .Net 4.0 development environment? My concern is that the error message isn't telling the real story, for example maybe it is able to find it, however just not the right version of the assembly.
Is it likely that since the DLL targets .Net 4.5 I need to have all of its referenced dll's also be the 4.5 version? For example, it references Microsoft.TeamFoundation.VersionControl.Client however I only have the version 10.0.0.0 (which I assume the .Net 4.5 version of this might be 11.0.0.0)
Here was the solution, in short story format: I installed Visual Studio 2012. Result: I was able to add ColinsALMCorner.CustomBuildTasks to my workflow in Visual Studio 2010 without error. I assume this means there was a 2012 (v11.0.0.0) DLL or two required to use the activity in 2010, despite the fact that the requirements state:
Team Foundation Build 2010, 2012 or 2013
I have Visual Studio 2008, 2010, and WIX37.msi (WIX 3.7) installed on my machine.
However, I am unable to see WIX project type in Visual studio 2008/2010.
Do I need to install additional tool/plugin?
I have Visual Studio 2008 and Visual Studio 2010 installed on my machine and I installed WiX v3.7 RTM from Codeplex. Things work okay for me. There is a known issue in VS2008 that requires you to set an MSBuild property called RunWixToolsOutOfProc to true. This occurred because parts of WiX v3.7 were incorrectly built against the NETFX4.0 and VS2008 runs on NETFX2.0.
Install v3.0 of WiX Toolset, to make it work with Visual Studio 2008. You can get it here: http://wix.codeplex.com/releases/view/44406
I don't know why it's not documented on their site but apparently you can't install the latest version (3.10 at the moment) and make it work with VS2008.
I have already using Visual Studio 2010 for my project. Now I have to work with a Visual Basic 2006 legacy application. Can I install VB 2006 Enterprise Edition on my system?
Will this affect Visual Studio 2010?
Yes. Visual Studio 2010 and Visual Studio 6 will happily install side-by-side.
You can run multiple versions of Visual Studio on the same machine. I currently have VS2003, VS2005, VS2008 and VS2010 installed and am using all of them.
Where you may get into problems is with something like hooking up the older ones to TFS. This can be done, as I have VS2003 and VS2008 connected to TFS2010, but my VS2005 won't work as it whinges about the provider for some reason.
Another area to watch out for is IIS. As you have already installed VS2010, IIS may be defaulting to .Net 4.0 so if you start deploying .Net 2.0 apps then the websites may not work without some adjustment of things like app pools.
But if you are just using them independently of each other then you should be fine. If you're really paranoid, consider creating a VM and installing the old VS on it.
EDIT
I see from your edited post that you were talking about VB6. This also can be installed alongside any of the later versions of Visual Studio.