I have completed a WPF application in Visual Studio 2010 and SQL Server 2008 Express. I have also used Crystal Reports in my project. Now I need to deploy the application on client's systems. I assume that I will have to install the following pre-requisites first.
.Net Framework 4.0
MS SQL Server 2008 express (which may require .Net 2.0)
CR Runtime for .Net 4.0
Report Viewer
IS there a way so that everything installs on its own? I have tried selecting all the above as ** prerequisites**, but that gives me an error that CR Runtime msi not found. Can I also include all the files within my software in the bin folder?
Please give me suggestions.
you can download CRRuntime_32bit_13_0_1.msi from SAP website (google it) and place it in this location:
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\Crystal Reports
for .NET Framework 4.0\
Related
How do I open a DTSX file for editing using Visual Studio 2019?
I have generated a DTSX file by using the Import Data wizard found in SQL Server Management Studio, using the same process outlined in this question. The answer to that question explains how to edit a .dtsx file, but it does not appear to be correct anymore. I am using Visual Studio 2019. The answer says I need to use this link to download SQL Server Data Tools for Visual Studio:
Download and install SQL Server Data Tools (SSDT) for Visual Studio
But at that link, it says:
Changes in SSDT for Visual Studio 2019
With Visual Studio 2019, the required functionality to enable Analysis Services,
Integration Services, and Reporting Services projects has moved into the
respective Visual Studio extensions. The core SSDT functionality to
create Database Projects has remained integral to Visual Studio (you
need to select the Data storage, and processing workload during
install). There's no more standalone SSDT installation required.
If you already have a license to Visual Studio 2019:
For SQL Database Projects, install the Data storage and Processing
workload for Visual Studio
For Analysis Services, Integration Services
or Reporting Services projects, install the appropriate extension(s)
from the marketplace
I believe I need Integration Services, but it doesn't have a link to the appropriate extension in the marketplace. Through various googling paths1, everything keeps pointing back to the SQL Server Integration Services Projects extension. I have installed this extension2, but I am still unable to open DSTX files.
Here's how I'm attempting to do it: In Visual Studio, am going to File|Open Project. Then I browse to the folder with the .dtsx file in it, change the filter to *.* (because .dtsx isn't in the list of supported project extensions), choose the file, and click Open. I get this message box:
So, my question again: How do I open a DSTX file from Visual Studio 2019?
See below for detailed versions and installed extensions.
1 For example, see Lesson 1-1: Create a new Integration Services project, where they create a DSTX project. The lesson's Prerequistes instructs you to install the SQL Server Data Tools from Download SQL Server Data Tools, which is the same link from above.
2 I note that version 3.1 of the extension is currently labeled a Preview and that release notes for this version includes the text, "This is the second preview release. We do not recommend using it for production." But I do not see where I am able to download an earlier version of this extension, either from the marketplace website or from in Visual Studio. I would try the latest production release if I could find it, but it doesn't seem to be available.
I also see there are two notes about issues with this preview release. Neither seem relevant to my situation. The first is a regression in VS 16.2 where they recommend upgrading to 16.2.3. I am already on 16.2.4. The second is an issue where the extension and/or Visual Studio Tools for Applications 2019 might be deleted during a VS instance upgrade. I have not done any upgrades to VS since installing this extension.
Installed Software
Visual Studio 2019, version 16.2.4
SQL Server Management Studio, version 17.9.1.
In Visual Studio, when I go to Help|About Microsoft Visual Studio, I also see the following listed in Installed Products (this list is not complete; it includes only the items that seemed relevant):
SQL Server Data Tools 16.0.61906.28070
SQL Server Integration Services 15.0.1301.433
In Visual Studio, when I go to Extensions|Manage Extensions, I see SQL Server Integration Services Projects in the list of installed extensions.
The error message indicates you are trying to open a project/solution. DTSX is a package.
You first need to open the .sln or .proj file. Within the project (solution explorer) you can open the dtsx. Do not try to open the dtsx file from the source control explorer as that does not open with the project references.
In summary, open the solution/project, then open the package from the solution explorer.
To edit and create integration services packages (.dtsx) is necessary to install SQL Server Integration Services Projects.
After installation Visual Studio 2019 can create or edit integration packages either independently (open file) or in Integration Services Project. It is also possible to open packages on SQL server even when SSMS fails with message:
Connecting to the Integration Services service on the computer "xxxx" failed with the following error: "Access is denied."
You will have to install SSMS, SSAS from VS Extensions> (In VS Menu, click "Extensions" and then "Manage Extensions
I'm fairly new to Visual Studio and SSIS and was wondering if someone could just clear up for me how Visual Studio SSIS Projects and Visual Studio in general handle Add-In Extension and Package Deployment.
The Scenario: I am currently developing and creating a Visual Studio SSIS Package on my local machine.I need to use an extension from the Tools > Extensions and Updates which just links me to a webpage.I need to install this and use it to make a package which I will deploy to the Integration Services Catalog on a SQL Server 2014 that does not have Visual Studio installed. When I deploy this project as a package will the things the extension did be baked into the package or is it like references where I will need to install the extension on the server that will be running the package via SQL Agent Job. Thanks, any help is appreciated.
When you deploy a package to the catalog, all libraries/extensions (eg.azure connection etc) are deployed along-with, so no special treatment is needed. But many a times you will need to ensure your frameworks( eg. .net 4.0 etc) exist for the extension to be executed on the integration services server you are deploying to.
In some cases you have to register the dlls using GACUtil, to the integration services server. Your custom tool installation instructions will specify that.
Previous versions of the Microsoft Report Viewer technology for Windows Forms had a runtime file you could install on a client PC to setup the Microsoft Report Viewer assemblies on the users machine. Does something like this exist for Report Viewer version 14.0 used by Visual Studio 2017? I can't seem to find anything available on the Internet.
Viewer 14 on VS 2017 is quite nice in that all you need is the nuget package and you have everything you need to run reports. It doesn't require an installation package to run on the target machines.
This makes web applications a lot easier to deploy as you don't have to install anything on the server short of the website itself. And for winforms you just need to include the dll files the nuget package added.
Has anyone managed to use vs2010 db build & deployment with teamcity without VS 2010 installed on build server?
I've registered the missing DLL's but it doesn't work and seems msdn suggest that we need vs installed on the build server.
Install the Microsoft Windows SDK v7.1 and any other requirements (example being ASP MVC 3 framework), etc. Make sure you have the correct versions of .NET installed as well. I am able to build and run unit tests, no issue without Visual Studio 2010 on a windows 2008 r2 64-bit server.
I'm developing a Windows Forms application using Visual Studio 2008 C# that uses an SQL Server Compact 3.5 database on the client. The client will most likely be 32 bit Windows XP or Windows Vista machines. I'm using a standard Windows Installer project that creates an MSI file and setup.exe to install the application on a client machine. I'm new to SQL Server Compact, so I haven't had to distribute a client database like this before now. When I run the setup.exe (on new Windows XP 32 bit with SP2 and Internet Explorer 7) it installs fine, but when I run the application I get this error:
Unable to load DLL 'sqlceme35.dll'. The specified module could not be found
I spent a few hours searching for this error already, but all I could find were issues relating to installing on 64 bit Windows and none relating to normal 32 bit that I'm using.
The install application copies the all the dependent files that it found into the specified install directory, including the System.Data.SqlServerCe.dll file (assembly version 3.5.1.0). The database file is in a directory called 'data' off the application directory, and the connection string for it is
<add name="Tickets.ieOutlet.Properties.Settings.TicketsLocalConnectionString" connectionString="Data Source=|DataDirectory|\data\TicketsLocal.sdf" providerName="Microsoft.SqlServerCe.Client.3.5" />
Some questions I have:
Should the application be able to find the DLL file if it's in the same directory, that is, local to the application, or do I need to install it in the GAC? (If so, can I use the Windows Installer to install a DLL file in the GAC?)
Is there anything else I need to distribute with the application in order to use a SQL Server Compact database?
There are other DLL files also, such as MS interop for exporting data to Excel on the client. Do these need to be installed in the GAC or will locating them in the application directory suffice?
You don't need it to be in the GAC for SQL Server Compact to run, and it will pick them up from the application directory. There are several ways to deploy an SQL Server Compact project. The two main ways are:
Deploying the SQL Server Compact redistributable installer with your project, but this way is painful and also can be unistalled by the end user, or upgraded by Windows updates and breaking your application.
Including the DLL files in your application folder. Depending on the features of SQL Server Compact you are using (replication or whatever), there is a handful of DLL files to deploy in your application folder.
If you have SQL Server Compact installed on your machine, they are most likely located at "C:\Program Files\Microsoft SQL Server Compact Edition\v3.5". They can be added to the project in Visual Studio and then set their project output type to "copy always". And the main reference to System.Data.SqlServerCe that you have in your project references should have copy local set to true.
sqlceca35.dll
sqlcecompact35.dll
sqlceer35en.dll
sqlceoledb35.dll
sqlceqp35.dll
sqlcese35.dll
If you have these all set, then in your installer project all you have to include is the project output of this project and you're good. In my opinion this is the only way to go. It is a simple deployment, of a couple of files and you are in control of what DLL versions your application uses.
I hope that helps.
I had a similar problem, a Visual Studio 2008 Windows application targeting 32-bit Windows XP and Windows Vista that used SQL Server Compact 3.5 SP1 - that then got this error when installed on 64-bit Windows 7:
Unable to load DLL 'sqlceme35.dll'. The specified module could not be found
I was embedding an MSI for SQL Server Compact into the installer for the application.
Following this rather confused discussion on MSDN revealed that I needed to use the 64-bit MSI for SQL Server Compact on 64-bit machines. D'oh! That is, from page Microsoft SQL Server Compact 3.5 Service Pack 1 and Synchronization Services for ADO.NET version 1.0 Service Pack 1 for Windows Desktop I needed SSCERuntime-ENU-x64.msi rather than SSCERuntime-ENU-x86.msi for 64-bit machines.
How to: Deploy a SQL Server Compact Edition Database with an Application should help, at least with your first two questions.
In general, I think you should not install anything in the GAC for a single application.
The following provide a solution to the problem and an explanation also.
Troubleshooting: Can’t load SQL Server Compact DLL
SqlCeException on application's first use of SQL Server Compact
Laxmi Narsimha Rao Oruganti 's blog
I hope this helps.