Advanced Forum Search Results
-
OK, I think I figured it out. Even referencing the DLLs, VS still looks at the project. So move the DLLs out to another location and reference them from there. Also, F#'s optimize code seems to have some sort of issues with SL's mscorlib. Then F# should work fine:
(The previously posted stackoverflow link has the info.)
-
I don't think that's accurate. F# has many options to target other .NET platforms:
fsc --noframework --cliroot "C:\program Files\Microsoft Silverlight\2.0.31005.0" --standalone
Manifest ends up with only one external assembly reference, to Silverlight's mscorlib. VS Silverlight tools STILL won't reference it ...
-
Here is the exact code I have in a production system and it works fine in conjunction with the rest of the code:
protected void Application_EndRequest(object sender, EventArgs e)
{
// In all ...
-
I have sample code on my site. But no, I didn't have to do anything that I recall. Can you post a full stacktrace?
-
Awesome, thanks. So we'll just restyle and everything will be fine.
-Michael
-
Right now, each operation returning a value gets "OperationXCompletedEventArgs" which inherits AsyncCompletedEventArgs. This event args class really just adds a Result property of a specific type. It seems it'd be a lot easier to deal with this with generics and have an AsyncResultCompletedEventArgs<T> with a property T Result. ...
-
I hate to me too this, but this feature definately got my vote. .NET programming model with access to audio/video == some pretty awesome possibilities. Then again, Silverlight is so full of win that they can afford to miss entire areas and still kick the crap out of Flash.
I suppose the good thing is that MS is being pretty ...
-
Well, I'm not sure of your particular apps design, but using SqlDataReader direct from an ASPX page seems sort of icky. In some app designs, you'd already have a service layer in between, so using Silverlight for the client means you don't need a server-side presentation layer. That's a whole tier of servers you can theoretically ...
-
This is for WCF on the server, but most of the code doesn't depent on WCF. I'm pretty sure you could fixup the code to work with ASMX:
http://www.atrevido.net/blog/2008/03/27/Hacking+SOAP+Faults+Into+Silverlight+2+Beta+1.aspx
-Michael
-
Well I got a cheap hackaround to at least allow some faulting with Silverlight: http://www.atrevido.net/blog/2008/03/27/Hacking+SOAP+Faults+Into+Silverlight+2+Beta+1.aspx
It's cheap, it's hacky, but it gives me enough to deal with until Beta 2.