silverlight-3.0

I am creating a Silverlight with WCF connectivity. I would like to create and maintain a session after user login in Silverlight and do the following. On successful login, create a session object and store session id, user id, user name, session status On further calls with WCF, the session information needs to be passed from Silverlight to WCF One solution would be to create a session object and pass it as parameter to all methods. Is there any other way of passing the info in all web service calls without passing a member variable? Something similar to persistent Session object in ASP.NET.

Im just starting to get to grips with silverlight 3, coming from ASP.NET and Flex. I have followed the new navigation tutorial here and read through the authentication and role management tutorials also. So, i have a main page, which has a frame, inside of the grid, and several views. These are all navigatable and working fine. I see this main page as kind of a master page to my little application i have i mind. So know I want to have a login.xaml UserControl. This will handle all login and once authenticated I want to navigate to the MainPage, and the use its frame to go from there. I dont

The .NET RIA Services are described as an n-tier framework for Silverlight. I have been wondering what the relation is between this framework and the Model-View-ViewModel pattern. Are they in conflict or can you see the potential for synergic combination? .NET RIA Services and MVVM are synergistic, and aren't in conflict. For example, if I write a Catalog domain service that exposes Products and Categories on the server, and correspondingly have a Catalog domain context on the client... then the following are options to use depending on the scenario: Write a view model that wraps the Catalog

I want to know if there is a way of using C# to get the Current Silverlight Version a user is running when opening a client of an app I'm developing. It is for logging purposes. I want to know if they are using Silverlight 3 or 4 on their browsers var dotNetRuntimeVersion = Deployment.Current.RuntimeVersion; var silverlightVersion = Environment.Version.ToString(); Supported in: 5, 4, 3 Using C# only I don't know, but what you could do is detect it with javascript and then send an ajax request to a function which lets the server know what version. http://www.apijunkie.com/APIJunkie/blog/post

I am making a sort of "print preview" control for some documents in my Silverlight 3 application. I have a Canvas (for showing the document) inside of a ScrollViewer, and I have zoom in / zoom out buttons that control the X and Y Scale properties of the ScaleTransform for the Canvas.RenderTransform property. I want the scrollbars of the ScrollViewer to show up when I "zoom in" enough such that the canvas is no longer visible in the ScrollViewer area, but it seems that they only show up depending on the Width/Height of the Canvas itself, regardless of whether it is zoomed in or not. Can anyone

I have a Silverlight3 application that is meant to run on both Windows and Mac OS environments. I would like to know in runtime if my application is running on a Windows or Mac so I can tweak a few things to the way users are accustomed to in their operating system of choice. For example, in Windows it is the norm to use "OK" "Cancel" buttons, while in Mac OS the norm is "Cancel" "OK" buttons (reverse order). Any ideas? NewAgeSolution There are two ways. From Silverlight: string os = Environment.OSVersion.Platform.ToString(); string version = Environment.OSVersion.Version.ToString(); From ASP

The ChildWindow is a modal window, but it does not block. Is there any way to make it blocking? I basically want a ShowDialog() method that will call ChildWindow.Show() but then not return until the user has closed the ChildWindow. I tried using Monitor.Enter() to block after ChildWindow.Show(), but the ChildWindow never rendered and the browser just hung. Anyone have any ideas? I don't believe it supports that behavior. You can vote for it on CodePlex. Depending on what you want, you might either look at some of Tim Heuer's workarounds here , or use a different custom control, like the