Need an explanation of what binaries are required after a build

[axefrog]

I just performed a build of the latest source code snapshot (.Net 4.0) and I'm a bit confused as to the relationship between the two main projects - IronJS vs IronJS.Runtime. Neither reference each other and both end up with multiple assemblies, but I know previous builds I've downloaded have provided a single IronJS assembly. It would be good if this information was in the wiki.

For what it's worth, I need an "Any CPU" build. It would be great if that could be included as an option, even though it's less efficient than the platform-specific builds. There are many instances where it's not straightforward to choose either the x64 or the x86 build.

[otac0n]

Ok, so first off, there is an Any CPU build. It is on the master branch and in NuGet. In fact, both versions that have been published to NuGet have been Any CPU.

Secondly, what do you mean that neither library references the other? IronJS references IronJS.Runtime.

Thirdly, we have a script in the "Package" folder that will automatically merge the assembiles together so that you can have the "single assembly" that you want.

[axefrog]

I'm sorry, I was going off what was available in the "Downloads" popup. I'm guessing what's there is somewhat out of date. I didn't realise the assemblies needed to be merged.

[otac0n]

They don't need to be merged, but you can do so if you would like. We plan on pushing it out to NuGet that way.

[axefrog]

Will you be updating the downloads in parallel? We don't use NuGet for our project, rather we have a dependencies folder where we dump binaries. NuGet is a little too helpful for us given the legacy nature of our project.

[otac0n]

Ok, I have put the most recent NuGet versions up on the downloads tab.

[axefrog]

Great, thanks I'll check it out. I still recommend an update to your compile instructions in the wiki though.