search

jbarker7 / sqlcc

SQL Code Coverage - SQLCC is a code coverage tool that allows developers the ability to track which lines of code within stored procedures, functions, and triggers have been tested in SQL server by integration tests written by the developer.
BSD 4-Clause "Original" or "Old" License
26 stars 22 forks source link

Constructor on type 'SQLCC.Impl.MsSqlProvider.MsSqlProvider' not found. #3

Closed ghostsquad closed 9 years ago

ghostsquad commented 11 years ago

Constructor on type 'SQLCC.Impl.MsSqlProvider.MsSqlProvider' not found.

AssemblyLoader.cs: Line 68

here's the line that the exception occurs on: return (T)Activator.CreateInstance(type, args);

it's because args = object[0] and there is no constructor for MsSqlProvider that accepts that as input.

debugging GetNamedArgumentArray shows something interesting happen on line 84:

if (providedSignature != orderedParams) continue;

Here's the local variables being compared: orderedParams "dbp.applicationName,dbp.connString,dbp.traceDir" string providedSignature "dbp.applicationName,dbp.connString,dbp.traceDir,dbp.traceName" string

there are no other constructors, so the foreach ends, so then the last line of the method is:

return new object[0];

This error occurs when the config file is edited (per instructions from issue: KeyNotFoundException) (config addition below)

<add key="dbp.traceName" value="TraceFile" />

I've removed the above line from the config file, and added --app.traceName to the arguments when running the EXE and all seems well. Looks like we need an update to support dbp.traceName in the config file.

jbarker7 commented 11 years ago

Please try now-- I have made a few fixes and optimizations. The biggest issue was one of our collaborators actually committed a change that required traceName as a parameter-- I changed this to optional to keep things simple.

jbarker7 commented 9 years ago

Closed due to no response