Hi Dante,
thx for your reply. I see I need to be more specific. When I run the AXIMP task as defined in NANT it only created one file, but not two. So I used <exec> to run it through the command shell. Providing no switches and no output file name a OCX named wmplib.dll would result in Axwmplib.dll and (same name!) wmplib.dll using AXIMP and AxInterop.wmplib.dll and Interop.wmplib.dll in VS.
Technically spoken this question doesn't belong here, since it is VS vs. .NET Framework tools. So what would be the right place to ask?
:-) stw
[EMAIL PROTECTED] wrote on 23/02/2005 02:32:43:
> I don't think you are missing switches. As a matter of fact, I just
> emailed Gert directly yesterday about this issue. There is even a
> comment in the code that says it is being assumed that Interop.*
> will suffice and the call to AxImp uses the "/rcw" parameter. The
> work around I found so far is to run the exact same AxImp command
> without the "/rcw" parameter, this forces the creation of the
> AxInterop.* file.
>
> I don't know enough to say that the rcw parameter should just not be
> used but other than performance, I don't see how it would hurt to
> not make the assumption I mentioned above and never use the rcw
> parameter. Gert, would you enlighten us?? :-)
>
> Thanks!
>
>
> [EMAIL PROTECTED] wrote:
>
> Hi there,
>
> I want my software to be strong named. So my NANT task runs AXIMP to
> import a wrapper for an ActiveX Control. However the result is
> different from the interaction in Visual Studio. In VS I get 2
> files: AxInterop.wmplib.dll and Interop.wmplib.dll. In AXIMP I get
> Axwmplib.dll and wmplib.dll and some differences in the content (get
> some errors on execution). Am I missing switches?
>
> :-? stw
- Re: [Nant-users] Difference between importing a OCX in VS an... stephan
