Currently I am looking at LinqToExcel as a technology to be able to read Excel workbooks as a data source for test cases to be run as post build task. For each test case, the Excel workbooks will be copied into a separate output directory per test case run.
Could anyone please provide further detail on how LinqToExcel handles concurrent processes trying access the Excel workbook file.
What type of locking will be used while the file is being accessed?
I have not yet examined the source myself, however thought I would ask on this forum for Github.
This is a concern especially noting that it will be used as part of a process run as a post build task.
LinqToExcel uses OleDb to read data from the spreadsheets, so you'll want to research how OleDb handles concurrent processes. I don't know off the top of my head.
Hi all,
Currently I am looking at LinqToExcel as a technology to be able to read Excel workbooks as a data source for test cases to be run as post build task. For each test case, the Excel workbooks will be copied into a separate output directory per test case run.
Could anyone please provide further detail on how LinqToExcel handles concurrent processes trying access the Excel workbook file. What type of locking will be used while the file is being accessed?
I have not yet examined the source myself, however thought I would ask on this forum for Github. This is a concern especially noting that it will be used as part of a process run as a post build task.
Kind regards,
Marcus