mvvmlight Discussions Rss Feed

New Post: Could not load type 'INotifyPropertyChanging' error in VS 2012 Premium with MvvmLight 4.1.24.0

Familyghost — Sun, 19 May 2013 18:13:41 GMT

Sure thing Laurent, see attached.

I find I have to compile and run in more than once to see the error in the designer window.

Maybe you can tell me why my listbox data isn’t binding. I’m out of ideas.

Thanks,

Chris

New Post: Could not load type 'INotifyPropertyChanging' error in VS 2012 Premium with MvvmLight 4.1.24.0

lbugnion — Sun, 19 May 2013 13:21:36 GMT

Hi,

I don’t see the error. I tried adding mvvmlight through Nuget in a Windows Phone 7.1 and in a Windows Phone 8 app and both times I was able to wire the VM, add a property, and see everything in the VS designer.

Can you send me the app you did, including the packages folder with the downloaded DLLs?

Thanks

Laurent

New Post: Could not load type 'INotifyPropertyChanging' error in VS 2012 Premium with MvvmLight 4.1.24.0

lbugnion — Fri, 17 May 2013 17:54:06 GMT

I'll check it out.

Cheers
Laurent
--
Laurent Bugnion
Senior Director, IdentityMine
Microsoft Regional Director and MVP
http://www.galasoft.ch | http://www.identitymine.com
Sent from my beautiful Nokia Lumia 920

From: [email removed]
Sent: ‎17.‎05.‎2013 18:20
To: [email removed]
Subject: Re: Could not load type 'INotifyPropertyChanging' error in VS 2012Premium with MvvmLight 4.1.24.0 [mvvmlight:401430]

From: Familyghost

This is update 2, VS 11.0.60315.01

.NET framework 1.5.50709

Sent from Windows Mail

From: lbugnion
Sent: ‎Friday‎, ‎May‎ ‎17‎, ‎2013 ‎11‎:‎16‎ ‎AM
To: [email removed]

From: lbugnion

Hi,

You need to make sure that you are using the latest version of VS (update 2).

The VS designer *is* Blend so you are in fact using it ;)

Cheers
Laurent
--
Laurent Bugnion
Senior Director, IdentityMine
Microsoft Regional Director and MVP
http://www.galasoft.ch | http://www.identitymine.com
Sent from my beautiful Nokia Lumia 920

From: [email removed]
Sent: ‎17.‎05.‎2013 17:56
To: [email removed]
Subject: Re: Could not load type 'INotifyPropertyChanging' error in VS 2012Premium with MvvmLight 4.1.24.0 [mvvmlight:401430]

From: Familyghost

Laurent,

From the thread it sounds like this problem had been patched up by now. I installed MMVM light via nuget a few days ago, For instance System.Windows.Interactivity Verion 3.8.5.0 and still get this error.

I don't use blend. It shows up in the Designer in VS2012 Express for WP

Anything we can do?

Thanks

New Post: Could not load type 'INotifyPropertyChanging' error in VS 2012 Premium with MvvmLight 4.1.24.0

Familyghost — Fri, 17 May 2013 16:20:06 GMT

This is update 2, VS 11.0.60315.01

.NET framework 1.5.50709

Sent from Windows Mail

From: lbugnion
Sent: ‎Friday‎, ‎May‎ ‎17‎, ‎2013 ‎11‎:‎16‎ ‎AM
To: [email removed]

From: lbugnion

From: [email removed]
Sent: ‎17.‎05.‎2013 17:56
To: [email removed]
Subject: Re: Could not load type 'INotifyPropertyChanging' error in VS 2012Premium with MvvmLight 4.1.24.0 [mvvmlight:401430]

From: Familyghost

New Post: Could not load type 'INotifyPropertyChanging' error in VS 2012 Premium with MvvmLight 4.1.24.0

lbugnion — Fri, 17 May 2013 16:16:36 GMT

From: [email removed]
Sent: ‎17.‎05.‎2013 17:56
To: [email removed]
Subject: Re: Could not load type 'INotifyPropertyChanging' error in VS 2012Premium with MvvmLight 4.1.24.0 [mvvmlight:401430]

