mvvmlight icon indicating copy to clipboard operation
mvvmlight copied to clipboard

ViewModel folder and ViewModelLocator missing post nuget install

Open NeilIrvingMacc opened this issue 6 years ago • 10 comments

After creating a new Xamarin Forms 3.0 app in VS2017 I add MVVMLight 5.4.1 via NuGet the ViewModels folder and ViewModelLocator are missing from the project once nugget has completed.

How do I correct this? Is it something I have done or do I need to downgrade my version of MVVMLight?

NeilIrvingMacc avatar Jul 02 '18 10:07 NeilIrvingMacc

I am experiencing the same problem. I am having to copy the ViewModelBase and create the scaffolding manually in order to get started. Please fix.

SunnyMukherjee avatar Jul 06 '18 17:07 SunnyMukherjee

Yes I had to copy from another project

NeilIrvingMacc avatar Jul 09 '18 13:07 NeilIrvingMacc

I am getting this same issue. While following a tutorial I installed the MVVM Light via Nuget Package Manager. It claims everything installed fine, however I have no ViewModel folder nor any scaffolding files... Has anyone figured out a solution or reason for this?

korijHT avatar Sep 27 '18 18:09 korijHT

Same here... :(

sushibear avatar Nov 12 '18 10:11 sushibear

While following a tutorial

@korijHT I'd have liked to see a link to this tutorial as I struggle to implement a Locator pattern in my own learning app...

jhalbrecht avatar Nov 17 '18 22:11 jhalbrecht

I'm trying to use MVVMLight in a Xamarin.Forms app using VS Community 2017 for Mac, having this same issue. The package installs with no errors, but it doesn't create the directories and classes needed. The package doesn't even show up when adding a 'using' unless I add the MVVMLightLibs NuGet as well. Maybe I'll try creating the scaffolding manually, hope that works, I was looking forward to using this.

dan461 avatar Nov 22 '18 18:11 dan461

I had the same issue a few months ago when starting to use MVVMLight with a Xamarin Forms app. I too thought I would have to create the scaffolding manually. You’ll see my original comment above. I don’t think they’ve fixed the issue since then. Then I found FreshMVVM. It works beautifully and it’s easy to use. It was made for Xamarin Forms. Check it out.

SunnyMukherjee avatar Nov 22 '18 18:11 SunnyMukherjee

Any update on this? I am having this issue.

greektreat avatar Apr 04 '19 16:04 greektreat

I am also having this issue in VS 2019 (version 16.3.9) with MvvmLight v5.4.1.1

jwhitake avatar Nov 20 '19 04:11 jwhitake

Still facing this issue in VS 2019 (version 16.3.9) and with MVVMLightLibsStd10 for.NET Standard v2 and XF v4.2 last stable release

AshishMantosh avatar Dec 07 '19 07:12 AshishMantosh