this is indicating a problem locating your dll. i hav eno idea where the refrence is ... I would open up a edit -> find in files (something like that) look around under edit menu... then copy and paste the file name. the folder and files you search should Include the PROJECT FILE. actually you might start with the project file as it is most likely to have the reference. ANyways once you find it change ti to the correct location... The correct location being where you installed f#. Again you ay have to do a search using start menu-find files. good luck let me know if I can help out. Derek

By on 11/23/2007 12:56 PM ()

Would I be right in that you're trying to run the F# 'ajax' stuff which is described here?
[link:tomasp.net]

I'm having exactly the same problem, so I tried using (via control panel>admin tools>microsoft .net2 config) to add the f# assemblies to the GAC (I added all fsharp.*.dll files). It still didn't work, but looking at the assemblies in the GAC, I noticed that the public token key is actually different to the one in the web.config!

I don't how this can be when the actual version number of the f# is correct, but I'n new to .net too, so maybe I'm missing something?!

Anyway, if you change (the line with the PublicKeyToken in it) config file you quoted above to ...

1
    <compiler language="F#;f#;fs;fsharp" extension=".fs" type="Microsoft.FSharp.Compiler.CodeDom.FSharpAspNetCodeProvider, FSharp.Compiler.CodeDom, Version=1.9.2.9, Culture=neutral, PublicKeyToken=a19089b1c74d0809"/>

you may get some progress. Good Luck. For my part, I now have a new error, which I think is suggesting that I need to install the LINQ preview as well (because FLINQ.dll may be referring to System.Xml.Xlinq).

It also took me a good while to work out how to compile the webtools.controls.dll and webtools.core.dll files - some instructions on setup would have been really useful for this, and I might try contributing some should I ever get this running...

By on 10/23/2007 2:56 PM ()

Hi,
thanks for the comments regarding F# WebTools. I'll fix the build problems that you discovered and I'll try to add some quick "how to" on my blog soon! The LINQ reference is a bit problem, because I'm afraid that adding the LINQ DLLs to the download package would break some license agreements...

I'm afraid that this won't be fully solved until .NET 3.5 RTM will be out, but I'll try to write some "how to".

Anyway, thanks for your interest in the project!
Tomas

By on 10/23/2007 3:11 PM ()

Hello Tomas!
I downloaded thee LINQ (May preview), and that solved the problem I was having. however, the problem I have at the moment is that I get the following error when attempting to call the Lectures.aspx page from a web browser (see below). I have 1.9.2.9 installed and referenced in my web.config, so I've been scratching my head to work out why it's looking for version 1.9.2.7 - I assume it's an internal reference from one of the assemblies? (remember I'm just a newbie...)

Reading around, I got the impression that 1.9.2.7 of f# was created without the (normal) demo files, and that 1.9.2.9 was a recompilation to add them in, so maybe, I figured, a number of people would be likely to have them both on their machines. However, I only had 1.9.2.9 installed, and I can only find the .MSI file for 1.9.2.7, which won't let me install whilst I have a later version on my system. Huffle. So, my plan now is to get 1.9.2.7 as a zip, and manually add the assemblies into the GAC (which should be ok, as they're different versions..?)

However, I can't find anywhere I can get hold of the zip version of the 1.9.2.7 release - would anyone know where I can grab a hold of it?

On the subject of build problems, important tips I would like to add are:

  1. 1) Add the F#'s bin folder to the PATH environment variable.
  2. 2) Recompile the rewriter tool (it was crashing when I ran it). This is easy to do as the .fs file is supplied.
  3. 3) I don't know why, but the script to copy the webcore/webtools assemblies etc. to the demo projects' Bin folders didn't want to play. I didn't investigate too much because I just dragged them manually. It may well have been something to do with where I extracted the zip file though.
  4. 4) compile the webcore before the webtools (which I had correctly guessed, but it's worth mentioning in the howto).
  5. 5) When the site is built, it will not automatically open the page in the browser. You need to either right click on the aspx page and choose (open in browser) or type it (on the end of the ASP.Net development server's address) into the browser manually. This of course applied to running from Visual Studio (I don't have IIS :-( ).
  6. 6) Pre-requisite items needed on the system are:

f# 1.9.2.9 and 1.9.2.7 (?)
Linq preview May 2006.
Visual studio (with c# installed).

I'm running on an XP machine by the way.

Finally, I just want to say that I hope I'm not coming across as negative - I'm not from a web development background, and I find the plethora of languages and browser inconsistencies wildly infuriating. Any project which can combine server and client code into one language (and a functional one at that!) is to my mind a stroke of genius. I think it might be worth re-iterating in your blog that f# isn't properly a part of visual studio, and doing f# (and especially integrating into web projects) is inevitably going to involve a few 'hacks'. I know you do talk of this in the blog, but some newbies might skip the technical details and go straight to the download to start playing with the pretty new toy. Big Bold Letters might be an idea :-) Not that I did that of course...

Talking of which, I hear rumour (I read it somewhere) that there's a plan to make F# an official part of Visual Studio (i.e. you'll be able to install it as a VS option just like C# and VB.net) - would you know anything about this? I hope it's true.

Anyway, thanks, and keep up the works of genius!

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Could not load file or assembly 'fslib, Version=1.9.2.7, Culture=neutral, PublicKeyToken=a19089b1c74d0809' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'fslib, Version=1.9.2.7, Culture=neutral, PublicKeyToken=a19089b1c74d0809' or one of its dependencies. The system cannot find the file specified.

Source Error: 

Line 70:                         ConnectionStrings.Item("dictionaryDb").ConnectionString);
Line 71:         let cts = 
Line 72:           SQL <@ { for c in §db.Country 
Line 73:                    -> { CountryID = c.ID; 
Line 74:                         CountryName = c.Name } } @>

Source File: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\demos.lectureweb\15309743\1b12d634\App_Web_dslxwbjh.1.fs    Line: 72 

Assembly Load Trace: The following information can be helpful to determine why the assembly 'fslib, Version=1.9.2.7, Culture=neutral, PublicKeyToken=a19089b1c74d0809' could not be loaded.
By on 10/24/2007 2:41 AM ()

Hi,
I think that he problem may be that the 'finq.dll' that you're using was built using F# 1.9.2.7.
The following version was built using 1.9.2.9, so it should work: [link:tomasp.net]

Thanks again for your list of possible issues that should be included on the "How to list" - it is very useful!

>> Rumors about F#
There was an announcement by S. Somasegar (who is a manager of the Developer Division). You can find it here: [link:blogs.msdn.com]. The following article is also quite informative: [link:www.infoworld.com].

T.

By on 10/25/2007 7:05 PM ()

The path and lib environment variable has no effect on where .NET applications look for dlls. The .NET runtime first looks in the GAC and then in the directory the application is installed under (the .\bin directory in the case of web applications).

FSharp.Compîler.CodeDom.dll is not installed in the GAC by default, so you either need to install it in the GAC, using gacutil.exe (part of the .NET sdk), or copy it to the websites .\bin directory. Note that where your web applications .\bin directory is located is affected by your IIS settings if you are using this as a web server.

Cheers,
Rob

By on 10/17/2007 2:50 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