Sounds like you want to stick with VS2008 for now.

  • .fsproj files are not compatible. This is a Visual-Studio- / MSBuild- ism. When you open a project created with VS2008 inside VS2010, the 'upgrade wizard' will upgrade the project in place, and this will make it unusable in VS2008.
  • We have not yet posted the PowerPack binaries that are compiled for .Net 4.0, so if you need the PowerPack, VS2010 is a non-starter for the next few days until we get the PowerPack posted.
  • F# in VS2010 Beta1 targets only .Net 4.0 Beta1, whereas F# in VS2008 targets .Net 2.0/3.0/3.5.

See also

[link:lorgonblog.spaces.live.com]

By on 5/21/2009 10:49 AM ()
  • F# in VS2010 Beta1 targets only .Net 4.0 Beta1, whereas F# in VS2008 targets .Net 2.0/3.0/3.5.

Well, that answered my question. I suppose we would just migrate to current version of F# on VS 2008 for now.

By on 5/21/2009 3:19 PM ()

Regarding PowerPack - isn't it possible to take the source code from 2008 version and compile it with VS2010? I did that, and then used the produced DLL to compile FParsec successfully. Didn't check if it actually works, though, but what potential problems are there?

By on 5/21/2009 11:40 AM ()

Regarding PowerPack - isn't it possible to take the source code from 2008 version and compile it with VS2010? I did that, and then used the produced DLL to compile FParsec successfully. Didn't check if it actually works, though, but what potential problems are there?

This should probably be fine, we just assume most users don't want that hassle. Soon when we drop the 'official' version you probably want that in case there are any differences somehow.

By on 5/21/2009 12:29 PM ()

I was going to use the FSharp.PowerPack in a presentation next week. How would I go about building the PowerPack? Or should I just stick with VS2008?

Cheers!

By on 5/21/2009 7:40 PM ()

I was able to compile my project with VS 2010 and the PowerPack from the CTP, but it would not run because of some "missing function" runtime exceptions.

By on 5/22/2009 7:47 AM ()

I was able to compile my project with VS 2010 and the PowerPack from the CTP, but it would not run because of some "missing function" runtime exceptions.

Did you just take the PowerPack assembly from the 2008 CTP as is? That won't work for sure (and the compiler will even warn you about that, saying that PowerPack is compiled against different version, and is incompatible).

By on 5/22/2009 3:27 PM ()

FYI, we finally have the PowerPack binaries for VS2010/.Net4.0 Beta1 online:

[link:www.microsoft.com]

The long term plans are still to have this up on CodePlex (as mentioned a while back on Don's blog

[link:blogs.msdn.com]

) but we wanted to go ahead and make the binaries available in the meantime, to unblock those who want to use the PowerPack on .Net 4.0 Beta1 right now. Sorry it took so long to come online!

By on 6/3/2009 6:53 PM ()

Very cool.

I originally searched for how to get the Power Pack for .NET 4.0 from Google and I ended up at this site to download it - [link:www.softpedia.com]

The binaries there seemed to be recognised inside a script file in VS2010 but when I tried to reference the Power Pack dll from fsi 1.9.6.16 the dll wasn't loaded with this error:

error FS0191: Error opening binary file 'C:\Program Files\Microsoft F#\FSharp-PowerPack-4.0-Beta1\FSharp.PowerPack.dll': MapViewOfFile(0x80070008)

When I download from the Microsoft site - [link:www.microsoft.com] - it all worked fine.

Cheers,
Mark

By on 6/8/2009 1:58 AM ()

FParsec doesn't need the PowerPack.

If you comment out the (non-essential) "StructuredFormat" related code from primitives.fs and primitives.fsi, and put "[<CompilationRepresentation(CompilationRepresentationFlags.Instance)>]" above the ToString override in error.fs and error.fsi, FParsec should compile again.

I'm working on a major update of FParsec which I hope to be able to release on CodePlex early next week.

- Stephan

By on 5/21/2009 12:18 PM ()

put  "[<CompilationRepresentation(CompilationRepresentationFlags.Instance)>]" above the ToString override in error.fs and error.fsi

I was actually wondering if override is needed in the .fsi at all. Since it's already defined by the base class, the fact that it's overriden there is an implementation detail, no? And I should still be able to call ToString on instances of that type even if I don't have it in the .fsi ...

By on 5/21/2009 3:40 PM ()

int19h, you're right, the override declaration in the fsi is only for documentation purposes.

By on 5/22/2009 1:16 AM ()

The solution files and binaries are incompatible between VS 2008 and VS 2010. You could install VS 2010 Beta 1 in parallel, but I wouldn't yet recommend it as your primary development IDE.

By on 5/21/2009 10:47 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