From: Familyghost

New Post: Could not load type 'INotifyPropertyChanging' error in VS 2012 Premium with MvvmLight 4.1.24.0

Familyghost — Fri, 17 May 2013 15:55:18 GMT

New Post: PCL viewModel Win8/phone services async

roschler — Thu, 16 May 2013 18:14:01 GMT

@jhalbrecht - I ran into the same problem with "cannot await" errors. It's some odd incompatibility between Assembly versions. I found this cryptic NuGet issue resolution page on the subject:

http://blogs.msdn.com/b/bclteam/p/asynctargetingpackkb.aspx

I wish they had explained what the problem was and why the fix works, but the fix does work. Here's what they say:

Issue 2

Symptom

After installing the Microsoft.Bcl or Microsoft.Bcl.Async packages to certain projects, you may get build errors or warnings similar to:

Cannot await 'System.Threading.Tasks.Task'.

or

The primary reference "Microsoft.Threading.Tasks" could not be resolved because it has an indirect dependency on the framework assembly "System.Runtime, Version=1.5.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.0". To resolve this problem, either remove the reference "Microsoft.Threading.Tasks" or retarget your application to a framework version which contains "System.Runtime, Version=1.5.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".

Resolution

Microsoft.Bcl.Async package is not supported in Visual Basic Web Application projects. As a workaround, place all async/await usage in a class library and consume that from the Web Application project.

Otherwise, for other project types add an App.Config to the project with the following contents, replacing [version] with the version (for example, 2.5.10.0) of System.Runtime and System.Threading.Tasks that you are referencing:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<runtime>

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-[version]" newVersion="[version]" />
  </dependentAssembly>
  <dependentAssembly>
    <assemblyIdentity name="System.Threading.Tasks" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-[version]" newVersion="[version]" />
  </dependentAssembly>
</assemblyBinding>

</runtime>
</configuration>

Make sure you capitalize the first word in App.Config. In my case the DLLs I were using were 1.5.11.0 and replacing "version" (no quotes) with that value did the trick. Just check the version number of your System.Runtime and System.Threading.Tasks in the properties window. You'll see it in the path to the DLL(s).

-- roschler

New Post: CanExecute not updating UI when called from background thread

pipjt — Thu, 09 May 2013 19:07:29 GMT

OK, so I have figured out a work around.

Fortunately, the condition on my background thread that I am using to determine the CanExecute state, has an associated event.

I hooked into the event on my ViewModel using a lamda expression for each instance of the object in question, and used the dispatcher helper to call the RaiseCanExecuteChanged on the UI thread for each associated command.

DispatcherHelper.CheckBeginInvokeOnUI(() => { [MyCommand].RaiseCanExecuteChanged(); });

In future, if an event is not available I will consider using the Messenger.

This works but feels a little convoluted; is there a better way of doing this?

Many Thanks

Phil

New Post: Product: MVVM Light Toolkit -- Error 1721. There is a problem with this Windows Installer package

i00b — Thu, 09 May 2013 04:12:35 GMT

I get the following error message (from the event log) when attempting to install GalaSoft.MvvmLight.4.1.24.0.msi:

Product: MVVM Light Toolkit -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: PostSetupActionVS10Machine, location: D:\, command: C:\Users\MYUSERNAME\AppData\Roaming\MvvmLight\ModifyRegistryKey.exe -i10m "C:\Program Files (x86)\Laurent Bugnion (GalaSoft)\Mvvm Light Toolkit\Snippets\CSharp\

