Hi,

This is likely to be because of the use of CodeDom.dll, which requires fsc.exe be installed on the target machine, and which will no doubt require some higher level of priveleges.

If you are building a production system, our current recommendation based on the CTP bits is to use a C# presentation layer (e.g. a C# web app) with an F# code-behind DLL for your application logic.

Thanks

Don

By on 10/15/2008 10:52 AM ()

Don,

Thanks for the reply.

I'll use a C#-web app as you suggest for now (even though the dependency of fsc.exe seems a bit strange to me).

Regards,

Johan Kullbom

By on 10/23/2008 11:32 PM ()

Followup:

I'm now using a C# web application without code-behind files where the aspx-pages "Inherits" from types defined in a referrenced F#-assembly.

The referrenced F#-assembly is compiled using "--staticlink FSharp.Core" (under "Project Properties" -> "Build" -> "Other flags").

I had to manually add references to quite a few framework assemblies (including "Microsoft.VisualC" ??) but once done my site runs fine.

The site is now plain F# and hosted in a (shared and cheap) Medium Trust environment.

I am not able to use any inline F# on the pages - will have to use C# for that - but since I never liked that anyway that is not a problem...

(So far) I much prefer this sollution to using C# in code-behind ...

Regards,
Johan Kullbom

By on 11/7/2008 2:29 AM ()

Thanks for the follow up, sounds great! Just out of interest, what's the site?

Cheers,

Rob

By on 11/7/2008 4:21 AM ()

Robert,

The site is not public yet but I make sure to post a reference to it here when it becomes so ...

Regards,

Johan

By on 11/7/2008 4:45 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper