Is it possible to download the merge modules for VC++ 2008 (CRT) without having Visual Studio?
I have an old Visual Studio 6 project and an old Install Shield Installer. I am using some third-party dlls that are dependent on MSVCR90.DLL among others (installing the dll in my program folder doesn't work though maybe I am missing some others.)
What does make it work is manually installing the Microsoft Visual C++ 2008 Redistributable SP1 (vcredist_x86.exe) on the client machine.
I read here that the preferred way to distribute these pieces is through the associated merge modules. But I can't find a way to get the merge modules if I don't already have VS 2008 installed!
By the way, the third-party dlls do come with their own OEM installer but it is 80 MB and I'm hoping to avoid having to distribute that as well. The vcredist_x86.exe is only 4 MB.
Related
Until now I only used Visual Studio for Business Intelligence development and now I have to do something in C# that uses Google Drive API which has to be installed through NuGet Package Manager. Unfortunately I don't see this particular package in Visual Studio Extensions and Update manager. I though it may be related to lack of Tools > NuGet Package Manager > Package Manager Console option in my VS, so I wanted to install package manager. I downloaded .vsix file, but when I try to install, it fails with message This extension is not installable on any current installed products. I got VS 2015, 2013 and 2010 installed.
So if I'm not able to install package manager, there is at least any way to install google drive api without involving NuGet?
Drive api package name: Google.Apis.Drive.v3
EDIT: I did reset all Visual Studio settings since it was set for Business Intelligence development, but this didn't help as well.
Please make sure your Visual Studio 2015 has installed the latest update. The latest version for Visual Studio 2015 should be version 14.0.25431.01.
If your Visual Studio 2015 is the latest version, please try repair your Visual Studio 2015 to check whether there has any installation issue.
And you also can install nuget packages without NuGet Package Manager. Please download the NuGet package and unzip it to local folder, which will list all content of this package. Then add the dlls in the unzipped folder into your project through Add Reference.
You do realize that SSDT and BIDS are for use with project types that are specific to SQL Server business intelligence. Business Intelligence Development Studio is the primary environment that you will use to develop business solutions that include Analysis Services, Integration Services, and Reporting Services projects.
To my knowledge you are not going to be able to install NuGet on it or use it to develop an actually C# application.
I am going to take a wild guess here and say you are trying to use google drive with a Script task. You can do this I did it a number of years ago. The set up is a bit weird. Your going to have to create a normal C# application in NORMAL visual studio with Nuget and it will install all of the Dlls for you at that time.
Now that you have all of the dlls. You are going to have to dump them in GAC and the folders that SSIS needs
C:\Program Files (x86)\Microsoft SQL Server\100\DTS\PipelineComponents
The 100 part changes depending upon which version of Sql server you are using
2005 = 90
2008 = 100
2014 = 110 (I think I cant remember)
Once the dlls are in the correct folders you should then be able to use it in a scripting task.
Note: I am not 100% sure any of this will even work anymore. When I did it the client library still supported .net 3.5. Now you need to be able to use .Net 4.5 I am not sure if the newer version of Sql server will be able to handle the higher level of .net dll or if they all require 3.5.
Checked with a coworker his guess is that Sql server 12+ should support .Net 4.5 dlls.
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
My understanding is that the VC++ redists are essentially updates to some core Windows files, and that over time MS "catches up" by incorporating past versions into new versions/updates to Windows. For instance I'd probably expect anything built with VC++ 2005 wouldn't need me to install the redist on target PCs these days.
Can anyone provide definitive reference for which versions of Windows include which VC++ redist versions?
Also, is the redist approach something MS still employ in the newest versions of VC++ e.g. 2012 and later?
None of the files distributed with modern versions of Visual Studio are updates to files that ship with Windows.
Windows does ship with a C runtime, which is used internally and (for reasons of backwards compatibility) by applications built with Visual Studio 6 or earlier versions. Later versions of Visual Studio each have their own runtime, none of which are shipped with Windows.
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
On a Build machine, I have both VS 2010 and VS 2012 installed. (We are nearly finished migrating from VS 2010 to 2012 and have just migrated to 2012, the build machine is also on TFS 2012.) I seem to need this for features like static code analysis.
When running the build I now encounter errors: the FXCop seems to be very good at selecting the wrong .exe version whereas different (rule) .dlls are in the project files. (Meaning: I have v10 files in the project file, but v11 exe is taken or vice versa.)
On top of that (after uninstalling VS2010) I ran into problems with some legacy C++ projects that require VS 2010 (requiring some MSBuild v100 rather than v110).
In the end I uninstalled VS2012 and probably will revert once we have completely moved to VS 2012 (some members of the team are still happy if projects are compatible with VS 2010). Actually, things are working now with only VS2010 installed (though I had to revert some changes).
Is there a better way, is it e. g. possible to determine which FXCop you are using for static code analysis from within the build when having several VS versions installed?
Well, this is kind of a mess. I ended up selectively choosing what to put on our build server, rather than trying to sit VS2010 and 2012 side-by-side (had a lot of problems with 2012 there, so ended up having to rollback, too).
We ended up adding -
.NET 4.5 SDK
.NET 4.5 multi-targeting pack
.NET 4.5 Framework
Copy the files in C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PublicAssemblies on a machine with VS2012 installed to the same path on the build machine
Copy the files in C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0 on a machine with VS2012 installed to the same path on the build machine
I think that took care of everything, but it was a lot of trial-and-error to get all of the assemblies there. Good luck!