03-03-04 04:37 PM
This is working for us to.
If we follow the exact pattern of this sample, the DateFunctoidNet functoid
become available in the
BizTalk Mapper.
But it's not what we want.
We want to be able to design ours own functoid using ours develo tools ie
VS2003 and framework 1.1.
In regard with this, all seems to be OK.
The project conversion, the compilation, the installation/registration are
done without error.
But at end, we where unable to access ours functoid from BizTalk Mapper,
and we have no indication why.
--
Yves Tourchot
(ROT13 & rem spam filter to reply)
qriargfby_erzfcnz@flzcngvpb.pn
"Conny Blom?r" <conny.blomer@wmdata.se> wrote in message
news:6f9dfc56.0402270625.15338c86@posting.google.com...
> The example-functioid apperas after that "DateFunctoidNet.reg"-file
> has been executed. This is what i did;
> 1.
> C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\regasm
> C:\Temp\DateFunctoidNet\BTSCannedFunctoi
dsLib.dll
>
> 2.
> C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\gacutil /i
> C:\Temp\DateFunctoidNet\BTSCannedFunctoi
dsLib.dll
>
> 3.
> regsvr32 AssemblyPathFinderProxy.dll (modify the path)
>
> 4.
> C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\csc /r:system.dll
> / r:C:\Temp\DateFunctoidNet\BTSCannedFunct
oidsLib.dll /d:DEBUG /debug
> /define:DEBUG=1 /target:library
> / out:C:\Temp\DateFunctoidNet\DateFunctoid
Net.dll
> / win32res:C:\Temp\DateFunctoidNet\datefun
ctoidnet.res
> C:\Temp\DateFunctoidNet\*.cs
>
> 5.
> C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\gacutil /i
> C:\Temp\DateFunctoidNet\datefunctoidnet.dll
>
> 6.
> C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\regasm
> C:\Temp\DateFunctoidNet\datefunctoidnet.dll /verbose
> / tlb:C:\Temp\DateFunctoidNet\datefunctoid
net.tlb
> pause:
>
> 7.
> Run "DateFunctoidNet.reg"
>
> Regards Conny Blomér
>
>
> "Yves Tourchot" <qriargfby_erzfcnz@flzcngvpb.pn> wrote in message
news:<cruUb.19878$9U5.1082498@news20.bellglobal.com>...
the
[ Post a follow-up to this message ]
|