Last post Dec 06, 2010 03:48 PM by atconway
Dec 06, 2010 11:42 AM|billcrawley|LINK
Here's what I want to do, however I'm not sure of the best place for Excel. Excel files are sent via e-mail from various sources, from each source, they are sent in different versions of Excel and different information layouts, though from each source they
I want to give the user a front end to enable them to place the excel files into a drop zone and specify which files have come from which source. I then want to pass the file names and source origin to a workflow service. Based on this info the workflow
service will then take 1..n workflow routes based on the source with the ultimate aim that data will be placed into an SQLServer 2005 DB or if the Excel lines cannot be processed, then output for the user to see with a reason. Because this is quite a complex
task, I'm taking each source in turn.
My first set of Excel files come in 4 seperate files. I need to first merge the data in the Excel sheets to make 1 File for Processing. Some of the rows in the spreadsheets can be merged into a single line under certain conditions which will make the business
logic much easier further on. So, first off After the user has dropped the Excel files into the drop zone I need to open the spreadsheets and merge them. I then need to feed each line to a 'rules' engine to determine the data and business logic that needs
to be processed before updating the DB. So I thought I'd use a Workflow service for this since there will be no reason not to work on multiple sources at the same time as I progress through the development of the program. The problem I have is that unless
I download the CP1 for workflow I cannot use this directly (so it appears) for working with Excel. So I was looking at using possibly WCF as the 'feed' to the workflow service, but can I use WCF to do the possible long running process of merging the Excel
spreadsheets before pasing a row at a time down to the workflow service?
I'm using VS2010.
Dec 06, 2010 03:48 PM|atconway|LINK
So I was looking at using possibly WCF as the 'feed' to the workflow service, but can I use WCF to do the possible long running process of merging the Excel spreadsheets before pasing a row at a time down to the workflow service?
You should be able to do this (configure WCF to be long running), but making a WCF service be able to merge spreadsheet probably requires the Excel Interop .dlls and thus Excel needs to be installed on the server where the service is located. Office
Automation is typically frowned upon due to the issues that arise as seen in the MSFT link below:
Considerations for server-side Automation of Office:
If there is any way possible to do the data manipulation outside of Excel and then create an XML output to be exported into an Excel file, then I would go that route. It is best not to work with Excel open to manipulate data if possible.
Lastly you might be hard pressed to get specific WF questions answered here (on an ASP.NET forum). You might want to try the following forum for WF questions:
.NET 4: Windows Workflow Foundation:
Hope this helps a bit.