1

So I'm disassembling the Winnov.Amalga.Core.Session.Common.dll, and trying to figure out how the WriteScriptCommand works.

I'm absolutely new to .NET, so go easy on me, please. You can find the dll yourself here: Link under the Binary folder.

Below is pretty much the only reference I found. EDIT: From searching through the decompiled dll.

using System;
namespace winnov.Amalga.core
{
  public interface ISession
  {
     string Configuration { get; set; }
     SessionState { get; }
     TimeSpan Duration { get; }
     string ArchiveBasePath { get; set; }
     string ArchivePath { get; }
     void Start();
     void Stop();
     void ApplyPreset(string presetxml);
     void writeScriptCommand(string name, string value);
   }
}
  • @JasonGeffner I've already gotten it decompiled in DotPeek. That's how I found the code. – B1indfire Jul 24 '15 at 14:11
0

If you look at the decompiled code for the Winnov.Amalga.Core.Client constructor, you'll see that this._Session is a web service interface to whatever web service was used when constructing Winnov.Amalga.Core.Client. Thus, Session.WriteScriptCommand() is a server-side function and its code is not in Winnov.Amalga.Core.Session.Common.dll.

  • Thank you! But in the interest of learning, what part tipped you off to that conclusion? – B1indfire Jul 24 '15 at 16:03
  • 1
    Decompiling with ILSpy and seeing that WriteScriptCommand() is just a stub in the ISession interface, then looking at the Client constructor to see how _Session is initialized. And finally, disassembling with IDA Pro to make sure I didn't miss anything that might have been caused by a bug in ILSpy. – Jason Geffner Jul 24 '15 at 18:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.