It's not valid to say "always stored procedures". It totally depends on the application.

In any case, unless the stored procedures are plain old CRUD ones then ORMs (including Linq2Sql and...

Add an OnError handler for the data flow task (or the FoorLoop container - depending on your needs) and set the system propagate variable for that task to False. This...

Learning to use Visual Studio is the least of your worries in my opinion. I assume you have not coded before using VB.NET (unless you did it using another IDE...

They're not exactly the same. The difference is that a stream will have an open handle on the file the entire time. Plus you'd have to manage the buffer...

A Script Task is the way to go here in my opinion.

File I/O is the bottleneck so you want to limit the number of writes you do. I recommend caching...

This is more of an implementation details on the wcf service side. The wcf service will need to ensure the method returns immediately. Look into the WCF IsOneWay attribute,...

You will need to communicate with the Reporting Services web service. This will require creating a proxy class and calling the required functions.

Haven't done it myself yet but here are...

Note that creating the file does not only validate the full file path (folder + filename). It also does other things like checking that the account the code is running...

You will need to close the file stream before attempting the delete.

Try something like this:

Dim folder as string = CStr(Dts.Variables("FileLocation").Value)

Dim fileName as string = CStr(Dts.Variables("Filename").Value)

Dim filePath As String = System.IO.Path.Combine(folder,...

One option is to:

1. Create an ADO.NET Connection Manager named "MySQLConnMgr"

2. In your Script Task have something like:

Dim oConn As System.Data.SqlClient.SqlConnection = DirectCast(Dts.Connections("MySQLConnMgr").AcquireConnection(Nothing), System.Data.SqlClient.SqlConnection)

'TODO: Use the connection

If oConn IsNot Nothing...

You'd need the web page to somehow check the status. For example this could be by checking a flag in the database somewhere and then sleeping for a bit if...

What is the UI for? Just to let you set the variables in the SSIS package, execute it and then get the result?

Note that if it's a .NET EXE then by *default* they are not trusted and will probably fail when run off a file share unless they have been designed to...

One option is to do the *whole thing* in a Script Task. This gives you all the flexibility you need. I've had to do this on a few ocassions...

I'd probably do it all in a Script Task. I'm not a big fan of sticking in Script Tasks to increment variables and stuff.