VS 2010's WF4.0 project caused an error after installing VS 11 beta

Question

After I installed VS 11 beta, when I click the Final state on the state machine design surface of VS 2010's WF4.0 project,it caused an error InvalidOperationException:The specified Visual is not an ancestor of this Visual. But the project can be compiled and running normally.

How should I approach the issue and solve it？I wouldn't want to uninstall VS 11.

New update:I have already uninstalled vs 11,but this has no effect.

Answer 1

Hi,

You can try disable Visual Studio extensions to see it helps.

http://msdn.microsoft.com/en-us/library/dd293640.aspx

Also, make sure the target .Net Framework version is 4.0.

---

Leo Tang [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 2

Hi Justin,
Which product updates did you have installed previously to VS11 beta? Which project was your project targeting 4.0.1? 4.0.3?

Do you encounter the issue only in VS 2010, and not in VS11?

Do you encounter the same issue with a newly created state machine in a new project, or only with your existing project? Is there a nice short repro step sequence starting from a fresh solution?

I'm also interested in the uninstalling of VS11 having no effect. Perhaps it is a bug in setup. If you debug Visual Studio 2010, and can add file path + version information on the loaded CLR modules that might make some issue visible. (Also if you are going the debugging route, you can probably add a stack trace for the exception if you disable just my code, and enable debugging .net framework code.)
Tim

Answer 3

Hi Justin,
Which product updates did you have installed previously to VS11 beta? Which project was your project targeting 4.0.1? 4.0.3?

Do you encounter the issue only in VS 2010, and not in VS11?

Do you encounter the same issue with a newly created state machine in a new project, or only with your existing project? Is there a nice short repro step sequence starting from a fresh solution?

I'm also interested in the uninstalling of VS11 having no effect. Perhaps it is a bug in setup. If you debug Visual Studio 2010, and can add file path + version information on the loaded CLR modules that might make some issue visible. (Also if you are going the debugging route, you can probably add a stack trace for the exception if you disable just my code, and enable debugging .net framework code.)
Tim

Hi Tim,

Thanks for your answer.

I solved this problem by uninstalling vs 11 and re-installing vs2010.

It's my oversight.My wf4.0's framework version is 4,not 4.0.1 & 4.0.3 ,and my State Machine is the CTP version.

In another computer,I Patched my .net framework(KB2478063),and the wf4 project can upgrade 4.5 normally.