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.
Related
I'm developing my C# application with database hosted on SQL server. I just need to know how to create an installer for the client. And what should I install on the client machine?
I tried publishing the application but database changed are not reflected, so what should I do?
I've tried searching on the internet how to publish this application and give it to the client, but I couldn't find anything helpful.
Note: I'm using Visual Studio 2012, SQL server 2012.
There are many posts online regarding deploying databases along with your web applications. I would suggest using a Database Project to manage your database changes and installing the SQL Server Data Tools.
Here are a few tutorials:
How to: Deploy a Database With a Web Application Project
SQL Server Data Tools Updated for Visual Studio 2012
Deploying Database Projects
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 have a database in MS Access 2003 that is residing in my server running MS Windows Server 2003. I would like to develop C# code to manipulate data in my database. Can I use the free Visual Studio Express to develop the code to run in the previously mentioned environment?
When you download Visual Studio 2012 Express it will include very limited functionality. However, it will accommodate all the standard and basic Developer goals. Any functionality that you do not have, can either be added by downloading additional components. The other option would be to purchase a more advanced version.
By default yes it will work with your environments you asked about.
All the variations can be found here:
Hopefully that helps.
I need to write a proof of concept with the TFS API (fetching data from tfs server regarding workitems and put this data in our tables).
Can Any body suggest a way to do this without setting up my own TFS Server.
You can just set up one on the MS Cloud TFS which is now on tfs.visualstudio.com (previously called TFSPreview.com.
With TFS, your code is accessible from anywhere. You can check in code
directly from Visual Studio and Eclipse, or you can use command-line
tools to check in your code from Xcode and other IDEs. Since it's all
in the cloud, your team can get started quickly with no infrastructure
to manage.
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.