Do I need ODTforVS2017_122011.exe? - visual-studio-2017

I have VS2017 and plan to do some C# development that needs to access Oracle 12c database.
I went in Oracle site and downloaded ODTforVS2017_122011.exe. The installation was successful.
But when I tried to declare my connection type OracleConnection, my project does not know it and I can not reference Oracle.ManagedDataAccess. I had to go to Nuget to install them to satisfy the compiler.
So, my curious question is: is the ODT installation from Oracle site necessary or Nuget installation only would suffice? I just do not want to install to much irrelevant stuff that I would not be able to justify.

I don't believe you need the tools, no. They're Visual Studio features, rather than tools needed at execution time.
From the download page:
Oracle Developer Tools for Visual Studio enables Visual Studio data features such as Server Explorer integration, TableAdapter Configuration Wizard and Entity Designer and also includes many useful Oracle specific tools.
So you may find it useful to have those tools, but I don't believe they're required on every machine where you want to either develop or deploy your application.

Related

Tabular Model: Import data in compatibility 1400

Hope you are doing well.
I really need your help.
I am trying to create a tabular model in Azure analysis service with SSDT 2017.
Data is in Azure SQL Server.
I chose the compatibility 1400 and I saw the database objets.
But when I try to import data from the database I have an error "error ole dB".
I have also created a model with compatibility 1200. And all runs well with this compatibility.
Do you have any Idea on how to solve this issue ?
Please check your Azure SQL database compatibility level.
In SSMS, right-click the database name > Properties > Compatibility Level.
For more details, please reference: Compatibility level for Analysis Services tabular models.
Set the compatibility level 140 and try again.
Hope this helps.
Please try the latest version of SSDT 2017 (15.9.0). Download and install from here. Before installing SSDT for Visual Studio 2017 (15.9.0), uninstall Analysis Services Projects and Reporting Services Projects extensions, and close all VS instances.
Another possible solution is to try SSDT 2019. If you do not have VS 2019 download and install the Community version, then install the Analysis Services extension.

Visual studio: No sql server compact option in data connections

It is really unbelievable that I am not able to find such a simple thing, I have searched everywhere.
Actually I want to open sdf file which is a part of my project. I found that it can be opened with sql server management studio, external tools etc. but I want to open it in Visual studio by adding a simple data connection.
Am I asking too much? But Man! I am not able to find this simple thing on internet.
I my add connection window I don't see option for sql server compact data connection.
I already installed compact edition and when I am trying to install it again it is saying that it is already installed.
But for some reason visual studio is not showing up in the list of Data Sources Types.
I found this question, he is facing the same issue and his issue was also not resolved even after applying what was told in the answer
Adding SQL Server Compact Edition data source to Visual Studio?
Could somebody help to get this simple thing working?
Install the SQL Server Compact Toolbox, it will also install a DDEX provider, that allows you to connect in Server Explorer (for 4.0 only, however)

VS2017 not showing Report Viewer in prerequisites

I am trying to deploy a wpf application with an embedded rdlc report using clickonce. The previous version of report viewer (in VS2015) was built-in so it was easy and convenient to use and I had no issues deploying this project.
Now since easy and convenient is not the goal anymore, in vs2017 after a failed deploy with an error message that gave me absolutely no help, I have come to realize that apparently you have to install 2 additional VS extensions and a report viewer runtime on every machine where an app uses and rdlc reports (feels like crystal reports all over again) and you have to exclude the automatically included Chinese localization files in your clickonce deployment (which cause a manifest parse error). Anyway, the instructions on MS website say that click once should have a "Microsoft Visual Studio Report Viewer" prerequisite option to select as requirement of installing your app. However, after installing the runtime on my development machine, restarting visual studio, this option is not available. Does anyone know how to get this to work?
I used Project|Manage NuGet Packages to add this package to my project.
https://www.nuget.org/packages/Microsoft.ReportViewer.Runtime.Common/12.0.2402.15
If you search with Manage NuGet Packages, there's quite a few ReportViewer related items. I'm not sure which ones are appropriate to your WPF app.
Anyway, the deployment project picked up the various ReportViewer assembly dependencies and everything seems to be working without the EXE redist from MS.

how to deploy c++ application and create setup file for my music player

I have developed one music player in C++. Now I want to create setup.exe for that application so that i can put that application for downloading for other users. When we download some software from website we get setup for installing that application. I want to know how can i create that setup file for me cpp application. Please help as soon as possible
For Windows platform
There are loads of solutions some free some not
personnaly I'd recommend wix (it's free, it uses windows installer technology) but for some it's overkill
checkout
http://wix.tramontana.co.hu/
for a great example/cook book
Others include
install shield http://www.installshield.com/ (used to have a cool debugger, but not free)
inno Setup (http://www.jrsoftware.org/isinfo.php)
Wise Installer (OK looks like it's dead!)
Do it by hand using ORCA (an MSI editor http://msdn.microsoft.com/en-us/library/aa370557(v=vs.85).aspx)
WIX 3.X (http://wix.codeplex.com/releases/view/115492)
You can also do this with the free edition of Advanced Installer. Here is 5 minutes tutorial showing how to do it: http://www.advancedinstaller.com/user-guide/tutorial-simple.html
To create projects of type "Simple" you don't need a license and you can deploy the package for commercial purposes too.

Automated build installer using team foundation service

I have started using the preview of Microsoft Team Foundation Service (TFS in the cloud, henceforth TFService) for a small project, and I'm currently setting up builds using the online build service included with TFService.
What I want to do is to add an installer of some kind. I've previously worked with InstallShield Limited Edition, WIX and Inno Setup and would like to keep using one of those if possible.
I've previously integrated Inno Setup as part of a build process (TFS 2010). This involved installing Inno Setup on the build computer, and adding a custom build task for running an inno setup script. The last part should be possible with TFService as well, because it's possible to create custom build process templates.
However, I realize that installing anything such as Inno Setup or InstallShield will not work with TFService, since it's not possible to install any 3rd party software on the build computer (it's just a cloud service running on some unknown virtual computer which I cannot access).
So my question is; is there a way to automatically create an installer as part of a build process running on TFService? For example, is the build service capable of building installshield projects out of the box (there's a license included with Visual Studio after all)? Or are there other ways to do this?
I have some experience with this trying to get WiX and InstallShield to work with Microsoft TFS Preview cloud service using their managed build agents. On these agents, you don't have administrator rights and you can't install software.
This currently rules out InstallShield which must be installed.
It is however possible to check the WiX binaries into source control and pull them down as part of your build.
WiX uses .wixproj files (MSBuild) to define their project compile activities. This references a targets file and other properties ( referencing registry values ) that won't exist when you deploy this way. A small bit of hacking will get all of these properties to resolve to workable values.
The one problem you may still have though (and I'm thinking TFS managed build environment ) is that you may have to configure your projects to skip MSI ICE validation suites. On the build machines, I played on the windows installer service was outright disabled and this prevented the tests from running.