Problem installing TD .net

[mynkow]

Hi,

I have vs2008 and vs2010 installed on my machine. When I install
TD .net 3 the application is available for vs2008 but not for vs2010.
What can I do?

Thanks

[Jamie Cansdale]

Could you check the 'Add-in Manager' in VS 2010 and see if
TestDriven.Net is visible there?

Regards,
Jamie.

--
http://www.testdriven.net
http://twitter.com/jcansdale
http://weblogs.asp.net/nunitaddin

> --
> You received this message because you are subscribed to the Google Groups "TestDriven.NET Users" group.
> To post to this group, send email to testdri...@googlegroups.com.
> To unsubscribe from this group, send email to testdrivenuse...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/testdrivenusers?hl=en.
>
>

[mynkow]

It is not there, I also tried to install it manually but I failed.

On Jun 15, 4:48 pm, Jamie Cansdale <jcansd...@gmail.com> wrote:
> Could you check the 'Add-in Manager' in VS 2010 and see if
> TestDriven.Net is visible there?
>
> Regards,
> Jamie.
>

> --http://www.testdriven.nethttp://twitter.com/jcansdalehttp://weblogs.asp.net/nunitaddin

[Jamie Cansdale]

Could you check that the following file exists:

C:\Program Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn
(or if you're using a 32-bit OS)
C:\Program Files\TestDriven.NET 3\TestDriven2010.AddIn

and there is an entry called:
"C:\Program Files (x86)\TestDriven.NET 3\"

at the following registry key:
HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\AutomationOptions\LookInFolders
(or if you're using a 32-bit OS)
HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\AutomationOptions\LookInFolders

Regards,
Jamie.

--
http://www.testdriven.net
http://twitter.com/jcansdale

http://weblogs.asp.net/nunitaddin

[mynkow]

It is not there. I also tried to install it manually but I failed.

On Jun 15, 4:48 pm, Jamie Cansdale <jcansd...@gmail.com> wrote:

> Could you check the 'Add-in Manager' in VS 2010 and see if
> TestDriven.Net is visible there?
>
> Regards,
> Jamie.
>

> --http://www.testdriven.nethttp://twitter.com/jcansdalehttp://weblogs.asp.net/nunitaddin

[mynkow]

Double post, sorry.

All files and registry keys are online.

The registry key contains C:\Program Files (x86)\TestDriven.NET 3\
where the td.net is actually installed.

On Jun 15, 5:03 pm, Jamie Cansdale <jcansd...@gmail.com> wrote:
> Could you check that the following file exists:
>
> C:\Program Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn
> (or if you're using a 32-bit OS)
> C:\Program Files\TestDriven.NET 3\TestDriven2010.AddIn
>
> and there is an entry called:
> "C:\Program Files (x86)\TestDriven.NET 3\"
>
> at the following registry key:
> HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\AutomationOptions\LookInFolders
> (or if you're using a 32-bit OS)
> HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\AutomationOptions\LookInFolders
>
> Regards,
> Jamie.
>

> --http://www.testdriven.nethttp://twitter.com/jcansdalehttp://weblogs.asp.net/nunitaddin
>
> On Tue, Jun 15, 2010 at 2:58 PM, mynkow <myn...@gmail.com> wrote:
> > It is not there, I also tried to install it manually but I failed.
>
> > On Jun 15, 4:48 pm, Jamie Cansdale <jcansd...@gmail.com> wrote:
> >> Could you check the 'Add-in Manager' in VS 2010 and see if
> >> TestDriven.Net is visible there?
>
> >> Regards,
> >> Jamie.
>

> >> --http://www.testdriven.nethttp://twitter.com/jcansdalehttp://weblogs.a...

[mynkow]

I also tried this http://social.msdn.microsoft.com/Forums/en/vssetup/thread/84f86998-ede1-4582-860e-7270fa8e1e77
... still no luck

On Jun 15, 5:06 pm, mynkow <myn...@gmail.com> wrote:
> Double post, sorry.
>
> All files and registry keys are online.
>
> The registry key contains C:\Program Files (x86)\TestDriven.NET 3\
> where the td.net is actually installed.
>
> On Jun 15, 5:03 pm, Jamie Cansdale <jcansd...@gmail.com> wrote:
>
> > Could you check that the following file exists:
>
> > C:\Program Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn
> > (or if you're using a 32-bit OS)
> > C:\Program Files\TestDriven.NET 3\TestDriven2010.AddIn
>
> > and there is an entry called:
> > "C:\Program Files (x86)\TestDriven.NET 3\"
>
> > at the following registry key:
> > HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\AutomationOptions\LookInFolders
> > (or if you're using a 32-bit OS)
> > HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\AutomationOptions\LookInFolders
>
> > Regards,
> > Jamie.
>

[Jamie Cansdale]

Are you familiar with Sysinternals Process Monitor?
http://technet.microsoft.com/en-gb/sysinternals/bb896645.aspx

I'd like to check that 'TestDriven2010.AddIn' is actually being read
when VS 2010 starts.

If you add a filter for 'Path' > 'ends with' > 'TestDriven2010.AddIn'
then 'Include'.

You should see the following (plus a load more) when VS 2010 starts:

devenv.exe C:\Program Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn SUCCESS

devenv.exe RegQueryValue HKCU\Software\Microsoft\VisualStudio\10.0\PreloadAddinStateManaged\TestDriven.NET;C:\Program
Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn SUCCESS

BTW, do you have any other add-ins loaded? I'd be interested to know
if GhostDoc works on your VS 2010:
http://submain.com/products/ghostdoc.aspx

Regards,
Jamie.

--
http://www.testdriven.net
http://twitter.com/jcansdale

http://weblogs.asp.net/nunitaddin

[mynkow]

Hi,

there are no other addins installed.

I have all success except for this one:

Operation: QueryOpen
Result: FAST IO DISALLOWED
Path: C:\Program Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn

and the stack:

"Frame","Module","Location","Address","Path"
"0","fltmgr.sys","fltmgr.sys + 0x2027","0xfffff88000e40027","C:\Windows
\system32\drivers\fltmgr.sys"
"1","fltmgr.sys","fltmgr.sys + 0x4b9d","0xfffff88000e42b9d","C:\Windows
\system32\drivers\fltmgr.sys"
"2","fltmgr.sys","fltmgr.sys + 0x22a5f","0xfffff88000e60a5f","C:
\Windows\system32\drivers\fltmgr.sys"
"3","ntoskrnl.exe","ntoskrnl.exe + 0x374ca7","0xfffff80002bc3ca7","C:
\Windows\system32\ntoskrnl.exe"
"4","ntoskrnl.exe","ntoskrnl.exe + 0x36aa64","0xfffff80002bb9a64","C:
\Windows\system32\ntoskrnl.exe"
"5","ntoskrnl.exe","ntoskrnl.exe + 0x36fb76","0xfffff80002bbeb76","C:
\Windows\system32\ntoskrnl.exe"
"6","ntoskrnl.exe","ntoskrnl.exe + 0x3551ca","0xfffff80002ba41ca","C:
\Windows\system32\ntoskrnl.exe"
"7","ntoskrnl.exe","ntoskrnl.exe + 0x6f853","0xfffff800028be853","C:
\Windows\system32\ntoskrnl.exe"
"8","ntdll.dll","ntdll.dll + 0x5028a","0x76db028a","C:\Windows
\SYSTEM32\ntdll.dll"
"9","wow64.dll","wow64.dll + 0x1abfd","0x744aabfd","C:\Windows
\SYSTEM32\wow64.dll"
"10","wow64.dll","wow64.dll + 0xcf87","0x7449cf87","C:\Windows
\SYSTEM32\wow64.dll"
"11","wow64cpu.dll","wow64cpu.dll + 0x276d","0x7442276d","C:\Windows
\SYSTEM32\wow64cpu.dll"
"12","wow64.dll","wow64.dll + 0xd07e","0x7449d07e","C:\Windows
\SYSTEM32\wow64.dll"
"13","wow64.dll","wow64.dll + 0xc549","0x7449c549","C:\Windows
\SYSTEM32\wow64.dll"
"14","ntdll.dll","ntdll.dll + 0x484c8","0x76da84c8","C:\Windows
\SYSTEM32\ntdll.dll"
"15","ntdll.dll","ntdll.dll + 0x47623","0x76da7623","C:\Windows
\SYSTEM32\ntdll.dll"
"16","ntdll.dll","ntdll.dll + 0x3308e","0x76d9308e","C:\Windows
\SYSTEM32\ntdll.dll"
"17","ntdll.dll","ntdll.dll + 0x1fe0e","0x76f5fe0e","C:\Windows
\SysWOW64\ntdll.dll"
"18","KERNELBASE.dll","KERNELBASE.dll + 0x18b61","0x74d58b61","C:
\Windows\syswow64\KERNELBASE.dll"
"19","msenv.dll","DllUnregisterServer + 0x10f57c","0x6e5f56dd","C:
\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
\msenv.dll"
"20","msenv.dll","DllUnregisterServer + 0x58b11","0x6e53ec72","C:
\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
\msenv.dll"
"21","msenv.dll","DllUnregisterServer + 0x58678","0x6e53e7d9","C:
\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
\msenv.dll"
"22","msenv.dll","DllUnregisterServer + 0x53852","0x6e5399b3","C:
\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
\msenv.dll"
"23","msenv.dll","DllCanUnloadNow + 0x2a563","0x6e418106","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"24","msenv.dll","DllCanUnloadNow + 0x2a527","0x6e4180ca","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"25","msenv.dll","DllCanUnloadNow + 0x2a34b","0x6e417eee","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"26","msenv.dll","DllMain + 0x206ae","0x6e2e5cf4","C:\Program Files
(x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"27","msenv.dll","DllCanUnloadNow + 0x57df","0x6e3f3382","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"28","msenv.dll","DllCanUnloadNow + 0x5896","0x6e3f3439","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"29","msenv.dll","DllCanUnloadNow + 0x5936","0x6e3f34d9","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"30","msenv.dll","DllMain + 0x2328f","0x6e2e88d5","C:\Program Files
(x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"31","msenv.dll","DllMain + 0x237f9","0x6e2e8e3f","C:\Program Files
(x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"32","msenv.dll","DllCanUnloadNow + 0x5182","0x6e3f2d25","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"33","msenv.dll","VStudioMain + 0x78","0x6e30db92","C:\Program Files
(x86)\Microsoft Visual Studio 10.0\Common7\IDE\msenv.dll"
"34","devenv.exe","devenv.exe + 0x7435","0x2f997435","C:\Program Files
(x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe"
"35","devenv.exe","devenv.exe + 0x10445","0x2f9a0445","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe"
"36","devenv.exe","devenv.exe + 0x1167c","0x2f9a167c","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe"
"37","devenv.exe","devenv.exe + 0x116ec","0x2f9a16ec","C:\Program
Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe"
"38","kernel32.dll","kernel32.dll + 0x13677","0x76953677","C:\Windows
\syswow64\kernel32.dll"
"39","ntdll.dll","ntdll.dll + 0x39d72","0x76f79d72","C:\Windows
\SysWOW64\ntdll.dll"
"40","ntdll.dll","ntdll.dll + 0x39d45","0x76f79d45","C:\Windows
\SysWOW64\ntdll.dll"

On Jun 15, 5:25 pm, Jamie Cansdale <jcansd...@gmail.com> wrote:
> Are you familiar with Sysinternals Process Monitor?http://technet.microsoft.com/en-gb/sysinternals/bb896645.aspx

>
> I'd like to check that 'TestDriven2010.AddIn' is actually being read
> when VS 2010 starts.
>
> If you add a filter for 'Path' > 'ends with' > 'TestDriven2010.AddIn'
> then 'Include'.
>
> You should see the following (plus a load more) when VS 2010 starts:
>
> devenv.exe C:\Program Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn SUCCESS
>
> devenv.exe RegQueryValue        HKCU\Software\Microsoft\VisualStudio\10.0\PreloadAddinStateManaged\TestDriven.NET;C:\Program
> Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn SUCCESS
>
> BTW, do you have any other add-ins loaded? I'd be interested to know
> if GhostDoc works on your VS  2010:http://submain.com/products/ghostdoc.aspx
>
> Regards,
> Jamie.
>

> --http://www.testdriven.nethttp://twitter.com/jcansdalehttp://weblogs.asp.net/nunitaddin
>
> On Tue, Jun 15, 2010 at 3:06 PM, mynkow <myn...@gmail.com> wrote:
> > Double post, sorry.
>
> > All files and registry keys are online.
>
> > The registry key contains C:\Program Files (x86)\TestDriven.NET 3\
> > where the td.net is actually installed.
>
> > On Jun 15, 5:03 pm, Jamie Cansdale <jcansd...@gmail.com> wrote:
> >> Could you check that the following file exists:
>
> >> C:\Program Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn
> >> (or if you're using a 32-bit OS)
> >> C:\Program Files\TestDriven.NET 3\TestDriven2010.AddIn
>
> >> and there is an entry called:
> >> "C:\Program Files (x86)\TestDriven.NET 3\"
>
> >> at the following registry key:
> >> HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\AutomationOptions\LookInFolders
> >> (or if you're using a 32-bit OS)
> >> HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\AutomationOptions\LookInFolders
>
> >> Regards,
> >> Jamie.
>

[Jamie Cansdale]

> I have all success except for this one:
>
> Operation: QueryOpen
> Result: FAST IO DISALLOWED
> Path: C:\Program Files (x86)\TestDriven.NET 3\TestDriven2010.AddIn
>

I get the same on my machine when it loaded okay.

Could you try launching VS2010 with Sysinternals DebugView open. If
you could send me the log, maybe there will be a clue in there.

Regards,
Jamie.

--
http://www.testdriven.net
http://twitter.com/jcansdale

http://weblogs.asp.net/nunitaddin