This have been told here but I really can't figure why Visual Studio 2013 Ultimate (x86 installation) generates only bin\Debug and does not generate bin\Release folder.
Does anyone know why it does not generate the release folder?
Here is my Visual Studio version (am I missing a Service Pack?)
My project is a Windows Forms Application.
My project is targeting .NET 2.0, it runs fine and bin\Debug is always generated. Here are my project properties with default configuration:
Hope you have set the Release configuration from here:
Also go to the Configuration Manager and check the Active Solution Configuration as Release.
Related
My development environment: SQL Server 2014, Visual Studio 2015, SQL Server Data Tools Preview (September) for Visual Studio 2015
I have a custom SSIS source component that I can successfully use on another SQL 2014 box with VS 2013 and SQL Server Data Tools - Business Intelligence. However, this component does not show up in the toolbox in VS 2015 Integration Services project.
The component is located in c:\Program Files (x86)\Microsoft SQL Server\120\DTS\PipelineComponents. It is also registered in GAC.
Do I need to make changes to the component so that it will work with VS2015?
More general question: how to troubleshoot issues like this?
I've managed to get the problem of adding a custom SSIS component to a Visual Studio 2015 SSIS package. This maybe have been enabled by the release of SQL Server 2016 CTP 3.2, but I thought that I'd put this out there in case it helps anyone.
First of all let me just let everyone know what system I'm using in case this doesn't work for everyone:
My system is: Windows 8.1 64 bit
Visual Studio Community 2015 Version 14.0.24720.00 Update 1
Microsoft SQL Server Integration Services Designer Version 13.0.900.80 (I've installed the SQL Server 2016 CTP3.2 so the version of SSIS is this version - this may be part of the problem and it isn't a fully released product and this may be a bug)
Microsoft .NET Framework Version 4.6.01055
In my c# class project I used the .NET Framework 4.6
(Project Properties->Application).
I made sure that I added to the gac using the gacutil.exe in the following folder:
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6 Tools
and I copied the dll to the following folder:
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\PipelineComponents
After refreshing the SSIS toolbox the component now appears in the Common folder/subsection.
I hope this works for everyone or is at least of use to anyone else who has had this problem. I was so happy after trying nearly everything and it coming up blank to see the component appear in the SSIS toolbox and know how frustrating this kind of thing can be!!!
Matt
In VS2015 Solution Explorer, right click on the .dtproj file and select properties. On the General Tab choose the SQL Server version that matches the component version. If the component worked on VS2013, choose 'SQL SERVER 14' when opening the package in VS2015.
I have recently migrated my visual studio 2010 projects to 2013 but my database project looks unhappy about it. I have a TFS build definition which helps me deploy the database project and i have specified the (.sln) solution file and the .proj separate file which helps e drop the file to some location. This has been working well when I was using 2010 but right now its giving me the following error.
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I replaced .sln file with the .sqlproj and this seems to fix the failing build definition but I don't get any deployment files.
Do you have any suggestions please, this is blocking my work right now.
You need to set the environment variable VisualStudioVersion=12.0 when building from the command line if you are using VS2013. SQL Projects rely on this to detect whether to use the VS2012 (v11.0) or VS2013 (v12.0) targets file when building.
Normally when a new Visual Studio version is released there's an accompanying .Net version update that changes the default VisualStudioVersion default value, but with VS2013 this didn't happen. Hence SQL Projects (and some other resources with similar version-specific dependencies) require 12.0 to be explicitly set as the version, since 11.0 is the default.
Also when running on a build server you must have a version of Visual Studio 2013 installed that includes the SQL Server tools. Full instructions on setting up a build server are in the whitepaper and presentation on the SQL Server tools team blog.
Can any1 help me on generate *.appx package on every check-ins we do on Visual Studio. How to automate the process of generating the appx through TFS build. Please let me know what r the changes i need to do *.csproj so that appx package is created.
msbuild WinStoreProject.csproj /p:AppxBundle=Always/p:Configuration=DEBUG /p:AppxBundle=Always /p:Platform=x86
Don't worry about the platform identifier. This approach will build a package that can support x64/x86/ARM. Look in your solution root under the AppPackages folder.
Enjoy!
The .csproj file of Windows Store projects by default builds the AppPackage as well. You can try it out yourself by calling the following from the command line:
msbuild WinStoreApp.csproj
By default this will create the AnyCPU package. You can set the Platform property to create AppPackages for other platforms:
msbuild WinStoreApp.csproj /p:Platform=ARM
I suppose you will need Windows Server 2012 R2 to build Windows 8.1 applications an at least Windows Server 2012 to build Windows 8 applications. You will also need a working build environment. Visual Studio Express 2013 for Windows will certainly suffice; Windows SDK for Windows 8.1 and Microsoft Build Tools 2013 should be enough as well.
When I click on EDIT SCRIPT button for Script Task in SSIS 2012 package,
It does not open the Script editor rather it shows:
"cannot show Visual Studio Tools for Application editor"
Couls not load file or assembly
"Microsoft.visualstudio.tools.applications.core version=10.0.0.0 ...."
system can not find the file assembly specified.
I tried the solutions provided in the following links:
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e5337b0c-7f70-4603-859e-fbc7d0cf1c37
SSIS Script Editor throws an exception
First of all go to Program and Features and check whether you have
"Microsoft Visual Studio Tools for Applications x86 Runtime 3.0"
installed. Most probably you will see this below
"Microsoft Visual Studio Tools for Applications x64 Runtime 3.0"
If it is not installed then you have the same issue that i have.
To resolved this error, I put in my SQL Server installation disk. Then go to redist->VSTA->runtime->x86 and then run VSTA_RT30.msi
The workaround mention in this link solved my issue:
https://connect.microsoft.com/SQLServer/feedback/details/776248/could-not-load-file-or-assembly-microsoft-visualstudio-tools-applications-core
Both the x86 and x64 runtimes must be installed, currently one or both the runtimes may be missing depending on the order of the SQL Server 2012 installation. As a workaround, check in Control Panel - Programs and determine which of the component is missing (it should be listed as Microsoft Visual Studio Tools for Applications x86 or x64 Runtime 3.0). You can install the component manually from your installation disk or download from the \redist\VSTA\runtime\ folder.
It is year 2021, when searching for the error, this is the top hit. The solution that worked for me with Visual Studio 2019 is to download and install "Visual Studio Tools for Applications 2019"
Link:
https://www.microsoft.com/en-us/download/details.aspx?id=58317&WT.mc_id=DX_MVP4025064
Interestingly, this is not provided as an option in Visual Studio installer. The above needs to be manually downloaded and installed.
By now, SQL Server 2012 Service Pack 1 is out. Try updating your release and after that, you might even consider putting the Cumulative Update 1 on top of it.
More about CU1: http://blogs.msdn.com/b/sqlreleaseservices/archive/2012/11/21/cumulative-update-1-for-sql-server-2012-service-pack-1.aspx
goto SQL server installer folder and install these msi files
redist/VSTA/designtime/VSTA_DT30msi
redist/VSTA/runtime/x64/VSTA_RT30.msi
redist/VSTA/runtime/x86/VSTA_RT30.msi
Now that Visual Studio 2012 is released, where can I download the accompanying 2012 Report Viewer Runtime so I can install it on my server? Is there a redistributable installer included with Visual Studio 2012?
Specifically, I'm looking for the updated 2012 version of this: Microsoft Report Viewer 2010 Redistributable Package
I believe I've found a temporary workaround for this:
In your project's references, select the Microsoft.ReportViewer.WebForms assembly.
Add a reference to C:\Windows\assembly\GAC_MSIL\Microsoft.ReportViewer.Common\11.0.0.0__89845dcd8080cc91\Microsoft.ReportViewer.Common.dll
In the properties window, set "Copy Local" to True for both assemblies.
Deploy your project to the server.
I haven't tested this extensively, but so far it appears that simply copying the assembly to your project's bin directory satisfies the runtime requirements on the server.
the final version of the installation program is http://www.microsoft.com/en-us/download/details.aspx?id=35747