Can't get it to work

[cbordeman]

Can't get it to work

[cbordeman]

I know if you install the VS2015 RC it will work (in 2013). I'm currently targeting all the way back to 2010, which may be not be worth it due to confusion around dependencies.

I'll issue an update in a few days to correct the dependencies.

[OldNo7]

I tried installing 4.6 from here:
https://msdn.microsoft.com/en-us/library/w0x726c2(v=VS.110).aspx
Still doesn't work. I'll try the VS2015 RC when I get a chance.

[cbordeman]

OldNo7, I'm issuing an update soon so you can configure the suffixes for the views and view models. For example, if you use SamplePresentationModel for the view model within one project or several, you can configure that. Also, you can configure the list of recognized view suffixes.

If your view models or views aren't named with a special suffix at all, the extension has no way of telling them apart from regular classes. And I'd rather not resort to looking for particular inheritance as property notification can be done many ways.

[OldNo7]

My views and view models are in the same project and same namespace. They are named using the default convention used by Caliburn.micro.

AppView.xaml 
AppViewModel.cs

They are both in the same directory although I've also tried having them in separate directories ("Views" and "ViewModels")

[cbordeman]

Please answer these questions:

1. have you installed VS2015 RC yet?
   2 Are you able to access the Options page yet? If that doesn't open maybe the plugin won't work at all.
2. From the view model, press the Ctrl+E, Ctrl+V. What exactly happens?

I've tested your scenario and it worked (on my computer (famous lasts), so if you can see options, is there a chance you could put your project up on One Drive or DropBox and post a link? If necessary, encrypt it and email me the password through github or [email protected]. I really want this thing to work for you!!

[OldNo7]

1. I'm downloading 2015 now.

2. No I can't access Options. I get this error:
   

3. I get the following error
   

[OldNo7]

After installing Visual Studio 2015 it now works in VS2013

[cbordeman]

Great thanks.