> Tamir,
>
> If you are using a COM component, then you will need to make sure that
> the COM component is installed on the other machine. You can't just take
> the wrapper (which is what TLBIMP creates) and use that, the COM component
> needs to be installed as well.
>
> Hope this helps.
>
>
> --
> - Nicholas Paldino [.NET/C# MVP]
> - mvp@spam.guard.caspershouse.com
>
> "Tamir Khason" <tamir-NOSPAM@tcon-NOSPAM.co.il> wrote in message
> news:u8sUIWptEHA.3460@TK2MSFTNGP15.phx.gbl...
>> OK, Got a problem, but not a solution
>> I have in this application some Interoped COM. While REMOVING this (let's
>> say FooCOMLib.dll) when leave the original FooCOM.dll in solution works
>> fine (of couse not module using this COM, but when return it the
>> application on prod machine exits straignt after loading.
>> The FooCOMLib.dll created with tlbImp and signed (as all other assemblies
>> (including interops) with strong key.
>>
>> Once more, the SAME program working fine on Dev enviroment.
>> FooCOM.dll (original) is registered.
>>
>> PLEASE HELP
>>
>> --
>> Tamir Khason
>> You want dot.NET? Just ask:
>> "Please, www.dotnet.us "
>>
>> "Tamir Khason" <tamir-NOSPAM@tcon-NOSPAM.co.il> wrote in message
>> news:OCvoO4otEHA.2876@TK2MSFTNGP14.phx.gbl...
>>> Nothing about it
>>> Other ideas....
>>> It got to be REALLY problem for deployment...
>>>
>>> --
>>> Tamir Khason
>>> You want dot.NET? Just ask:
>>> "Please, www.dotnet.us "
>>>
>>> "Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
>>> news:MPG.1be04904d5fec88d98b755@msnews.microsoft.com...
>>>> Tamir Khason <tamir-NOSPAM@tcon-NOSPAM.co.il> wrote:
>>>>> What the difference between (from assemblies point of view) computer
>>>>> with
>>>>> and without VS2003??
>>>>
>>>> I don't know, to be honest. You could look in the GAC of both
>>>> machines...
>>>>
>>>> --
>>>> Jon Skeet - <skeet@pobox.com>
>>>> http://www.pobox.com/~skeet
>>>> If replying to the group, please do not mail me too
>>>
>>>
>>
>>
>
>