I have merged four WPF tools into one as per my client requirements. The four WPF developments was done in Visual Studio 2015, and I merged them in Visual Studio 2017, and they have given a set of instructions on how to create an EXE file using InstallShield for deployment on their machines.
But when I do it I get an error, -6416, and when I search it here I do not get that error code.
Long story short, how do I go about this? I have tried this, but it did not work.
Any ideas? Please note that the code is connected to the database, and I want that EXE file to work whether they have a database or not.
Related
Full disclosure, I had a minimum level of comfort with designing reports in VS 2005 (just enough to get the job done) and recently my computer was changed and I now have SSMS 2016 and VS2015 instead of SSMS 2008 and VS2005.
I can't seem to open my reports, .rdl isn't even a listed file extension. If I go to the directory where the .rdl files are, I can click on them and open with vs 2015, but it just gives me the xml code. So is there any way to import my old reports into VS 2015? I don't even see a place or tool bar to edit/create reports.
I tried to change the installation to include MS SQL Data Tools, but I could not find the package (maybe I have to get it online?)Presumably, I could then edit the design and layout. But right now, I don't even understand what most of the tool bar options are.
So, as for a question - Where do I start? Once I get SQL Data Tools installed, can I edit the layout/design of existing, VS2005 reports and deploy them to our existing Report Manager as I have done in the past with VS 2005? Thanks for helping!
You definitely need to install SQL Server Data Tools for Visual Studio 2015. It looks like this is now available. Without having SSDT installed VS2015 will have no concept of what an RDL file is.
I personally have no experience with VS2015. VS2013 though can open VS2005 reports, and you can deploy them as before,.
Personally I found the old reports now looked a bit messy and I had to reformat a number of them (thought this may not have been necessary - I might just have not liked the way the guy before had coded them)
I have one already developed SSIS application using SQL Server 2005. I'm trying to view the script like below:
Right click -> Edit -> Script -> Design script
[normally instade of "Design script" it should come "Edit script". I think, due to SSIS 2005 its like that]
However, its not showing me underline script.Its not showing any error as well.
I have BI studio 2005 installed. However, I can not see VB under(file -> new -> project) if I'm going to create new project. So, do I need a Visual studio version 2005 with VB to be installed to open this?
Is there any other way to see this? OR is there any settings needs to be changed to see this underline script?
Hum I don't know what is causing that error but Visual Studio BI edition is enough (and required) to edit all functionality of a SSIS. Including the VB code in the Script Task without the need to install the whole VB environment.
You should really watch about any error reported when you open the solution, especially the "corruption" messages which are usually indicators that Visual Studio cannot decipher the parts of the SSIS that were encrypted (depending of the security model of your SSIS).
You also would want to make sure you've installed the Visual Studio BI for 2005 and not 2008 (or other) since, unlike 'classic' projects, SSIS projects are highly tied with the version of VS BI it was created with.
I have my my setup project in (Visual Studio 2015: Community Edition) ready to be built and create my program installer. But, obviously the program will not work on other computers without the appropriate redistributable package installed on the clients computer.
So, I need to set that up in my project but I do not know how. I read in a post on another site that it is located in:
Project>>Setup Properties>>Prerequisites
But, all I just see are selectables for ".net framework" related things. Also, I read that merge modules are not good to use due to servicing issues.
If you have any insight into whether I am needing to download an extension for the correct prerequisite to appear, use merge modules, or something else it will be greatly appreciated!
I have several .sql files in my visual studio 2010 project.
I am looking for an extension or add on where I can right click on the sql file and execute its contents against a sql server database.
Anyone know if such an extension exists?
Starting with SQL Server Denali (at least in the community preview version I installed to play with), SQL Management Studio is integrated into the Visual Studio 2010 IDE. So you get all the syntax highlighting, Object Explorer, etc., all from within VS2010.
That said, I didn't specifically try adding a SQL script to an existing project (and I uninstalled the shared features last week because there were... issues), but with such a tight integration, I assume doing more or less what you're asking for is the intention.
I'm running Windows 7 x64 with Visual Studio 2008 (SP1). Yesterday I came across an issue when creating WPF projects. I don't know if I've created any other WPF projects since I installed Win7.
First of all, in the Create Project dialog, the project type says "csWPFApplication" which is weird enough and I never noticed before. When I try creating the project I get 2 Package Load Failure errors for Microsoft.VisualStudio.Internal.WPFFlavor.WPFPackage and then a message that "The project file ... cannot be opened. The project type is not supported by this installation.
I tried a number of different suggestions from Google and even uninstalled/reinstalled to no avail. Any ideas?
Try starting Visual Studio with.
C:\Program Files\Microsoft Visual
Studio 9.0\Common7\IDE\devenv.exe
/resetskippkgs
I would also try to just create a blank solution/WPF project. and then add the files from your old project one at a time, and see if you still get the error.
If that doesn't work, I would try to uninstall and reinstall .NET 3.5 which looks it could be corrupt.