I've been setting up a pretty vanilla website using Umbraco 7. Suddenly, I'm getting a strange error, while trying to publish an update to a page.
I don't think I've done anything to cause it. Has anybody any idea what it could be?
An error occured
Unable to cast object of type 'System.Web.Caching.AspNetCache' to type 'System.Collections.IEnumerable'.
Exception Details
System.InvalidCastException: Unable to cast object of type 'System.Web.Caching.AspNetCache' to type 'System.Collections.IEnumerable'.
I've received an answer over Twitter. It appears it's a Windows 10 bug, in the latest preview builds from 15002, https://our.umbraco.org/forum/using-umbraco-and-getting-started/82257-unable-to-log-into-backoffice-greeted-with-a-white-screen-log-shows-invalid-cast-exception. Apparently there is a fix which should be out in a week or so (Today's Date 01 Feb 2017)
Related
Me and my team have just migrated our cross-platform XF 4 project to XF5.
The only issue that we have encountered thus far is the following:
Our UWP App was throwing an unhandled App.Xaml exception when navigating to a different page for no apparent reason and after some search, installing the nugget Microsoft.UI.Xaml explicitly fixed that issue, even though that nugget package is supposed to be installed along with XF5 nugget.
But right now a new issue has emerged. When calling the await Application.Current.MainPage.**DisplayAlert**(szTitle, szMessage, btnOk, btnCancel); from the UI thread the alert gets displayed properly but when I click on one of its buttons Ι get an unhandled exception
"No installed components were detected. The property path '(controls:AnimatedIcon.State)' could not be resolved for a Setter." where controls is defined as xmlns:controls="using:Microsoft.UI.Xaml.Controls"
Could you please help me find out what is going wrong?
As far as I know the DisplayAlert() is handled by Xamarin.Forms.
Finally I decided update my app to new Xamarin.Forms 5 ... but after solving few issue with build and running application it crashes with error:
IsTransient: Exception of type 'System.NotImplementedException' was thrown
Message: No Content found for ShellContent, Title:New Contact, Route D_FAULT_ShellContent16
TargetSite: Xamarin.Forms.IShellContentController.GetOrCreateContent
Have anybody faced with the same issue ?
Seems like the issue happens, because Xamarin.Forms 5 does not allow not set ContentTemplate for FlyoutItem
I'm loading the RBCodeHighlighting package from the Cincom store and I get an error which says: "post load action caused an error. Tools.Trippy.BehaviorInspector has no binding". If I continue my image is broken and I can't open a workspace. I get a DNU in Workspace>>postBuildWith:
Anybody has any idea what's the solution?
That means that Tools.Trippy.BehaviorInspector is not found as a class or SharedVariable in your image. If that originates in the postLoad-action than the code is basically loaded correctly, just some post-load initializations didn't work.
RBCodeHighlighting is only needed in VisualWorks 7.x, not in 8.x. In 8.x the SourceCodeEditor uses Text2 and RBCodeHighlighting doesn't work anymore with it.
I am developing an app that uses DatePicker and LoopSelector at same time.
Looking on the tutorials for each of them I have been advised to add assembly references, first one for DatePicker and second one for Loopselector:
xmlns:toolkit="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit"
xmlns:toolkit="clr-namespace:Microsoft.Phone.ControlsPrimitives;assembly=Microsoft.Phone.Controls.Toolkit"
and then I get error message saying The type 'toolkit:Selector' wasn't found.
I welcome any ideas. Thanks.
You cannot have the same name ("toolkit") for both of them!
Error context:
Visual Studio 2010 Service Pack 1
ASP.NET MVC 3 Application
IE9 with Script Debugging enabled for Internet Explorer
Error conditions:
Execution stops int a JavaScript file called "script block [dynamic]" at the following line
doc.addEventListener("DOMNodeInserted", onDOMNodeInserted, false);
that line of code is nested inside the following if block
if (ver >= 9.0)
{
doc.addEventListener("DOMNodeInserted", onDOMNodeInserted, false);
doc.addEventListener("DOMNodeInsertedIntoDocument", onDOMNodeInsertedIntoDocument, false);
}
This is a very persistent error that started happening after I re-imaged my hard drive and reinstalled VS 2010 SP1 and ASP.NET MVC 3. I did it twice to make sure I did it right.
I am going to take a guess and suggest that this bug is the side affect of an un-handled exception in ASP.NET MVC 3 or a bug in IE9. The error seems to ocurr when a (GET?) action method cannot be found that is specified in the ActionLink HTML helper method such as
#Html.ActionLink("Link Text", "Action")
I believe that IE9 does support addEventListener so the error itself is incorrect. Unless I can get more info this error is beyond my ability to fix its cause. I can prevent it by making sure that my action method is there and that it works. That is a workaround not a fix. Fixing the error would prevent it from being erroneously reported because IE9 does in fact support addEventListener.
An answer has been found to this question. The problem was caused by the Divix browser plugin
Solution: Object doesn't support property or method 'addEventListener'
Thank you to a poster on the asp.net forums for helping to solve this problem. The Divix browser plugin has recently been updated. The update may have fixed this issue. However, it remains disabled on my system. Disabling the Divx plug-in definitely fixed this issue for myself and others. I have reported this bug to Divx support.
I've been getting this error today while working on a VS 2010 project, I was using IE9 for my browser. Turns out it's an erroneous message, I should have been getting a page not found error. I tried disabling Divx as mentioned above, but that didn't help. I then tried using Chrome and it reported my error correctly and I was able to solve my problem.
If you get this error, try a different browser which may point you in the right direction.
I turned off Compatibility Mode (was running on local intranet) and the problem went away.