Programmatically Resolve Assembly Name to Full Path the Same Way MSBuild Does

re: Programmatically Resolve Assembly Name to Full Path the Same Way MSBuild Does

Matt — Fri, 30 May 2008 05:11:11 GMT

Hi Jomo!

This was a very timely post, thank you so much.

Of course, as luck would have it, I'm not using F#... I need to do exactly what you've done here in C#.

I think I understand most of your code. The one thing that I don't get is this part:

IBuildEngine buildengine = new Microsoft.Build.Framework.

let x = { new IBuildEngine with

member be.BuildProjectFile(projectFileName, targetNames, globalProperties, argetOutputs) = true

member be.LogCustomEvent(e) = ()

member be.LogErrorEvent(e) = ()

member be.LogMessageEvent(e) = ()

member be.LogWarningEvent(e) = ()

member be.ColumnNumberOfTaskNode with get() = 1

member be.ContinueOnError with get() = true

member be.LineNumberOfTaskNode with get() = 1

member be.ProjectFileOfTaskNode with get() = "" }

To me that reads, "create a new IBuildEngine with the following properties." Is that right?

Is this creating an anonymous type that implements IBuildEngine?

Do you know how one creates an IBuildEngine normally? I can't even find a concrete type that implements IBuildEngine when I search in Reflector (and MSDN). Any guidance would be greatly appreciated! :)

re: Programmatically Resolve Assembly Name to Full Path the Same Way MSBuild Does

Jomo Fisher — Sun, 01 Jun 2008 09:25:58 GMT

Matt,

That's exactly right. F# lets you anonymously implement an interface with an 'object expression' like you see above. In C# or VB you'll need to create a named type (onymous?) that inherits from IBuildEngine and then new it up inside the resolution function.

re: Programmatically Resolve Assembly Name to Full Path the Same Way MSBuild Does

Matt — Mon, 02 Jun 2008 21:46:32 GMT

Jomo,

Thanks for the reply!

While I was investigating the above, I figured I'd temporarily try to interop directly. I compiled your code with the latest F# compiler and referenced it from my project, and of course it works perfectly. Viva la CLR.

I'm looking forward to a fully supported release of F# so I can justify spending more real work time on it.

As an aside, I'm surprised there isn't a framework class available that implements IBuildEngine. I expected to be able to do something like:

task.BuildEngine = Engine.GlobalEngine;

Keep up the good work, I really enjoy reading your blog.

Matt

re: Programmatically Resolve Assembly Name to Full Path the Same Way MSBuild Does

mood — Fri, 29 Aug 2008 23:50:47 GMT

hi,

i've put your code into VB. so far so good.

but if i try to execute the RAR by:

"If (Not rar.Execute) Then"

i get an "EntryPointNotFoundException" at this point, i don't know why. any ideas?

btw: F# seems to be really nice, fits the minimal style i like so much :)

good bytes

F# Scripts—Reference Nirvana

Jomo Fisher -- Sharp Things — Tue, 02 Sep 2008 09:10:45 GMT

Jomo Fisher— Last time I wrote about getting started with F# scripts. They’re the fastest way to just

re: Programmatically Resolve Assembly Name to Full Path the Same Way MSBuild Does

Steve Guidi — Fri, 09 Jan 2009 03:46:47 GMT

Mood:

Please verify that your code is referencing v2.0 of the MSBuild assemblies. I was able to reproduce the raising of the EntryPointNotFoundException when I referenced the corresponding v3.5 assemblies.

re: Programmatically Resolve Assembly Name to Full Path the Same Way MSBuild Does

Steve Guidi — Fri, 09 Jan 2009 03:48:54 GMT

Any idea why the related XML files don't appear in the result set? I would expect to see at least the XML file for System.Core as it coexists with the assembly in the same directory.