First off, I would like to say that I am very new to SharePoint and SSIS.
I'm trying to create an SSIS package in VS2010 that fetches rows from a remote SQL server and pushes it to a (also remote) Sharepoint Library.
So far, I managed to install and use the Business Intelligence to design the SSIS package on my VS2010 (thx to SQL server 2012 Standard 180-trial version).
I've also found out about the SharePoint List Adapters, but from what I've read, they are only usable in VS2008.
So, I want to find out if:
1. Is it possible to achieve this (SQL -> SSIS Package -> Upload/Push to Sharepoint)
2. Can I use SSIS SharePoint Tools in VS2010?
3. (Edit! Important) Is uploading Shared Documents in SharePoint Library achieved in the same way as publishing lists ?
I've found a (not so pleasing) answer to my #1 question, and it's from 2011, so I hope maybe some solution has come up since then: Sharepoint Development in Visual Studio 2010
Disclaimer: I don't know much about SSIS.
However, if SSIS lets you "run a custom piece of code for each SQL returned row", you could then use the SharePoint 2010 Client Object Model to create a SharePoint list item on a remote server for each SQL row.
This doesn't require SharePoint to be fully installed on the machine running the SSIS code. It only requires a couple of DLLs, Microsoft.SharePoint.Client.dll and Microsoft.SharePoint.Client.Runtime.dll. You can copy these from a SharePoint server (located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI) or, I believe, you can install the SharePoint Foundation 2010 Client Object Model Redistributable.
Related
I have a C# application that I want to install on my clients computers. It has a SQL Server database connection so that it can store data. I want to create a installer so than I can install the app on clients computer.
So far I tried Installer shield and advanced installer and I could not manage to pull it off.
NOTE: I can't install Microsoft SQL Server Management Studio on clients computer due to toughness.
NOTE: I'm using Visual Studio 2019 with Microsoft SQL Server Management Studio 2017 and .NET 4.5 and DevExpress and because I'm using DevExpress I have some reference files to copy to client directory.
If the users are not sharing their data with one another, you don't need SQL Server to begin with. There are other data storage options, ones that don't require an enterprise grade client-server database.
Your app can use a local database such as SQLite. You can use files - JSON or XML allow for easy parsing from C#.
I'm coding a C# Console Application that connects to a database and runs some queries where my database Engine is Microsoft SQL Server 2016 and I code in Visual Studio 2015. I have already installed and activated InstallShield Limited Edition on my visual studio and I'm able to make an installation(setup) file for my C# Console Application.
I don't want to to install Sql Server on my customer's PC and attach the database to that manually, instead I want to give everything in an installation file that includes .Net framework 4.5 and my database. The first part(.Net Framework) is done by InstallShield easily, but I don't know how to attach my database to the installation file.
Please explain how to do this and if any other version of InstallShield(Express, Professional or Premier) is needed let me know and explain the steps in that version.
Note that I want to give the installation file to the customer and make every feature of the app function well after he/she installs the program without needing to do anything manually.
Sql server 2016 cannot be installed automatically as it needs to be configured by the user, he must set the instance names, permissions and so on, which makes it unusable for your scenario.
What you need to use is Sql Server LocalDB, this is a subset of Sql Server Express for your concrete scenario, something which can be installed without the need of configuration and capable of attaching a database file also without user interaction.
You can find information about LocalDB here, as you see it can be downloaded as a .msi, in this way you can add this msi to your installshield project and chain it (more info on how to chain an installer here), it will not ask to the user about complex configurations, just a simple installer. To download the .msi you get the sql server express installer on your development machine and instruct it to download media and select the LocalDB package, that will give you the .msi.
Finally you will add the database file as part of your project files, then you only need to specify on the connection string the path to the file.
My team works on SQL database and asp.net in MS Visual Studio 2008. We have own server where our current repository is stored. We use Visual SourceSafe (VSS) 6.0 as the source control. Recently we decided the switch to the latest source control technologies such as Team Foundation Server or GIT.
I was able to create the GIT repository in our server and all team members were able to commit changes in the repository through Visual Studio 2013. But we like the nice GUI of Team foundation server and all of it features like source control explorer, check-out files for edit, managing users group and permission through TFS control panel, etc. It would be convenient for us if we have access to those features.
My question is can we use Visual Studio Team Services by maintaining our central repository in our own server? Or we have to host our source code in Visual Studio Team Services or any other third party repository? We do not want to store our code to any other places other than our own server and still want to use the TFS features.
Thank you for your help in advance.
YES, TFS allows you to store your repository on your own private server. Just install TFS on the server, then Visual Studio will connect to it for each client machine and you can use source control etc.
I want to create a setup file for an application that uses the following tools and technologies:
Microsoft visuals studio 2013
MSSQL server 2012
and I have used winforms and C# to write the program.
My questions are:
If I want to deliver the application to customer without giving out the source code what technique or tool should I use?
How do i supply the database? Should I detach it? How do I provide the database with my application?
I'm assuming you need to deploy the application you've created with Visual Studio rather than deploy Visual Studio itself. In which case you have a variety of options depending on its destination.
You can just copy your executable and required dependencies to a destination without distributing your source. However, there are several tools out there that will subsequently disassemble your assemblies to reveal the source.
The Visual Studio website has a list of options for deploying applications. If you want a tradional Next -> Next -> Finish type of installation, I would suggest using InstallShield Limited Edition.
For SQL deployment it would depend on the Edition you have used and whether the server already exists at the destination. Additionally, it will depend on whether you only need to deploy the schema or populate the database too.
You can distribute SQL Server Express with your application. SQL Server Management Studio will allow you to generate a "CREATE DATABASE" script (right-click database -> Script database as -> CREATE to -> File) from your existing database that can be executed as part of the installation. Alternatively, consider a backup/restore approach as detailed in this article.
I am currently writing a Windows application in C# that will add documents to a document library list. I am trying to reference Microsoft.Sharepoint, however I do not see the COM or .NET library inside visual studio 2005 add references lists. What dll do I need to reference and where can I find this?
Thanks,
Alex
To access a document library I would recommend going through the list web service which SharePoint exposes. From personal experience that is the easiest, most portable and upgradable way.
The documentation for ALL the web services and .NET libraries to do it as well can be download in Visual studio extensions for windows sharepoint services
to access the SharePoint library you have to include following assembly into your project: Microsoft.SharePoint.dll
You can find it on your SharePoint Server under the 12 hives folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI
There you can find some more assemblies you might need for more SharePoint functionality.
What kind of application do you have to develop???
If it is a client application that will be execute on machines that are not the Sharepoint target machine you'll have to call to SharePoint web services to do the operations.
If your application will be executed on server, SharePoint machine, you can use the dll's that are on 12 folder. For developing, you'll have to copy the dll's on a local folder and reference them into your project. To check if the application works well have to be executed on the SharePoint machine not on the developing machine.
I assume you're using Sharepoint 2007, so you are able to find the libraries in the Bin folder in the 12 Hive on where SP is installed. That is usually:
C:\program files\common files\microsoft shared\web server extensions\12
You will need a reference to Microsoft.SharePoint.dll.