|
Home > Archive > BizTalk Server Applications Integration > June 2004 > Generated BTSComponentsLib.dll doesnt work
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Generated BTSComponentsLib.dll doesnt work
|
|
| ram_kri 2004-06-01, 5:01 pm |
| Hi Guys,
I have used "TlbImp" utility to create BTSComponentsLib.dll using the
btscomplib.tlb and a .snk file that I have generated. After I have
generated I wanted to refer it in my project but it doesnt seem to be
working. Its not giving me the "IBTSAppIntegration" infact I am not able
to see "Microsoft.BizTalk.BTSComponentsLib" namespace at all in my c# file
in VS.NET.
I noticed a situation here, When I take the BTSComponentsLib.dll from
BizTalk Toolkit 2002 and copy it into the Bin/debug folder of my
application then I see the "Microsoft.BizTalk.BTSComponentsLib" namespace.
But when I use the one that I have generated it doesnt work. Why ?
I even have tried to refer btscomplib.tlb directly into my project and
build it, it has generated a dll called "Interop.BTSComponentsLib.dll" in
the bin\debug folder but even this doesnt seem to be working. Why ?
A difference that I noticed between the BTSComponentsLib.dll that I have
generated and the one that comes along with BizTalkServer 2002 toolkit is
that the one that comes with toolkit is of size 10K and the one that I
have generated is of the size 5K.
Why is this happening ?
Have a nice day.
Regards,
kris
| |
| Jeff Lynch 2004-06-02, 11:11 am |
| When you setup the BizTalk Server 2002 .NET Toolkit the required assemblies
should have been added to your GAC (Global Assembly Cache). Run the
"setup_toolkit.cmd" file found in the "NET Toolkit" directory where you
installed BizTalk Server 2002. You may need to modify this file if you are
using VS.NET 2003 so that it uses the correct version of the .NET Framework.
Once this is run the Microsoft.BizTalk.BTSComponentsLib namespace will be
available to any VS.NET solution.
Jeff Lynch
"A BizTalk Enthusiast"
"ram_kri" <ram_kri@yahoo.com> wrote in message
news:6c6162971c637c9f375f690744016091@lo
calhost.talkaboutsoftware.com...
> Hi Guys,
> I have used "TlbImp" utility to create BTSComponentsLib.dll using the
> btscomplib.tlb and a .snk file that I have generated. After I have
> generated I wanted to refer it in my project but it doesnt seem to be
> working. Its not giving me the "IBTSAppIntegration" infact I am not able
> to see "Microsoft.BizTalk.BTSComponentsLib" namespace at all in my c# file
> in VS.NET.
> I noticed a situation here, When I take the BTSComponentsLib.dll from
> BizTalk Toolkit 2002 and copy it into the Bin/debug folder of my
> application then I see the "Microsoft.BizTalk.BTSComponentsLib" namespace.
> But when I use the one that I have generated it doesnt work. Why ?
> I even have tried to refer btscomplib.tlb directly into my project and
> build it, it has generated a dll called "Interop.BTSComponentsLib.dll" in
> the bin\debug folder but even this doesnt seem to be working. Why ?
> A difference that I noticed between the BTSComponentsLib.dll that I have
> generated and the one that comes along with BizTalkServer 2002 toolkit is
> that the one that comes with toolkit is of size 10K and the one that I
> have generated is of the size 5K.
> Why is this happening ?
> Have a nice day.
>
> Regards,
> kris
>
| |
| Nick Malik 2004-06-04, 11:56 pm |
| Hi Kris,
Clearly, you've discovered why Microsoft released the toolkit... because the
tools that come with the .NET Framework are not sufficiently tuned to
produce working interop libraries by themselves.
So, what's the problem with using the toolkit?
--- Nick
"ram_kri" <ram_kri@yahoo.com> wrote in message
news:6c6162971c637c9f375f690744016091@lo
calhost.talkaboutsoftware.com...
> Hi Guys,
> I have used "TlbImp" utility to create BTSComponentsLib.dll using the
> btscomplib.tlb and a .snk file that I have generated. After I have
> generated I wanted to refer it in my project but it doesnt seem to be
> working. Its not giving me the "IBTSAppIntegration" infact I am not able
> to see "Microsoft.BizTalk.BTSComponentsLib" namespace at all in my c# file
> in VS.NET.
> I noticed a situation here, When I take the BTSComponentsLib.dll from
> BizTalk Toolkit 2002 and copy it into the Bin/debug folder of my
> application then I see the "Microsoft.BizTalk.BTSComponentsLib" namespace.
> But when I use the one that I have generated it doesnt work. Why ?
> I even have tried to refer btscomplib.tlb directly into my project and
> build it, it has generated a dll called "Interop.BTSComponentsLib.dll" in
> the bin\debug folder but even this doesnt seem to be working. Why ?
> A difference that I noticed between the BTSComponentsLib.dll that I have
> generated and the one that comes along with BizTalkServer 2002 toolkit is
> that the one that comes with toolkit is of size 10K and the one that I
> have generated is of the size 5K.
> Why is this happening ?
> Have a nice day.
>
> Regards,
> kris
>
| |
| Niklas E 2004-06-06, 4:53 pm |
| I remember that there is a bug in one of the pre-compiled interops in the
toolkit and that you needed to alter it for VS.net 2003. Strange that MS
hasn't made one for VS.net 2003 as well? Now every developer has to use
their time to make these hacks themselves.
The bug that you need to re-compile yourself is in the following method:
public void setParams
in this method it is missing this row:
this.EnvelopeName=sEnvelopeName;
The code you need to recompile is in this folder:
[ProgramFiles]\Microsoft BizTalk Server\NET Toolkit\Runtime Callable
Wrappers\BTSInterchange\BTSInterchange.cs
I told Microsoft about this bug in june 2003. Perhaps they have updated the
toolkit since then? I haven't been using bt2002 since last summer so I am
not updated on this...
Anyone from Microsoft who knows if there is an updated .NET Toolkit with
this bug-fix and VS.Net 2003 released or to be released?
Best regards
Niklas E
"Nick Malik" <nickmalik@hotmail.nospam.com> wrote in message
news:QO9wc.4674$4S5.2971@attbi_s52...
> Hi Kris,
>
> Clearly, you've discovered why Microsoft released the toolkit... because
the
> tools that come with the .NET Framework are not sufficiently tuned to
> produce working interop libraries by themselves.
>
> So, what's the problem with using the toolkit?
>
> --- Nick
>
> "ram_kri" <ram_kri@yahoo.com> wrote in message
> news:6c6162971c637c9f375f690744016091@lo
calhost.talkaboutsoftware.com...
file[vbcol=seagreen]
namespace.[vbcol=seagreen]
in[vbcol=seagreen]
is[vbcol=seagreen]
>
>
| |
|
| Hi guys I have a similar problem...
I get this when I complie my AIC..
****************************************
*
COM Interop registration failed. Type library exporter encountered an error while processing 'BTS2002AIC.BTS2002DEV, BTS2002AIC'. Error: Referenced type is defined in managed component, which is imported from a type library that could not be loaded (type
: Microsoft.BizTalk.BTSComponentsLib.IBTSAppIntegration; component: c:\windows\assembly\gac\btscomponentslib
\1.0.0.0__31bf3856ad364e35\btscomponentslib.dll).
****************************************
*
I have no problems to put BTSComponentsLib in the GAC.(I have run setup_toolkit.cmd)
I can compile the project if I set "Register for COM Interop" to "false" in project poperties.
I have vs2003 on a w2003 server with .net framework v1.1.4322
Does anyone know what this means? I haven't worked with COM interop before.
"Niklas E" wrote:
> I remember that there is a bug in one of the pre-compiled interops in the
> toolkit and that you needed to alter it for VS.net 2003. Strange that MS
> hasn't made one for VS.net 2003 as well? Now every developer has to use
> their time to make these hacks themselves.
>
> The bug that you need to re-compile yourself is in the following method:
> public void setParams
>
> in this method it is missing this row:
> this.EnvelopeName=sEnvelopeName;
>
> The code you need to recompile is in this folder:
> [ProgramFiles]\Microsoft BizTalk Server\NET Toolkit\Runtime Callable
> Wrappers\BTSInterchange\BTSInterchange.cs
>
> I told Microsoft about this bug in june 2003. Perhaps they have updated the
> toolkit since then? I haven't been using bt2002 since last summer so I am
> not updated on this...
>
> Anyone from Microsoft who knows if there is an updated .NET Toolkit with
> this bug-fix and VS.Net 2003 released or to be released?
>
> Best regards
> Niklas E
>
>
> "Nick Malik" <nickmalik@hotmail.nospam.com> wrote in message
> news:QO9wc.4674$4S5.2971@attbi_s52...
> the
> file
> namespace.
> in
> is
>
>
>
|
|
|
|
|