I have my my setup project in (Visual Studio 2015: Community Edition) ready to be built and create my program installer. But, obviously the program will not work on other computers without the appropriate redistributable package installed on the clients computer.
So, I need to set that up in my project but I do not know how. I read in a post on another site that it is located in:
Project>>Setup Properties>>Prerequisites
But, all I just see are selectables for ".net framework" related things. Also, I read that merge modules are not good to use due to servicing issues.
If you have any insight into whether I am needing to download an extension for the correct prerequisite to appear, use merge modules, or something else it will be greatly appreciated!
Related
I want to create a SQL Database project and manage my database as code (e.g. DevOps), but I am not sure what tools I can use for free within an enterprise.
How do I install and use SSDT without requiring paid licensing and violating any EULAs, such as Visual Studio Community Edition's?
In enterprise organizations (meaning those with >250 PCs or > $1M in annual revenue) no use is permitted...
This Microsoft article states that I can use SSDT in VS2019, but it doesn't tell me how to install it and not violate EULA.
This SSDT Download page is unhelpful and does not provide anything about licensing.
Also, I considered other tools, but looking at docs they don't seem comparable to SSDT:
Azure Data Studio - (cross-platform) new preview extension SQL Database Project supports DACPAC. I wasn't happy with my previous trial of this product. Maybe I'll give it another try in a couple years.
VS Code: Does not appear to have any extensions that directly support a SQL Database Project and/or DACPAC
Thanks to all of the answers, but I think I found what I was looking for in the Visual Studio Community Edition license: https://visualstudio.microsoft.com/license-terms/mlt031819/
My understanding, is that this allows me to use Visual Studio 2019 Community Edition for SSDT tools in an enterprise setting.
You don't have to install SSDT in Visual Studio 2019, even in Community. Go to new project and type SQL and hit return. It will say something like "SQL Server Database Project". Guess what? That's SSDT. In older versions, it was a separate install. It is now part of the core Visual Studio. And you upgrade it, if there are any, the same way you do anything else.
Already installed Visual Studio? No problem. Reopen the installer and install the data tools. This can be part of the payloads they have (I forget which one, but it has to do with data) or you can click on the tab that allows you to install individual components and search for the SQL tools. Once installed, they are there.
I don't belie you can install using the SSDT separate installer anymore, just like you know handle all of the .NET Core installs in Visual Studio, rather than separate. Kathleen Dollard outlined this in one of her posts last year (not SSDT, but .NET Core, etc.), so it has been a bit more than a year these things got folded into the installer. Core may still allow download and install? Not sure. But SSDT is the SQL project in 2019.
I guess that you can use SSDT anywhere where you can use Visual Studio. In other words, if you can use Visual Studio - you can use SSDT as well. Now the question - can you use Visual Studio? Here is the link to pdf document describing their Licensing policy.
Here is the snapshot from there:
Visual Studio Community 2019 is a free,
full-featured IDE for any developer building non-enterprise apps
across any platform or device. It includes all the capabilities needed
to create compelling non-enterprise applications, including powerful
productivity features, mobile development tools for Windows, iOS and
Android, and access to thousands of extensions.
Who can use the Software
Rights to use Visual Studio Community depend on the customer
segment and usage scenarios as explained below.
Individual developers
Any individual developer can use Visual Studio Community to create their
own free or paid apps. In addition, any number of users may use the
software to develop and test device drivers for the Windows operating
system.
Organizations
• An unlimited number of users within an
organization can use Visual Studio Community for the following
scenarios: in a classroom learning environment, for academic research,
or for contributing to open source projects.
• Any number of users may use the software to develop and test device drivers for the Windows operating system.
•For all other usage scenarios: In non-enterprise
organizations up to 5 users can use Visual Studio Community. In
enterprise organizations (meaning those with >250 PCs or > $1M in
annual revenue) no use is permitted for employees as well as
contractors beyond the open source, academic research and classroom
learning environment scenarios described above
VS Code - is the text/development editor that have nothing for SSDT, you can work with SSDT projects like with files and folders. You won't be able to build/validate/deploy the project.
ADS - the text/development editor that was created on the base of VS Code to work with SQL Server databases. You can do some basic stuff for SSDT projects (build, deploy, compare, add/remove objects), but is not so powerful as Studio SSDT version yet.
Technically you need only MSBuild and SQLPackage to build and deploy dacpacs, so if these tools can be used for free in Enterprise, then you can technically do everything without the Studio, just with ADS or in hard-core way - with any editor if your knowledge is deep enough to generate proper sqlproj (xml) file.
From Prerequisites on the setup property pages, I selected the option to Download prerequisites from the component vendor's web site
There is no Windows Installer 4.5 in the prerequisites to install option..
because every im installing my setup using the sqlexpr_x64_ENU.exe in custom actions to install, run the setup after the extracting sqlserver it pops up the window says
There is a problem with this Windows Installer package. Aprogram run as part of the setup did not finnish as expected. Contact your support personnel or package vendor
im using VS2017 on windows 10
Exclude MSI Engine: You should not include Windows Installer 4.5 with any package these days. This runtime is from back in the day of Windows Vista - we are long since on version 5. Windows Installer should be deployed only via Windows Update as of today - in my opinion. Leave the runtime out of your setup.
No Concurrency: You can not run an MSI setup from within another MSI setup via a custom action. This is due to technical restrictions. There is a mutex set when an MSI runs its actual installation sequence, and triggering another installation sequence from within it will fail. A similar answer on the topic.
Setup.exe Launcher: What you need is to install your pre-requisites via a setup.exe launcher instead. This runs installations in serial, not in parallel. Which version of SQL Server are you installing? I see only a couple of versions available in the Visual Studio Installer Project launcher.
Other tools have features to allow you to install a setup.exe with embedded packages of various kinds in sequence. I have explained a myriad of times how to do this in previous answers. Here are just a few that I found quickly:
SQL Server named instance with Visual Studio 2017 Installer project (basically exactly the same issue - I suggest WiX the open source, free alternative)
Custom installer for application in Visual Studio 2017 (I suggest WiX and several commercial tools that are easier to use - maybe try to read this one)
Cannot call command.exe(SQL Server Setup.exe) while calling C# CA with parameters
How to create a MSI file which simply copies a directory to Program Files? (tools list)
Combine exe and msi file in one installer
Visual Studio 2017 Installer Project - include VC++ 2015 Redistributable
The general situation:
The problem is not Windows Installer 4.5, it's the fact that you are trying to do a recursive MSI install (the SQL one from inside yours) which is not allowed and will fail.
The MSI 4.5 engine is pretty much obsolete, about 10 years old, and anyway it's not the issue, and it's not clear why you believe it is. But it IS in the Prerequisite list on my VS 2017 setup project prerequisites - see 3 - even though you almost certainly don't need it.
There are some SQL Express options available in the Prerequisites of the VS setup project - right click the project in solution explorer and choose Properties, then Prerequisites.
Is there any workaround to get Rational ClearCase running in VS2015 RC? It looks like no plugin is available yet. Can I somehow use the plugin from VS2013?
The solution proposed by user5337760 worked perfectly for me.
In ccvsisearchtoolwin_VS2013.reg and reg_VS2013.bat, globally change all the 12.0 instances to 14.0. (I don't use the Remote Client, so these 2 files are the only ones I needed.)
Check the environment variables in reg_VS2013.bat to be sure they match your setup.
Run reg_VS2013.bat.
According to http://www.almtoolbox.com/blog/installing-microsoft-visual-studio-2015-integration-with-clearcase, Microsoft Visual Studio 2015 is integrated with ClearCase as of release 8.0.1.10.
The same site has also a non-official Visual Studio integration with ClearCase 9.
First, apply the the latest fix pack for your ClearCase Client version. Support for VS2015 may already be included.
If not, start with the approach given by IBM for VS2013 http://www-01.ibm.com/support/docview.wss?uid=swg24036865
Before executing the scripts though, be sure to replace all references to VS2013 ("12.0") with ("14.0") in the batch and registry scripts provided.
Also, since you're probably using a 64-bit system, be sure to specify "Program Files (x86)" where appropriate.
Can I somehow use the plugin from VS2013?
You can try, but it isn't supported officially.
I don't know of a compatible ClearCase plugin for now.
Official support for Microsoft Visual Studio 2015 was introduced in ClearCase 8.0.1.10 as noted in the "What's New" page.
Currently I have a 60MB assembly which needs a 100 MB of prerequisites to be installed. For example Visual C++ 2005 for Crystal reports, Visual studio Tools for Office 2010 , Visual C++ 2010 redistributable and finally .NET framework.
Is there a way through which I don't need to deploy these prerequisites, inturn saving time and space?
May be there is a way to extract and include only those parts within these prerequisites which are needed.
With certain exceptions, MSFT generally doesn't support this. Using high level languages, frameworks, APIs and such come with a cost. You don't get all that for free... it has to be deployed.
That said, you can make choices to make it more manageable. You can target .NET 3.0+ and eliminate Windows XP and the .NET Framework suddenly doesn't need to be distributed.
You can also choose not to redistribute them and instead have your installer simply error out and tell the user to go install it.
It's one of those "it is what it is" problems.
I believe there are merge modules for CR for VC++ 2005 that you can include in your MSI build, but that redist isn't huge anyway. I also believe you don't need to install Visual Studio Tools for Office 2010 either, you need the Visual Studio Tools for Office 2010 Runtime Redistributable, not the same thing. The VC++ 2010 redist isn't that huge either, but again there are merge modules you could include in your MSI. I also suspect that you don't need the entire NET Framework, just the Client Profile redist.
My WPF project requires Adobe Reader. Apparently when I try and run the installer, it says I need to have it installed before I run the installer for my project.
I was wondering how do I package it along with InstallShield so that the user can select the option to have Adobe Reader install before installing the main project instead of having to search for it online themselves to install it?
Is this even possible? I tried to search online but I'm having hard time finding results.
Right now I'm using InstallShield Limited Edition for Visual Studio 2012.
EDIT:
Here's one screenshot where I picked the settings:
EDIT #2: I found a redistributable .exe of Adobe Reader 9.1. Now, I am wondering how I can tie that into InstallShield?