Greg
Have you looked at the Registry on both (32-bit/64-bit), under Visual Studio
DataProviders? It may be a quicker comparison.
I have only VS2010 installed, the key being
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0_Config\DataProviders
] -
_
Ian Thomas
Victoria Park,
Hope it helps.
My standard debugging technique is to now always check any and all logs I
know about just in case something somewhere has recorded a little titbit of
info that could be relevant.
You'd be surprised what windows logs
On 20 May 2013 13:14, Greg Keogh wrote:
> Did check the fusion
>
> Did check the fusion log to see what was being probed for?
Ah! fuslogvw ... Good idea, I'll try it tonight when I get home -- Greg
Did check the fusion log to see what was being probed for?
On 20 May 2013 11:09, Greg Keogh wrote:
> I copied EVERY dll referenced by the project over to the test machine and
> it still fails. I was suspicious that the test machine it did work on had
> Visual Studio 2012 installed on it, so I un
I copied EVERY dll referenced by the project over to the test machine and
it still fails. I was suspicious that the test machine it did work on had
Visual Studio 2012 installed on it, so I uninstalled VS2012 and all other
development tools (it's an old spare VM) and now it crashes there as well.
So