Hi Frederico and thanks for the reply. Actually you are right but the circumstances are odd.
I'm using VS 2010 at work to create an application using Prism. The Prism templates dont work on VS 2012 so i'm sticking with that for the moment.
I used VS 2012's version of Blend to create an animation and when I copy pasted the XAML into my VS 2010 project the project utterly died in the manner shown above. Worse than that, even when I remove the offending module and try to recompile, it seems that something has changed in the project such that this reference is fixed and will not go away. This means that the project will never run again without essentially being reconstructed from scratch. (new project and import all the files)
One big problem is that my employer insists on using VB which is not at all my cup of tea and the way it manages its references are not as evident as for a C# project.
Right now I have decided not to use Blend 2012 in the project.
Bob Powell.
I'm using VS 2010 at work to create an application using Prism. The Prism templates dont work on VS 2012 so i'm sticking with that for the moment.
I used VS 2012's version of Blend to create an animation and when I copy pasted the XAML into my VS 2010 project the project utterly died in the manner shown above. Worse than that, even when I remove the offending module and try to recompile, it seems that something has changed in the project such that this reference is fixed and will not go away. This means that the project will never run again without essentially being reconstructed from scratch. (new project and import all the files)
One big problem is that my employer insists on using VB which is not at all my cup of tea and the way it manages its references are not as evident as for a C# project.
Right now I have decided not to use Blend 2012 in the project.
Bob Powell.