That's a good point. For now we can limit it to AddReference and
ImportNamespace. So we probably need a new abstraction specific for script
packs.


On Thu, Mar 7, 2013 at 10:38 AM, Filip W <notifications@github.com> wrote:

> In src/ScriptCs.Contracts/IScriptPack.cs:
>
> > @@ -0,0 +1,17 @@
> > +using System;
> > +using System.Collections.Generic;
> > +using System.ComponentModel.Composition;
> > +using System.Linq;
> > +using System.Text;
> > +using Roslyn.Scripting.CSharp;
> > +
> > +namespace ScriptCs.Contracts
> > +{
> > +    [InheritedExport]
> > +    public interface IScriptPack
> > +    {
> > +        void Initialize(ISession session);
>
> should the IScriptPack implementor have access to ISession.Execute()? I
> believe he only needs ISession.AddReference()
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/scriptcs/scriptcs/pull/67/files#r3285328>
> .
>