VB .net in SSIS.

Howdy all. I'm am not at all a .net guy, and don't know that I'm looking to
become one. I was on a mission to accomplish something similar to what is
described here: http://www.sqlis.com/default.aspx?307,1 (actually, I wanted
to do something even simpler) when I realized, "this is not VB Script like
DTS had".

Im sure Im not the first DBA to realize this and become terror stricken. I
got pretty good at VBS, and felt confident in tackling anything that came my
way in DTS, but this is new... this is CHANGE!!!!

Is there no way to continue using VBS in SSIS? Alternatively, is there
another way to accomplish my goal in SSIS without becoming a .net guy?

Is becoming a .net guy the only way for DBA's to survive in the future?

TIA, ChrisR

"ChrisR" < noFudgingWay@NoEmail
.com> wrote in message
news:eyQ$KMtHHHA.3780@TK2MSFTNGP02.phx.gbl...
> Howdy all. I'm am not at all a .net guy, and don't know that I'm looking
> to
> become one. I was on a mission to accomplish something similar to what is
> described here: http://www.sqlis.com/default.aspx?307,1 (actually, I
> wanted
> to do something even simpler) when I realized, "this is not VB Script like
> DTS had".
>
> Im sure Im not the first DBA to realize this and become terror stricken. I
> got pretty good at VBS, and felt confident in tackling anything that came
> my
> way in DTS, but this is new... this is CHANGE!!!!
>
> Is there no way to continue using VBS in SSIS? Alternatively, is there
> another way to accomplish my goal in SSIS without becoming a .net guy?
>
> Is becoming a .net guy the only way for DBA's to survive in the future?

I don't see how changing the scripting language from VB Script to VB.NET
requires you to become a '.NET Guy'.  The basic language constructs from VB
Script are present in VB.NET, and you can just ignore all the new
capabilities .NET gives you.

The ways in which VB.NET differs from VB Script are almost all good.  It's
much, much easier to write reliable code and figure out problems in VB.NET.
It's compiled, it's fast, you can find bugs when you're writing code instead
of when you're running it, and you can debug it.

To become a .NET programmer you need to learn:
A .NET Language (vb.net, c#, etc)
.NET Framework Class Library
Basics of Object-Oriented programming
Multiple of
Windows Forms Applications
Web Forms Applications
Web Services
Windows Services
Console Applications
Software Development Lifecycle Practices

David

Apparently I jumped the gun a bit, my apologies. It's all just so... scary
looking. ;)

Thanks!


"David Browne" <davidbaxterbrowne no potted meat@hotmail.com> wrote in
message news:uFgZWPuHHHA.420@TK2MSFTNGP06.phx.gbl...
>
>
> "ChrisR" < noFudgingWay@NoEmail
.com> wrote in message
> news:eyQ$KMtHHHA.3780@TK2MSFTNGP02.phx.gbl... 
is 
like 
I 
came 
>
> I don't see how changing the scripting language from VB Script to VB.NET
> requires you to become a '.NET Guy'.  The basic language constructs from
VB
> Script are present in VB.NET, and you can just ignore all the new
> capabilities .NET gives you.
>
> The ways in which VB.NET differs from VB Script are almost all good.  It's
> much, much easier to write reliable code and figure out problems in
VB.NET.
> It's compiled, it's fast, you can find bugs when you're writing code
 instead
> of when you're running it, and you can debug it.
>
> To become a .NET programmer you need to learn:
>     A .NET Language (vb.net, c#, etc)
>     .NET Framework Class Library
>     Basics of Object-Oriented programming
>     Multiple of
>         Windows Forms Applications
>         Web Forms Applications
>         Web Services
>         Windows Services
>         Console Applications
>     Software Development Lifecycle Practices
>
> David
>
>