Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

Installing SQL Server support files in a Visual Studio 2008 Installer project

I have creating a .NET 3.5 application using Visual Stuido 2008.  I have made use of some features contained in the Microsoft.sqlserver.Smo Dll and want to ensure that my application will run on the target machine which may or may not have SQL Server 2008 installed (most likely it will not as these are client PCs).

I have created a Visual Studio 2008 Installation project which correctly lists the dependancies and installs the product correctly however I am not sure if just because the dependancy is listed in the installation project that the relelvant SQL server files are being installed.

Can anyone tell me if this is the case or if not how I can ensure that correct version of these files can be included in my setup project and installed along with the application.

In a similar way, my application uses .NET 3.5 and this is listed as a dependancy - will the installer install .NET 3.5 if required.

Sorry about the basis questions but I have always used InstallShield previously but no longer have a license so am trying to see if the in-built installer is sufficient for my requirements.
0
ChrisMDrew
Asked:
ChrisMDrew
1 Solution
 
Anthony PerkinsCommented:
>>which may or may not have SQL Server 2008 installed (most likely it will not as these are client PCs).<<
My understanding is that you will require a SQL Server license installed on any workstation that uses SMO.

You can download the distributable package here:
Microsoft SQL Server 2008 Feature Pack, August 2008
http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now