Windows Server

Richard Ruben · Guest

I am doing some test with HIS 2004 because in the near future we want to
migrate to HIS 2004 (We are now using HIS 2000). I created a new TI Project
with a .Net assembly and imported a TLB that we already used in HIS 2000.
When I tried to register this assembly with the TI Manager en the server I
got this error message:

Progress
(5600) An Object "COMMSOLP.COMMSOLP.1", contained in the file
"\\xx\COMMSOLP.DLL", could not be installed in the Virtual Directory "Sitio
Web predeterminado/Ceder Bank". Generation of a proxy failed with
"c:\Documents and Settings\xxx\Configuraci¢n
local\Temp\SS13AE.tmp\COMMSOLP.cs(32,2046): error CS1034: Se ha excedido el
l¡mite del compilador: una l¡nea no puede tener m s de 2046 caracteres".
(Compiler limit exceeded: Line cannot exceed 2046 characters)

Finished

Seems an internal error of the compiler to me. A tried to import other TLB´s
and this went fine. What can I do to generate the proxy for this assembly?

Thanx,

DPP · Guest

Hi Richard,

I also got same exception while generating the proxy. This is an C# compiler
error and i think it came because of your TP method is having too many
parameters.

I don't think there is any readymade solution for this. So, i went to COM
client library project and imported old TLD from HIS 2000 and created the
object in HIS 2004 TI Manager. Then it went on fine.

You can also try to use the COM client library instead of .NET client library.

--
Thanks,
DPP

"Richard Ruben" wrote:

Neil Pike · Guest

Richard,

Seems this is not just HIS related as other folks doing C# stuff are hitting
the same issue with generated code - see below.

------

Thanks much for the reply. After some fiddling, we found that the statements
causing the problem are the method declarations themselves. Apparently, if the
WSDL does not define a top-level "container" for a whole bunch of elements all
at the top level, wsdl.exe makes each element an argument to the method. This
is of course nice normally. However, we have so many elements in the XSD that
the method declaration is too long. We removed the namespace portions of the
XmlElementAttribute attributes for each arg and we're below the limit on most
of them. Of course, we have to "hack" the auto-generated code for this which
kinda stinks.

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

Rob Beardsworth [MSFT] · Guest

Yes, this is a known problem, and the suggested solution is to make up some
Structures in Designer and have them as parameters to the routine. Or you
can call your parameters P1 etc :-)

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1