I'm trying to setup Visual Studio's Server Explorer to connect to a postgresql database. I am using ASP.NET Core & EF Core with npgsql.
This feature works fine with SQL Server but there's no option to connect to postgresql and my attempts (including this guide) have failed. I'm using Visual Studio 2017 RC with MSBuild .NET Core, but I could downgrade to 2015 if necessary for this to work.
My aim is to be able to edit data from within VS and have a development 'localdb' similar to the one provided with SQL Server.
Solved this by downloading the ODBC driver, entring my credentials, then adding it to Visual Studio through 'Add Connection'. For some reason only the 32-bit version worked (on my 64-bit machine).
Related
I'm creating a hotel management service in C# on Visual Studio (Mac) and I can't seem to find a good explanation on how to add a local database file to my project. I created my database table in open office (.odb file) but there doesn't seem to be a way for me to implement this in my project. The documentation has nothing on this either. Any one got a clue how to add databases to a Mac Visual studio project?
there are no localDB in visual studio for mac, you need to install the docker image for sql server.
here is the link
You can run SQL Server on a Mac now:
https://database.guide/how-to-install-sql-server-on-a-mac/
Using Docker it can be made as your localhost SQL Server. I've done this and it works. SQL Management studio for Mac is useful too.
Hope this helps someone.
Consider using sqlite instead
Microsoft RazorPagesMovie tutorial using sqlite instead of localdb in Visual Studio 2019 for Mac:
Follow Tutorial: Get started with Razor Pages in ASP.NET Core
And the second part: Add a model to a Razor Pages app in ASP.NET Core
I have downloaded BIDS and SSDT for 2015, but these don't seem to allow me to open a .rptproj file in my sln. It tells me that the application is not installed. How can I open this? It opens perfectly fine on vs 2012.
Currently the SQL BI project types (SSAS, SSRS, SSIS) are not supported on Visual Studio "15" Preview releases. The BI projects rely on some things not available yet (for example SSIS requires VSTA) and so support is not yet available in that product. The list of available versions to install is on the SSDT download page and will be updated when future versions are supported.
For now, Visual Studio 2015 is the recommended version to use - it is backwards compatible for all project types through SQL Server 2012-2016, with relational DB projects, SSAS and SSRS supported back through SQL Server 2008.
I have few SSIS packages which is developed using VS2013 (.NET 4.5 Framework) in one solution.
And few packages which are developed using VS2012 (.NET 4.0 Framework) in another solution.
I want to integrate both solutions with TFS. Currently, I have integrated VS2013 with TFS and its works fine.
But, if I want to integrate VS2012 developed SSIS with the same TFS. There are two problems:
Do I need to do TFS installation has to be done in VS2012 or can i use same TFS installed for VS2013.
When I add these VS2012 solution to existing TFS, my build is overrritten by something and getting corrupted.
How I can keep both solutions of different framework in TFS?
TFS is a version control system. It can manage any text file and since an SSIS package (.dtsx) is just XML, it can version control it just fine.
There are many interfaces into TFS: there's a web interface, a UI shell as well as integration with Visual Studio 2010/2012/2013/2015.
The trick is going to be that you have two different version of SQL Server Integration Services packages there and they are not interchangeable.
VS 2010 or VS 2012 => SQL Server 2012
VS 2014 => SQL Server 2014
VS 2016 * => SQL Server 2012/2014/2016
If you open an SSIS project on an older version of VS, it will not be able to open the packages. You'll get an error about the XML being broken in VS and SQL Server won't be able to run them either.
If you open an SSIS project on a newer version of VS, it will automatically upgrade it to the current version. Which is great if you're migrating to that version, otherwise, see preceding point.
You will not be able to have a single solution that contains both 2012 and 2014 SSIS packages. You can edit projects in the VS version that corresponds to your SSIS project and then use whatever version of VS you chose for the TFS Team Explorer integration but that'd be silly as it's a feature of them all.
VS 2016
This gets its own section as it is currently in flux. However, the stated direction from the VS and SQL Server teams with regard to tooling is an important one. VS 2016 is slated to provide editing capabilities for SQL Server 2012, 2014 and 2016 SSIS packages. No more do you have to keep a version of VS around just to support each version of SQL Server. There will be a toggle that allows you to specify what version of SSIS this project should target.
And the people did rejoice and did feast upon the lambs, and toads, and tree-sloths, and fruit-bats, and orangutans, and breakfast cereals...
You can install the VS 2012 Update 5 and connect to your TFS Server(both 2013 and 2015) use it directly. For TFS and VS client compatibility information, please refer to this document：https://msdn.microsoft.com/en-us/library/vs/alm/tfs/administer/requirements?f=255&MSPPError=-2147217396.
I think you’re using TFS 2013, and you want to build your VS 2012 solution using TFS 2013 build definition, right? If yes, you can install VS 2012 Update 5 on your build agent machine, then add /tv:4.0 or /p:VisualStudioVersion=11.0 in your build definition>>Process>>MSBuild arguments. https://msdn.microsoft.com/en-us/library/ms164311(v=vs.110).aspx.
Additionally, TFS 2013 support TFS 2012 build controller/agent, so you can install TFS 2012 build controller/agent(on another new machine which installed VS 2012 Update 5) to connect your TFS 2013 Server collection, then use default TFS 2012 build template in build definition and specify TFS 2012 build controller in it. This TFS 2012 build server will be the dedicated build server to build VS 2012 solutions.
I've been trying to install MySQL Connector 6.9.4 (NET) for Visual Studio 2012 Ultimate but for some reason the MySQL Connection database does not appear inside Visual Studio.
Here's a screenshot of Programs and Features in Windows:
... and heres one of the Data Sources in Visual Studio 2012, running a C# Windows Forms Project:
Uninstall the connector and install version 6.6.5
Starting with version 6.7, the Visual Studio integration comes in a separate package. You should download the full Windows Installer available at http://dev.mysql.com/tech-resources/articles/mysql-installer-for-windows.html and install it.
If you install only the above driver, then you can access MySQL directly from your code but nothing else.
I have Visual Studio 2008 Business Intelligence version that was installed along with Reporting Services for SQL Server 2008 R2. I want to work with C#, but there are no options to create a C# project. I haven't been able to find any way to install a C# package or something.
Is there a way to add on C# functions, are they already built in but hidden, or should I just download a full version?
Thanks
UPDATE:
So I finally managed to find a download of Visual Studio 2008 Express, and installed the C# version. After installing I launched visual studio and it was the same thing, only the sql server projects came up as templates.
I found a forum that said to go into import and export settings and to reset my settings to general development settings, but I still cannot make a c# project.
UPDATE2:
I'm going to try installing VS 2012 Express to see if that works for me, since its the only download microsoft has that you can easily find now.
UPDATE3:
VS 2012 Express has been working just fine for me, and I still don't have the project templates in VS 2008 though.
You'll need to install one of the stand-alone editions of Visual Studio. Business Intelligence Studio, bundled with SQL Server, doesn't allow you to work with C# or other language projects.
SQL Server 2008 Business Intelligence Development Studio ("BIDS") is just an add-on over standard Visual Studio (VS 2008 in this case).
If you hadn't had Visual Studio installed before deploying BIDS, the most basic VS shell was installed along BIDS that does not allow you to work with projects other than the SQL Server BI family.
For you to work with .Net projects, despite being able to edit basic C# files already, you will need to reinstall any version of regular Visual Studio 2008 (e.g. licensed, express). This won't break your BIDS.