I have built custom components for SSIS 2008 using VS2008. Can I build a custom component for SSIS 2008 using VS2010?
Thanks
Yes.
Yes, you can build SSIS 2008 custom components using Visual Studio 2010 but you need to target .NET Framework 3.5 because SSIS 2008 does not support .NET Framework 4.0
Reference:
You can take a look at this answer on MSDN forum that discusses a similar question.
SSIS Custom Components and .NET 4.0
Related
I have a wonderful solution in Visual Studio 2012 with a Web project using WebAPI and a supporting Web Service project for data using Entity Framework (EF) Code First. I was just told I need to see about using Visual Studio 2010.
Is there something I can do to work on this project in Visual Studio 2010?
As Henrick answers: you do not upgrade/downgrade VS installs, rather you install versions side by side.
You note two technologies that might be problematic:
EF Code First: this is supported from 4.1 (or was it 4.2?) which is supported against .NET 4.0 and VS2010. Providing your not using enum or geo/spatial data types (which require .NET 4.5) this should work, but you'll need to ensure you update to the EF5 NuGet package for .NET 4.
WebAPI: This is new in MVC4, which comes with VS2012, but is a separate install for .NET 4/VS2010.
Finally. While some project types with round trip between VS2012 and VS2010 SP1 (you need the service pack) it is not true for all project types. Details are on MSDN.
You can install Visual Studio 2010 separately and open the project and see. There is no danger in having version 2005, 2008, 2010 or 2012 of Visual Studio installed.
Is there a way in Visual Studio 2012 Express to target .Net 3.5? By default .Net 4.0 is targeted, but i couldn't change it. Is there a way to change this setting?
Thanks!
I see the template export option under the File menu in Visual Studio 2012 Express. I have used it to create project templates for targeting .net 3.5 and .net 4.0.
Target framework is related to the project template not to the IDE and Since VS2012 doesn't have Export Template Wizard,I think you have to get a template project that targets .Net Framework 3.5 and create your projects with it.
Hope it helps
Where can I download a standalone installer for SQL CE 4.0 SDK / template to be used within Visual Studio 2010 > Project > Add Item?
I tried http://www.microsoft.com/download/en/details.aspx?id=17876 but it appears to be the runtime only.
I have also downloaded VS 2010 SP1 from http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23691 still no go. The about dialog version says SP1Rel.
See my blog post here for a direct link to the VS 2010 SP1 Tools for SQLCE 4.0 - http://erikej.blogspot.com/2011/01/sql-server-compact-40-released.html - keep in mind that the tooling is only avilable for Web project types.
I notice that Visual Studio 2010 database projects have a re-distributable component to support the deployment on end-user systems.
Will this component work against .Net 3.5, or does it require .Net 4.0?
From what I can tell, Visual Studio 2010 database projects will require .Net 4.0 on the target machine. If you inspect the redistributable components in %ProgramFiles%\Microsoft Visual Studio 10.0\VSTSDB\Deploy using Reflector, you'll see that they all depend on version 4.0.0.0 of the framework libraries.
In addition to this, the .deploymanifest files (which are really MSBuild files in disguise) specify 4.0 as the MSBuild tools version.
It looks like you would need to use Visual Studio Team System 2008 Database Edtion GDR R2 (which of course requires VS 2008) if you want to target .Net 3.5 on the database server.
Is there a way to change .NET framework version of Visual Studio 2005 to 3.5?
No. Visual Studio 2005 only supports .NET 2.0 out-of-the-box. It can be updated to support .NET 3.0.
It is possible to compile .NET 3.5 code with a Visual Studio 2008 Express Edition, or without Visual Studio 2008 using Mono and I think the Windows/.NET SDK. However these will obviously not be integrated into Visual Studio 2005.
Visual Studio 2005 only supports .NET 2.0. The format of the solution file (.sln) changed in Visual Studio 2008 to allow you to select the target .NET version.
VS2008/2010 have a visual way of setting the project setting "TargetFrameworkVersion" which makes it easier, however I have found that adding the same tag to a VS2005 project will change the target framework. You might try adding 1(one) of the following into the section of your VS C# project.
<TargetFrameworkVersion>v3.0</TargetFrameworkVersion>
<TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>