Enable NCrunch grayed out in fresh VS 11 beta install

Info:

Fresh install of VS11 Premium on Win7 Pro 64-bit.

Symptoms:

NCrunch menu item exists, but "Enable NCrunch" menu item is grayed out.

Any help is appreciated!

-Cork

I am experiencing the same issue with VS 2011 Beta.

I am on Windows 7 Enterprise 64bit and VS 2011 Beta Ultimate using NCrunch version 1.38.17b.

Based on this forum topic "Unable to enable NCrunch for new install", I made sure that all ncrunch files in the solution were writable. Then re-opened VS2011 Beta. This did not fix the issue.

Please let me know if there is any more information that I can provide to help troubleshoot this issue.

This tool is wonderful and look forward to using it with VS2011 Beta.

jhamm wrote:I am experiencing the same issue with VS 2011 Beta.

I am on Windows 7 Enterprise 64bit and VS 2011 Beta Ultimate using NCrunch version 1.38.17b.

Based on this forum topic "Unable to enable NCrunch for new install", I made sure that all ncrunch files in the solution were writable. Then re-opened VS2011 Beta. This did not fix the issue.

Please let me know if there is any more information that I can provide to help troubleshoot this issue.

This tool is wonderful and look forward to using it with VS2011 Beta.

I'm having the same issue. Just one more information, on configuration, it only shows "All Solutions". No solution or project node is shown, like the solution has not been loaded.

Thanks in advance

This seems to be caused by Visual Studio events that aren't firing consistently. I'm wondering if anyone experiencing this problem can answer the following for me in order to help me reproduce this problem:

* Does this problem occur if you open Visual Studio 11 directly onto a solution file (i.e. if you double-click a VS11 solution file in windows explorer)?
* Does this problem occur if you open Visual Studio 11 without a solution, then open it via the menu?
* If the problem has occurred for you, what happens if you close the solution using the File menu, then re-open it?
* If the problem has occurred for you, what happens if you switch to a different solution (using the File menu) without closing the one currently open?

* Does this problem occur if you open Visual Studio 11 directly onto a solution file (i.e. if you double-click a VS11 solution file in windows explorer)?
NCrunch is now enabled.
* Does this problem occur if you open Visual Studio 11 without a solution, then open it via the menu?
Still happens.
* If the problem has occurred for you, what happens if you close the solution using the File menu, then re-open it?
Still happens.
* If the problem has occurred for you, what happens if you switch to a different solution (using the File menu) without closing the one currently open?
NCrunch is now enabled.

* Does this problem occur if you open Visual Studio 11 without a solution, then open it via Start Page -> Recent Used?
Still happens.


Thanks for responding so quickly!

* Does this problem occur if you open Visual Studio 11 directly onto a solution file (i.e. if you double-click a VS11 solution file in windows explorer)?
No...and this is my workaround for now :)

* Does this problem occur if you open Visual Studio 11 without a solution, then open it via the menu?
Yes.

* If the problem has occurred for you, what happens if you close the solution using the File menu, then re-open it?
The problem remains.

* If the problem has occurred for you, what happens if you switch to a different solution (using the File menu) without closing the one currently open?
The new solution allowed me to enable NCrunch...once.

Thanks guys. From your feedback, I've been able to reproduce this problem and I am now working on a fix. I will keep you updated.

Ok - I've implemented a fix for this issue and deployed a new revision of 1.38b (1.38.0.18) to the download page for everyone to grab.

The problem itself is caused by abnormal behaviour in some of the VS events that NCrunch relies on around solution opening/closing. Because it looks as though this behaviour is not by design in VS, the fix I've implemented is quite speculative and I hope you'll be able to share some feedback on whether it has worked for you.

Thanks!

Remco

Remco wrote:Ok - I've implemented a fix for this issue and deployed a new revision of 1.38b (1.38.0.18) to the download page for everyone to grab.

The problem itself is caused by abnormal behaviour in some of the VS events that NCrunch relies on around solution opening/closing. Because it looks as though this behaviour is not by design in VS, the fix I've implemented is quite speculative and I hope you'll be able to share some feedback on whether it has worked for you.

Thanks!

Remco

Thanks! it works!

This fix also works for me!

Thanks!

Works for me either.

Thanks