Is AxImp broken in SP3?

  • Thread starter Thread starter Al Cooke
  • Start date Start date
A

Al Cooke

Hi,

I'm experiencing problems with AxImp.exe since installing framework
1.0 service pack 3.

When I try to run AxImp I get:
AxImp Error: Invalid Primitive Type: System.Reflection.Missing. Only
CLS compliant primitive types can be used. Consider using
CodeObjectCreateExpression.

If I run AxImp with the /source option I get:
AxImp Error: The process cannot access the file "....cs" because it is
being used by another process.

The errors only occur for one of our OCXs, the others work fine. It
definitely seems to be related to the service pack. If I reinstall the
framework it works, but if I then install SP3 it breaks again.

Is anyone else experiencing this problem? Is there a fix or
workaround?

Thanks,
Al
 
Hi Al,

I too have this problem. I guess there might be an unfavourable incantation
in our IDL files? Do let us know if you've found anything useful.

Thanks,

Ed
 
Eventually I found the problem.

On my control I had a couple of methods that accepted optional boolean
parameters but I hadn't explicitly specified a default value. Setting
a default value of False solved it! This only seems to be an issue
with booleans. I've got integers, doubles and objects with no default
values and they work OK.

Hope this helps!

Al
 
That worked for me too - thanks lots!

Ed

Al Cooke said:
Eventually I found the problem.

On my control I had a couple of methods that accepted optional boolean
parameters but I hadn't explicitly specified a default value. Setting
a default value of False solved it! This only seems to be an issue
with booleans. I've got integers, doubles and objects with no default
values and they work OK.

Hope this helps!

Al
Click to expand...
 
I too am experiencing this problem. Running aximp.exe on a particular .ocx
works fine with .net 1.1, but after applying .net 1.1 sp1, aximp.exe reports
the following errors on the same .ocx:

AxImp Error: Invalid Primitive Type: System.Reflection.Missing. Only CLS
complia
nt primitive types can be used. Consider using CodeObjectCreateExpression.

If I run aximp.exe with the /source switch, it reports:

AxImp Error: The process cannot access the file <autogenerated C# file path>
because it is being used by another process.

Examining the .cs file created by aximp reveals a premature EOF; it cuts off
in the middle of a function declaration.

I don't have any control over the interface of this .ocx so I can't use the
same method to "solve" the problem. It seems a bug was
introduced/reintroduced in .net 1.1 sp 1.
 
Back
Top