December 2, 2011 at 3:33 am
i have a requirement which i believe SSIS would be the best option.
first step: update records in a sql database table based on certain criteria. (this works)
I used an 'Execute SQL Task' item for this.
second step: access, and run, a project that has been created in visual studios. This project contains one page. the code for that page is all contained in the Form_Load function, so it just needs to load the page and its done.
I attempted to use an 'Execute Process Task' here. i placed it in the Control Flow tab, double clicked it, clicked the Process option and then added the full path to the .sln file in the 'Executable' option.
This hasn't worked though.
Is this possible? if so, how would i go about doing this?
thanks
December 2, 2011 at 3:41 am
I think you might have more success if you create a console application to do this and then just run the .exe that that produces from within SSIS.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
December 2, 2011 at 4:19 am
thanks for the advice.
i've followed the steps from this link, to create a consoleapp
http://averagecoder.net/passing-arguments-to-your-vbnet-console-application.htm
within the SSIS package, i've added the Execute Process Task and added the full pathway to the executable (in the bin folder) to the Process/Executable section - the same as how i previously did it in my first post.
unfortunately it doesn't seem to be running as my expecting results have not happened. i know the vb code works because i've been running it manually for a number of weeks now. When runnign the SSIS package, it completes with no errors.
December 2, 2011 at 4:43 am
Can you summarise what the app is supposed to do?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
December 2, 2011 at 4:57 am
sure:
it runs a Stored Procedure to get back a set of data.
it then cycles through that set of data, opening a Web Service and passing the data through one row at a time.
for each row, if the data has successfully been passed, it will insert a record into another table to signify success.
each time the application runs, the expected amount of data that gets sent wont be more than 20 rows.
December 2, 2011 at 5:03 am
davidandrews13 (12/2/2011)
sure:it runs a Stored Procedure to get back a set of data.
it then cycles through that set of data, opening a Web Service and passing the data through one row at a time.
for each row, if the data has successfully been passed, it will insert a record into another table to signify success.
each time the application runs, the expected amount of data that gets sent wont be more than 20 rows.
OK - sounds like something which a Foreach Loop would eat up directly in SSIS. But regardless of that, I'm not sure why you are having issues. I think I'd start by verifying that the console app is definitely running and that any parameters you are passing to it are being passed successfully.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
December 2, 2011 at 5:31 am
i thought that perhaps the code in the Console App wasn't working even though it worked when set up as a standard Project, so i ran the Console App manually and it worked.
that tells me that i haven't set up the SSIS task to call the console app properly.
when double clicking the task, and looking at the Process section, the details are as follows:
RequiredFullFileName - True
Executable - C:\documents and settings\folder1\folder2\Visual Studio 2010\Projects\myConsoleApp\bin\debug\myConsoleApp.vshost.exe
working directory - C:\documents and settings\folder1\folder2\Visual Studio 2010\Projects\myConsoleApp\bin\debug\myConsoleApp.vshost.exe
FailTaskIfReturnCodeIsNotSuccess - True
SuccessValue - 0
timeOut - 0
windowStyle - Normal
December 2, 2011 at 8:43 am
You can include VB.Net or C# code in an SSIS package using a Script task. So, you could take the code from your VB.Net app and add it in the Script task.
Hope that this helps...Chris
December 7, 2011 at 8:39 am
i've finally got my package working.
i used the Script Task item. Had a few problems but solved them in the end.
i'm sure it would have worked with the Console App as well, i just found it easier with the Script Task!
thanks
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply