Advanced Forum Search Results
-
I've been assuming MSFT would be doing some sort of CardSpace integration where the a presumably trusted CardSpace UI would be presented to gather the credentials, at least on Windows. I wonder what the plan might be for the Mac.
-
I guess I need to get off my fat butt and try it then .
-
Yeah, I kind of figured I'd end up having to hack federated authentication using ASP.NET before displaying the Silverlight application but I was hoping to get some kind of roadmap from MSFT on this, or at least a recognition that they still have some holes in their strategy that the need to work on.
The unfortunate implication of using ...
-
No comments from anyone. I guess this probably means that Microsoft doesn't quite have their Silverlight authentication story put together yet.
-
Now that Silverlight 3 has shipped and Azure is looming larger, I wonder if Microsoft has any updated guidance on how we should be building Silverlight applications that need to authenticate in a federated identity environment. I've done some searches and haven't found much out there discussing this that's less than a year ...
-
OK, I'm an idiot. I had the EndPoint="0.5,1" StartPoint="0.5,0" attributes defined in the <Border.Background> element instead of <LinearGradientBrush>. XAML parse error reporting could be a little clearer though.
-
I might be seeing something different then. I tried reinstalling Windows 7, Visual Studio 2008, and all of the Silverlight tools from scratch and still have the same problem. I'll have to mess around with finding a workaround.
-
I just ran into a similar problem with the final Silverlight 3 build and related tools. I narrowed this down to a Grid with a single Border within. I get this error when the Border has a LinearGradientBackground defined. The error goes away when I remove background.
I just upgraded to the final Silverlight bits on Saturday 7/11 (the ...
-
The hacked code above would sometimes cause catastrophic Silverlight errors, probably because LoadComponent() would be called twice if the Silverlight didn't throw a XamlParseException. I've refined the hack by setting _contentLoaded = false before retrying (_contentLoaded is a member generated by VS in the page's partial class ...
-
Yeah, this was a great help. I've been banging my head against this for a couple weeks and with a relatively complex application with lots of custom templated controls etc. So I figured this must either be my fault or something I'd have to workaround by tweeking the XAML or restucturing the application. I never considered ...