Change the Language for SSIS Script Task

Question

Post reply

Change the Language for SSIS Script Task

AndrewSQLDBA

SSC-Insane

Points: 21827
More actions
June 23, 2010 at 4:05 pm

#157032

How can I change the OOP language that SSIS uses for things like the Script task? Mine comes up to use C#. I can use that, and that is the language that I program with. But it seems that all the examples and samples that I am finding are written in VB.NET.
Thank you in advance
Andrew SQLDBA
August 19, 2023 at 8:02 am

This was removed by the editor as SPAM

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply

Raunak Jhawar SSCoach Points: 15701 More actions · Answer 1

Hi,

In the Script Task Component you will find a property by the name "ScriptLanguage"

This property can be set to either C# or VB

Raunak J

David Data SSCrazy Points: 2965 More actions · Answer 2

Just to add to what Raunak said - you can ONLY select the script language when you create a new Script Task; once you've clicked on Edit Script the language is set.

C# is the initial default, but if you mostly use VB you can change the default to that via Tools | Options, then scroll down to Business Intelligence Designers | Integration Intelligence Designers. (Yes it is fairly well hidden 🙂 )

AIRWALKER-375999 Hall of Fame Points: 3040 More actions · Answer 3

In the ScriptLanguage option I only have VB.Net, how can I add c#

thanks

David Data SSCrazy Points: 2965 More actions · Answer 4

AIRWALKER, which version of SQL Server do you use? SQL Server 2008 SSIS supports both VB.NET and C#.NET, but earlier versions only supported VB.NET (or plain old VB if you go far enough back).

AIRWALKER-375999 Hall of Fame Points: 3040 More actions · Answer 5

David Data (12/17/2010)
AIRWALKER, which version of SQL Server do you use? SQL Server 2008 SSIS supports both VB.NET and C#.NET, but earlier versions only supported VB.NET (or plain old VB if you go far enough back).

I'm using sql 2008 R2

thanks

Paul_Blackwell Ten Centuries Points: 1085 More actions · Answer 6

From the menu bar Tools>Options:

In the Options dialog box, select Integration Services Designers under the Business Intelligence Designers, in the left panel. Then select the language in the Language drop down Script panel.

@ David Data

Woops! I missed your post.

silkmane SSC Rookie Points: 43 More actions · Answer 7

Thanks guys

I've been racking my brains trying to find out where to change this option...:w00t:

Thanks again

sqlserver8650 Ten Centuries Points: 1121 More actions · Answer 8

Hi

First I choosen the C# when I writing the code in c# I got struct

So how will I change the language from c# to vb.net with out removing the script task

After changing the language in the designer

options-->tolls-->business intelligence designer--->integaration intelligence designer

stil shows c# only

Thanks...

David Data SSCrazy Points: 2965 More actions · Answer 9

Once you have started writing a script, you can't change the language in that task.

What you'll have to do is create a new script task, set the language you want BEFORE you do any editing, then copy what you've done already into it.

angel.fish Valued Member Points: 71 More actions · Answer 10

Very helpful post! I was able to locate VB Script, I was worrying that I was going to need to learn C# !

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 11

David Data (6/25/2010)
Just to add to what Raunak said - you can ONLY select the script language when you create a new Script Task; once you've clicked on Edit Script the language is set.
C# is the initial default, but if you mostly use VB you can change the default to that via Tools | Options, then scroll down to Business Intelligence Designers | Integration Intelligence Designers. (Yes it is fairly well hidden 🙂 )

ok, thanks to everyone.:-)

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/