connect to project generates error | object reference not set to an instance of an object

Aug 21, 2012 at 7:44 PM
Edited Aug 21, 2012 at 7:55 PM

When I launch "Test Case Export to Excel" and select connect to tfs... | <add + pick server> | <pick collection> | <pick project> | connect it generates a dialog containing:

Error | Object reference not set to an instance of an object. Application has encountered Fatal Error. Please contact your System Administrator. | [ OK ]

This occurs when I install and run tool on a clean win8x64/vs12 system setup.  This does not occur when I install and run tool on a w08r2x64/vs10sp1 system setup.

Is this an already known issue with a known fix?


Aug 21, 2012 at 9:48 PM
Edited Sep 26, 2012 at 2:29 PM

i'm wondering if this issue is less about the os version and more to do with it requiring the team explorer 2010 bits that are included as part of vs10sp1 ultimate versus being able to use team explorer 2012 bits that are included as part of vs12 ultimate.  thoughts?

Sep 26, 2012 at 7:43 AM

Hello all,

any one has any idea on how to fix this issue. I have no other choice then using this tool. please show a quick solution.

Thanks in advance.

Sep 26, 2012 at 2:31 PM

The fix for me was to run the tool on a system that has vs10sp1 installed as the current release appears to be hard wired to use vs10sp1 provided team explorer 2010 object model and not the vs12 provided team explorer 2012 object model.  

Long term it would be great to get an updated drop that works with vs12 provided team explorer 2012 object model.

Sep 27, 2012 at 2:32 AM

Hi robertob,

Thanks for the quick reply. Is there any other way like editing the config file to use vs12 rather then downgrading to VS10. I think it's not possible to downgrade entire office system to use VS10.

Do you have any idea on when is the next release that is compatible to VS12?


Sep 27, 2012 at 2:40 AM
Edited Sep 27, 2012 at 2:41 AM

i'm not sure it would require someone closely involved with this tool's sources and any current updates in progress to comment on that.   until we get a status update from them it would appear that this tool currently requires vs10 team explorer and excel10 installs to work, e.g. can’t currently use it on system with vs12 team explorer and excel13.