If you are using an ASP.NET service provider, then you might want to look at how I solved this problem, by deploying C#/ASP.NET at the root of the site, and F# DLL's for the rest.

By on 11/23/2009 1:16 AM ()

I think you should be able to just deploy your app and a copy of FSharp.Core.dll next to it.

By on 11/22/2009 11:12 PM ()

Actually the first file that is missing is the FSharp.Compiler.CodeDom

Then it looks for FSharp.core.dll

After that all I get is a generic "The system cannot find the file specified"
from "..fsppack\FSharp.Compiler.CodeDom\compiler.fs:119"
I'm unable to figure out what exactly is missing -- perhaps the code-behind file? But it's in the same configuration that runs locally!
In either case, it's not as simple as xcopy. Or if it is, I must be missing something that's easy.

By on 11/23/2009 3:01 PM ()

Have you tried using the --standalone compiler flag?

--standalone Statically link the F# library and all referenced DLLs that depend on it into the assembly being generated
--staticlink:<file> Statically link the given assembly and all referenced DLLs that depend on this assembly. Use an assembly name e.g. mylib, not a DLL name.

That should generate a larger assembly that won't have other runtime dependencies.

By on 11/23/2009 7:49 PM ()

brianmcn,

Simplying copying FShap.Core.dll and Powerpack.Linq.dll did not work for me. See this thread.

I was using .NET 4.0, I don't know if that applies to this topic.

By on 11/23/2009 4:00 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