single silverlight control in an asp.net mvc website?
By : user1242261
Date : March 29 2020, 07:55 AM
help you fix your problem Simple answer, Yes! Follow the following link to see a demo app developed by some students in the UK. Integrating something similar in your ASP.NET MVC application can be done by using service calls into Controller methods that return JSON, or strongly typed objects.
|
setting data context of silverlight user control leaves the control as always visible
By : user2500612
Date : March 29 2020, 07:55 AM
should help you out Have you verified that your converter is being called at all? I'd just put a breakpoint in and see what happens.
|
How to hide and show silverlight user control on main Silverlight Control?
By : user2575397
Date : March 29 2020, 07:55 AM
To fix this issue for programmability you might wanna set an id for the control u declare in xaml. you could say x:Name="top10" or something similar. on the click event of the button you could use the code below code :
top10.Visibility = Visibility.Collapsed; // to hide
top10.Visibility = Visibility.Visible; // to show
|
ArgumentException on setting DefaultStyleKey in custom control deriving from user control - Silverlight 4
By : user3545808
Date : March 29 2020, 07:55 AM
this will help Assigning a type that derives from UserControl to DefaultStyleKey is explicitly disallowed by throwing a ArgumentException (why an ArgumentException and why no explanitory message is included only the SL team know). A UserControl cannot be templated receiving instead its own associated Xaml. Thats the whole point of UserControl. You need to convert MyUserControl into a templatable control was well if you wish to inherit off it in manner you are attempting.
|
How to open another user control from the view model class of a user control in silverlight?
By : Tim Peters
Date : March 29 2020, 07:55 AM
wish of those help What you describe is one of the problems most people new to MVVM struggle with - Navigation. I'm trying to avoid in general to have any of my Viewmodels bear any knowledge on neither its own view (a viewmodel is supposed to be pretty view agnostic) nor any other view. One way to solve this is to have a central component in your application that handles all navigation. Let's call it NavigationController. This component handles navigation requests and is responsible for creating the views (and optional the associated viewmodels) and their initialization and it is the only component in the application that really knows about the interdependencies between the various ViewModels and their respective views.
|