Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't get it to work #1

Closed
OldNo7 opened this issue Jul 7, 2015 · 8 comments
Closed

Can't get it to work #1

OldNo7 opened this issue Jul 7, 2015 · 8 comments

Comments

@OldNo7
Copy link

OldNo7 commented Jul 7, 2015

If I have file open with a View or ViewModel ending (i.e. FooView.xaml, FooViewModel.cs, etc) I get the following error:

The type initializer for 'MvvmTools.Utilities.SettingsUtilities' threw an exception.

When I tried "Tools->Options->MVVM Tools" I get:

An error occurred loading this property page

If I open a file that doesn't have View or ViewModel in the name I get the expected error dialog that says:

Couldn't find any matching view or view model classes

I would love to use this extention. It would be very usefull, If I can get it to work. I'm using Visual Studio 2013 With Caliburn.Micro.

@cbordeman
Copy link
Owner

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
Copy link
Author

OldNo7 commented Jul 17, 2015

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 cbordeman reopened this Jul 17, 2015
@cbordeman
Copy link
Owner

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
Copy link
Author

OldNo7 commented Jul 20, 2015

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
Copy link
Owner

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 cbordeman@outlook.com. I really want this thing to work for you!!

@OldNo7
Copy link
Author

OldNo7 commented Jul 21, 2015

  1. I'm downloading 2015 now.

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

  3. I get the following error
    screenshot

@OldNo7
Copy link
Author

OldNo7 commented Jul 21, 2015

After installing Visual Studio 2015 it now works in VS2013

@cbordeman
Copy link
Owner

Great thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants