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.
Related
First of all, this issue has nothing to do with the installation of SSDT. I have the lastest version installed, at the time of writting this.
My issue is that the SSIS package was written some time ago using, I think either VS2005 or VS2008 as I was using Windows 7 with the lastest SSDT package fro the time, and I now need to open it up to view the workings.
I am now using VS2019 on Windows 10, again with the latest SSDT package, and studio refuses to open the project.
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- Contessa.SQL.SSIS, "G:\Work Stuff\Solution\40 SQL SSIS\TestSolution.SQL.SSIS\TestSolution.SQL.SSIS\TestSolution.SQL.SSIS.dtproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- Contessa, "G:\Work Stuff\Solution\TestSolution.sln"
I have found the answer and it had nothing to do with the SSDT installed.
After finding this article.
visual-studio-2019-open-solution-file-incompatible
It explains the need to make sure that the SSIS Extension is enables. In my case it needed to be installed.
This occurred because I had installed various versions of SSDT which caused Visual Studio to need me to reinstall.
I have encountered the following error:
The 'XamarinShellPackage' package did not load correctly.
It happens when i start Visual Studio 2015 Community Update 3 Or Visual studio 15 Preview 4.
I even reinstalled windows 10 and it doesn't help.
As asked, pasting VS info:
Microsoft Visual Studio Enterprise 15 Preview 4
Version 15.0.25618.0 PREVIEW
Microsoft .NET Framework
Version 4.6.01586
Installed Version: Enterprise
Visual Basic 15 Preview 4 00369-50000-00000-AA551
Visual C# 15 Preview 4 00369-50000-00000-AA551
ASP.NET and Web Tools 2016 15.0.20802.0
Common Azure Tools 1.8
JavaScript Language Service 2.0
JavaScript Project System 2.0
JavaScript UWP Project System 2.0
NuGet Package Manager 3.5.0
Parallel Debugger 1.0
SQL Server Data Tools 15.1.60805.0
TypeScript 2.0.1.0
Visual Studio Tools for Apache Cordova Update 10
Visual Studio Tools for Universal Windows Apps 15.0.25618.00
Xamarin 4.1.1.8 (60e5c00)
Xamarin.Android 6.1.1.1 (7db2aac)
Xamarin.iOS 9.8.1.4 (3cf8aae)
The tooling in the version information here is a little out of date. The solution in this case was to perform a thorough uninstall of Xamarin in Windows and reinstall using the latest available Stable release. I linked #Dorad to the direct download, but you can find this by signing into Xamarin.com, navigating to the Downloads page and selecting the download from the relevant drop-down list for your OS / desired Xamarin platform:
Another quick thing people can try that worked for me was deleting the .vs folder from the root of the solution folder. Make sure VS is closed when you do it.
There is a potential workaround you may want to try while we finish up a fix for this.
Please, close all open VS instance and copy this file (note you may need to adjust the path to your specific VS instance):
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\net461\lib\netstandard.dll"
to the Xamarin extension folder:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\Xamarin.VisualStudio
And then open VS and check if you can still repro.
thanks,
I had the same problem after the latest VS2017 update..I resolved uninstalling an extension (Visual Studio Bitbucket plugin) which - apparently - was in conflict with XamarinShellPackage. Removing the extension and restarting VS did the trick for me.
Can we use MSBuild without Visual Studio 2012?
Currently, we have a build server where we are compiling and creating deployment copy of one of our projects, it has Visual Studio Professional Edition installed. We are setting up a new build server now. Do we really need Visual Studio 2012 on the new build server?
If yes, then how? I googled it but I couldn't find an answer.
We have spent a lot of time trying to get our Build Servers to work without Visual Studio.
We do not use TFS for builds and therefore I am not sure the license exemption above applies to us. Also not having Visual Studio installed helps you really understand how your software is building and get references correct.
We have seen many examples of solutions with projects that contains references for the same piece of software with some in nuget packages shipped with the solution and others that are pointing to locations in the "program files" path which are not present on machines without Visual Studio installed. Once you attempt to build software without VS installed you can really see how "self-contained" your applications are.
Before I start listing the things you typically need to install, let me just point out that MS Build is now no longer considered part of the .NET framework but is shipped with Visual Studio but can also be installed separately. See this blog post for more: http://blogs.msdn.com/b/visualstudio/archive/2013/07/24/msbuild-is-now-part-of-visual-studio.aspx
The following software needs to be installed for most builds, there may be others for example if you are creating portable class libraries.
Microsoft Build Tools 2013
Web Deploy 3.5 (for packaging applications)
Microsoft .NET Framework 4.5.1 Developer Pack
Microsoft .NET Framework 4.5.2 Developer Pack
Windows Software Development Kit (SDK) for Windows 8 (You can use the SDK to build applications that target these operating systems: Windows 8, Windows 7, Windows Vista, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008)
The following directories need to be copied:
Reference Assemblies (need to be copied from a machine running Visual Studio from/to directory C:\Program Files (x86)\Reference Assemblies)
Public Assemblies (need to be copied from a machine running Visual Studio from/to directory C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PublicAssemblies
We also use Wix and therefore we install the following:
WIX Toolset 3.8
I have a similar set for testing however that was not part of the question so I will leave that off!
Hope this helps someone.
Update: 3rd March 2017
Microsoft recently responded to a long standing user voice request "Support .NET Builds without requiring Visual Studio on the server" for the requirement for Visual Studio to be installed on a build server to be removed.
From the description on the download page "These Build Tools allow you to build native and managed MSBuild-based applications without requiring the Visual Studio IDE." Not tested yet but after RTM I will look at this and provide a further update here.
There is a blog post that promises these build tools install all pre-requisites and can be used to build MS Build based applications.
No, you don't need Visual Studio on your build box. If I recall correctly, msbuild is installed as part of the .NET framework - it certainly used to be.
Depending on what you're building, you may find that there are some things which are easier to get working if you do install Visual Studio though - things like portable class library profiles. While there are usually non-VS installers available, I've found it simpler to install an Express edition of Visual Studio just to get the bundled build targets.
Remember: The easiest way to build your visual studio solutions is to install Visual Studio on the build server. Even Visual Studio Express is often enough.
That said, you can make it work without it. But it it sometimes a lot of work to figure out. You'll need to install the right Windows / .NET Platform SDK. You can install multiple of these SDKs side by side. Now, when you depend, for example, on ASP.NET MVC 5 or Entity Framework 6, you might need to install further SDKs to get your application to compile. The downloads for these all assume that you also have Visual Studio installed, but many of their payloads can also be installed separately. It can become quite a hassle.
Personally I've grown tired of trying to figure out which parts of which installers enable what. But that is also driven by the fact that Microsoft allows you to install Visual Studio on a build server (TFS) with the same license as your development machine as long as you are an MSDN subscriber. Check the Visual Studio License Whitepaper for more details.
Using Visual Studio on the Build Server
If you have one or more licensed users of Visual Studio Ultimate with MSDN, Visual Studio Premium with MSDN, or Visual
Studio Professional with MSDN, then you may also install the Visual Studio software as part of Team Foundation Server
2013 Build Services. This way, you do not need to purchase a Visual Studio license to cover the running of Visual Studio on
the build server for each person whose actions initiate a build.
If you, like me, would prefer this to change in the future, I suggest you make sure you're heard by submitting your request or voting for an existing one over at the Visual Studio User Voice.
Here's just a quick take on this.
Your build machine should decouple development tools as much as is possible. With that said, and as already stated by others here, MSBuild can be run independently of Visual Studio, and it should!
If your build requires Visual Studio to run then there is a very good chance that you have a solution or project architecture problem that ought to be resolved.
Visual Studio doesn't need to be installed. MSBuild is part of the .net SDK.
Other .net dependencies will need to be installed though, if you are using them. MSTest, or anything that is part of Team foundation will require Visual Studio installed.
I believe you only need MSBuild ( that is part of the .NET framework you're targeting ) .
Make sure you install the proper .NET distribution
the following is a good place for build servers it have the developer tooling.
The .NET Framework 4.5.1 Developer Pack installs the multi-targeting pack for .NET Framework 4.5.1. Developers can build applications targeting the .NET Framework 4.5.1 using either Visual Studio 2012 or third party IDEs. You need to download the web installer instead of this package if you intend to redistribute .NET Framework 4.5.1.
http://www.microsoft.com/en-us/download/details.aspx?id=40772
Best of luck.
C++ :
There is a "Build Tools" that contains MSBuild, Visual studio is not required.
From the official doc :
These tools allow you to build C++ libraries and applications
targeting Windows desktop. They are the same tools that you find in
Visual Studio 2015 in a scriptable standalone installer. Now you only
need to download the tools you need to build C++ projects.
Managed :
The same applied : Build Tool Managed
I have a couple of Crystal Reports that were developed in Visual Studio 2005, but I am now using Visual Studio 2010. The application is still referencing the 10.2.3600.0 DLLs and I have no desire to update those references. We are phasing away from Crystal and don't want to deal with migrating to a newer version.
I did install the latest version and support pack of "SAP Crystal Reports, developer version for Microsoft Visual Studio" from http://scn.sap.com/docs/DOC-7824 and am able to open and edit the reports as required.
However, when I try to run the application, I get the following error:
{"Could not load file or assembly 'CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.":"CrystalDecisions.ReportAppServer.CommLayer, Version=10.2.3600.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"}
I did some searching around and it seems I need the 2005 DLLs registered in the GAC? Does this sound correct? Will it not work with the redistributables installed by v13? The referenced 2005 DLLs are all in another folder and properly referenced by my project so I would think the application should work with those.
What is the minimum I need to install in order to be able to work with the reports in Visual Studio 2010, and to actually run these old 2005 reports in the application?
Modifying the reports requires the Visual Studio integration Install Executable to be run. The latest version can be found at http://scn.sap.com/docs/DOC-7824.
Displaying or printing the reports within the application requires the correct runtime distribution files. I cannot find an "official" source for the 2005 redistributables, but there seem to be a number of sites that offer it for download. Just search for it.
You have to install CRforVS_redist_install_32bit for 32 bit machine and CRforVS_redist_install_86bit for 64 bit machine. these will register all necessary DLLs.
below is the link of the same.
http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_redist_install_32bit_13_0.zip
http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_redist_install_64bit_13_0.zip
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.