A similar error has been reported before (see https://mvvmlight.codeplex.com/discussions/274919). Does this installation package need to be updated (as mentioned in the referenced post) or is there a work around solution?

Thanks,

Ian

New Post: CanExecute not updating UI when called from background thread

pipjt — Tue, 07 May 2013 16:20:08 GMT

Hi Laurent

I appologies if this has been asked before.

I am having an issue with my WPF application (using MVVM Light), where the CanExecute element of the RelayCommand is not updating my UI; this is appears to be becuse it is being updated from a background thread.

Is this something that can be overcome using the DispatcherHelper, if so how?

Many Thanks

Phil

New Post: Issue with EventToCommand in VS2012 (Update2)

tazzer — Tue, 07 May 2013 09:35:26 GMT

Any ideas on this one?

New Post: How to use DispatcherHelper with ProgressBar and BackgroundWorker

tropet — Thu, 02 May 2013 16:43:38 GMT

How can I use Dispatcher Helper with Progress Bar in Mvvm. I'm accessing Ui Element defined in my viewmodel and I think dispatcherhelper will solved this, but it seems the progressbar was not updated when I ran the Backgroundworker with DispatcherHelper. Please help:

here's my code :

_worker = new BackgroundWorker() {

        WorkerReportsProgress = true,
        WorkerSupportsCancellation = true
    };


    _grid = new Grid();
    _worker.DoWork += (sender,e) => DispatcherHelper.UIDispatcher.Invoke(() => {
        try{
            var vWorker = (BackgroundWorker) sender;

            ReportColumns = new List<ReportColumn>();
            #region Set Report Item Column
            for(var i = 1;i <= _reportBal.ReportItemContent.Columns.Count - 1;i++) {
                var vColumnsItems = ReportParser.ParseColumnAttributes(_reportBal.ReportItemContent.Columns[i].ColumnName);
                var vColumn = new ReportColumn();
                vColumn.DataType = vColumnsItems[0];
                vColumn.Width = vColumnsItems[1];
                vColumn.Header = vColumnsItems[2];
                vColumn.DataField = vColumnsItems[2];
                ReportColumns.Add(vColumn);
            }

            if(ReportColumns != null) {
                for(int ctrCol = 0;ctrCol <= ReportColumns.Count - 1;ctrCol++) {
                    var sp = new StackPanel { Orientation = Orientation.Horizontal };
                    _grid.ColumnDefinitions.Add(new ColumnDefinition {
                        Width =
                            new GridLength(Convert.ToDouble(ReportColumns[ctrCol].Width))
                    });
                    var tb = new TextBlock {
                        Text = ReportColumns[ctrCol].DataField,
                        FontWeight = FontWeights.DemiBold,
                        Margin = new Thickness(8,0,8,0),
                        TextWrapping = TextWrapping.Wrap
                    };
                    sp.Children.Add(tb);
                    Grid.SetRow(sp,0);
                    Grid.SetColumn(sp,ctrCol);
                    _grid.Children.Add(sp);
                }
            }

            #endregion

_recordCount = _reportBal.ReportItemContent.Rows.Count;

            #region Set Report Item Row
            GridHelper.SetRowCount(_grid,_reportBal.ReportItemContent.Rows.Count + 1);
            for(int rRow = 0;rRow <= _reportBal.ReportItemContent.Rows.Count - 1;rRow++) {

                if(vWorker.CancellationPending) {
                    e.Cancel = true;
                    break;
                }

                for(int cCol = 0;cCol <= ReportColumns.Count - 1;cCol++) {

                    string vValue = _reportBal.ReportItemContent.Rows[rRow][cCol + 1].ToString(); ;

                    var sp = new StackPanel { Orientation = Orientation.Horizontal };

                    var tb = new TextBlock {
                        Text = vValue,
                        Width = double.Parse(ReportColumns[cCol].Width),
                        Margin = new Thickness(8,3,8,3),
                        TextWrapping = TextWrapping.Wrap
                    };

                    sp.Children.Add(tb);

                    Grid.SetColumn(sp,cCol);
                    Grid.SetRow(sp,rRow + 1);
                    _grid.Children.Add(sp);


                }

                if(vWorker.WorkerReportsProgress) {

                    int vPercentComplete = (int)((float)rRow / (float)_recordCount * 100);
                    string updateMessage =
                        string.Format("Record(s) {0} of {1}",rRow,_recordCount);
                    vWorker.ReportProgress(vPercentComplete,updateMessage);
                }
            }

            #endregion

            e.Result = _grid;
            //_reportItemContent = _grid;
        }
        catch(Exception exception) {
            throw new Exception("#Error: Error parsing with report items" + Environment.NewLine +
                Environment.NewLine + "#Internal Error: " + exception.Message,exception);

        }
    });
    _worker.ProgressChanged += (s,e) => DispatcherHelper.RunAsync((() =>{
        ProgressPercentage = e.ProgressPercentage;
        Output = (string)e.UserState;
    }));

    _worker.RunWorkerCompleted += (s,e) => /*DispatcherHelper.UIDispatcher.Invoke((() =>*/ {
        if(e.Error != null) throw new Exception("Error Arg");
        _reportItemContent = (Grid)e.Result;
    };

New Post: MVVM Light Toolkit doesn't work on WP 7.1 project in VS 2012 Express

vfede — Mon, 29 Apr 2013 09:50:56 GMT

Thank you both so much for the explanation.

The thing that keeps bothering me is that I worked with that line of code in designMode for months and it worked flawlessly. Misteries of VS and Blend...

New Post: MVVM Messenger issue under WIndows 8

SergeCalderara — Mon, 29 Apr 2013 07:11:20 GMT

Dear all,

I have a WPF standard application which implement MVVM pattern using the MVVM light tool kit. Using actually the verison 4.0 of it. When running that app under Windows 7 touch PC I do not have any trouble but when trying that same app under Windows 8 Desktop, it seems that when using the Messenger to send Message betwenn different ViewModel, message are not receive properly.

By setting abreak point at the receiver, it is not hit and no exception occurs

The project has been build using VS 2010.

Does anyone have met this issue and how to solved ?

New Post: MVVM Light Toolkit doesn't work on WP 7.1 project in VS 2012 Express

lbugnion — Mon, 29 Apr 2013 04:37:54 GMT

That is correct. In addition to hardware issue, Blend can have issues with asynchronous code (for example when attempting to access web services), thread switching, database access, etc.

In some of my presentations, I show how to attach a Visual Studio debugger to able Blend while it is running your code, and how to execute the code until you find what line is causing the issue. You can then work around the issue with a variety of tricks including avoiding to execute some parts of the code in design mode, and using mocked services to create Blend-safe services.

cheers
Laurent

New Post: MVVM Light Toolkit doesn't work on WP 7.1 project in VS 2012 Express

jeff_winn — Mon, 29 Apr 2013 04:25:06 GMT

There are some things in Windows Phone and WPF apps that require hardware to work correctly. In a designer like Blend, this hardware may not be present. As such, when trying to instantiate those components that communicate directly with the hardware will generally throw errors indicating since the hardware is not available.

New Post: MVVM Light Toolkit doesn't work on WP 7.1 project in VS 2012 Express

vfede — Sat, 27 Apr 2013 17:47:50 GMT

Hi again,
I solved the Blend crashing and Design Preview window in VS12 not showing prview with the trick described here:
http://stackoverflow.com/questions/15326131/visual-studio-expression-remoteexception

if (!ViewModelBase.IsInDesignModeStatic)
 {
     _watcher = new GeoCoordinateWatcher(GeoPositionAccuracy.High) { MovementThreshold = 5 };
 }

I hope it could help and I am curious to know why this happened and why this fixes the problem, I will really appreciate that.

Thanks for MVVM Light!

New Post: MVVM Light EventToCommand and PRism+MEF

jivara — Wed, 24 Apr 2013 06:22:41 GMT

Hi,
This is great news. Please check this discussion at How to Trigger and handle TextChanged event from Text Box within DataGridColumnHeader in style Resource Dictionary where i wrote down the problem in details and help me rectify the errors.
Thanks

New Post: MVVM Light EventToCommand and PRism+MEF

elliatab — Tue, 23 Apr 2013 08:53:55 GMT

Like Laurent said, there is no reason for EventToCommand not to work in your PRISM/MEF application. If it helps, we are currently using it in our PRISM 4 solution (we are also using MEF for DI) so I can confirm it works.

New Post: MVVM Light EventToCommand and PRism+MEF

lbugnion — Tue, 23 Apr 2013 07:26:18 GMT

Hi,

Did you try it? I don't see any reason why it shouldn't work. Note however that Blend triggers cannot react to all event types, only routed events.

Thanks
Laurent