MvxCollectionViewCell samples that I can find on Internet are not reflecting current version of MvvmCross (5.x).
DelayBind does not exist as a method of binding.
Can anyone explain this?
Sorry, Visual Studio somehow created local MvxCollectionViewCell.cs so I inherited from empty class.
Please ignore my question.
Related
I'm creating script tasks in SSIS packages using the free BIMLExpress. Since we have different versions of .NET Framework installed in our environment I really need to be able to set the Framework version for the script project. Although I know how to change it manually, it would be very difficult to change it manually.
I have already tried looking for a solution and this answer suggests to use TargetFrameworkVersion property but I don't see that property at all, I've tried using it with no effect. I don't know if it only works with BimlStudio the paid version.
I'm using BIMLExpress 5.0.61915.0 with Visual Studio 2015.
Any help is greatly appreciated.
Thanks
I opened the generated .dtsx package and found that the TargetFrameworkVersion node placed inside of a separate PropertyGroup node. After I had moved it out to the first PropertyGroup of the same arrayElement node, then reopened my package in Visual Studio again, issue was gone! So you can write a script to move TargetFrameworkVersion node into the proper place for now.
Varigence support team told me that a public preview release is coming late next week which will include a fix for that.
While developping with Thymeleaf, I spotted the HTML5 Validation Dialect under the Community Dialects at the Thymeleaf website.
But now I'm currently integrating it, I found out this dialect is unfortunately not compatible with Thymeleaf 3 because it extends org.thymeleaf.dialect.AbstractXHTMLEnabledDialect which can't be found anymore in thymeleaf-3.0.2.RELEASE.jar
Indeed, someone requested support on 2016-09-22: https://sourceforge.net/p/html5valdialect/tickets/11/
Otherwise, I spotted someone who forked the dialect, but to no avail (because despite some pom.xml dependency updates, it stills extends that AbstractXHTMLEnabledDialect class)
https://stackoverflow.com/a/29758466/666414
Does anyone has a hint to something alternative?
Thanks.
I forked the "Thymeleaf Html 5valdialect",
and updated it to support Thymeleaf 3.
Please take a look.
https://github.com/masa-kunikata/html5valdialect
I am currently working on a legacy web app which uses newtonsoft.json.dll version 1.3.0 and vb.net.
I added four new fields in the application. This source code is shared by another application and it posts into my application and it breaks it.
See image for error.
[]
The error is:
Could not find member x on object of type runtimetype.
The stacktrace breaks at:
newtonsoft.json.jsonserializer.setobjectmember(jsonreader reader,object target, type targettype, string membername)
I did some research. The folks reportedly solved such an issue by upgrading DLL version and didn't have a direct solution to fixing it via code change. I know its very old and the application is high impact any upgrade has huge ripple. However they are planning a rewrite of the application.
Can someone please share any ideas that i should pursue in order to solve this?.
I am expected to make it quick and under pressure.
https://smugmugc3.codeplex.com/workitem/10024
My problem is very similar to what is described in the link above.
I am going to upgrade my version of json converter after convincing my boss and I see that is the only way out of this problem.
After which I will update this thread if I find issues.
I want to submit an app I wrote to the Windows store. All the examples I have found about implementing trial functionality in an app, seem to be dated. For example, most tell you to add the using directive 'using Microsoft.Phone.MarketPlace; which causes Visual Studio 2013 to ask if I have forgotten an assembly reference. Am I supposed to add a NuGet package or something? Any help would be greatly appreciated.
using Microsoft.Phone.Marketplace;
Can anyone suggest a good, reliable, and current source of information?
It should be in the Microsoft.Phone assembly, Microsoft.Phone.dll.
It may be available as an assembly reference on your machine, I couldn't see it on nuget.org.
https://msdn.microsoft.com/en-us/library/windows/apps/microsoft.phone.marketplace.licenseinformation(v=vs.105).aspx
I've found a topic describing NullReferenceException in Windows Phone designer, however I believe this is a somewhat different issue, since it happens in all platforms and not related to MvvmCross plugins.
Designer (VS2012, Store/WP8/WPF apps) works fine for earlier versions of MvvmCross. I tried to compile a version that corresponds to 3.0.6 NuGet packages, and I can see that design-time model is loaded in all platforms.
Recent MvvmCross version causes all designer to raise NULL reference exception ("Object reference not set to an instance of an object") on all platforms.
Attempt to debug a VS instance didn't help: the call stack doesn't say much, and there is no MvvmCross code there.
The error is not related to the actual view/view model: I can remove all controls from the view, and the error is stil raised. The view model constructor code is never reached.
So it looks like there's some MvvmCross code (not from MvxView) that is unsuccessfully executed in at design-time. I wonder if this is a known issue and/or if there is a workaround to get designer work.
UPDATE. I created a GitHub issue with steps to reproduce the problem: https://github.com/slodge/MvvmCross/issues/347
This question moved to GitHub where there was lots of discussion and a few samples - https://github.com/slodge/MvvmCross/issues/347
From these samples, I believe we concluded the Nuget release 3.0.8.1 :
supports time data based on Blend-generated XML data files
supports design-time data based on simple C# classes
does not support design-time data where the data uses MvvmCross MvxViewModel as a base class
It isn't entirely obvious that developers should want to do the third thing (designtime data isn't real data?), but given that the overall MvvmCross manifesto broadly speaking aims to enable developers and to give them choice, then future MvvmCross will make this easier in the future.
In the meantime, if anyone wants to initialise objects at design-time, then there are a few helper classes around to enable this.
For example, the color plugin (and a small part of MvvmCross IoC) can be made available in the design-time environment using the MvxColorDesignTimeHelper - see:
https://github.com/slodge/MvvmCross/issues/323 (linked to MvvmCross throws NullReferenceException in Windows Phone Designer)
https://github.com/slodge/MvvmCross/blob/TibetBinding/Plugins/Cirrious/Color/Cirrious.MvvmCross.Plugins.Color.WindowsPhone/MvxColorDesignTimeHelper.cs
https://github.com/slodge/MvvmCross/blob/TibetBinding/CrossCore/Cirrious.CrossCore.WindowsPhone/Platform/MvxDesignTimeHelper.cs