Strange problem on runtime

  • Thread starter Thread starter Tamir Khason
  • Start date Start date
T

Tamir Khason

I have an Application
While running it on computer (just runtime) WITH VS [not development] works
fine, BUT
running it on other computer without VS it just do not want to run (exit
with code 0 [OK])
What can be problem?
 
Tamir Khason said:
I have an Application
While running it on computer (just runtime) WITH VS [not development] works
fine, BUT
running it on other computer without VS it just do not want to run (exit
with code 0 [OK])
What can be problem?
Click to expand...

Have you installed the .NET framework on the other computer?
 
sure ;) the same version.
Maybe GAC?? All assemblies are strong key?..

--
Tamir Khason
You want dot.NET? Just ask:
"Please, www.dotnet.us "

Jon Skeet said:
Tamir Khason said:
I have an Application
While running it on computer (just runtime) WITH VS [not development]
works
fine, BUT
running it on other computer without VS it just do not want to run (exit
with code 0 [OK])
What can be problem?
Click to expand...

Have you installed the .NET framework on the other computer?
Click to expand...
 
Tamir Khason said:
sure ;) the same version.
Maybe GAC?? All assemblies are strong key?..
Click to expand...

Hard to say without knowing more about the application. Have you tried
a tiny "hello world" application?
 
What the difference between (from assemblies point of view) computer with
and without VS2003??
 
Tamir Khason said:
What the difference between (from assemblies point of view) computer with
and without VS2003??
Click to expand...

I don't know, to be honest. You could look in the GAC of both
machines...
 
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 said:
Nothing about it
Other ideas....
It got to be REALLY problem for deployment...
Click to expand...
 
Tamir Khason said:
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.
Click to expand...

Ah, right. Where is FooCOM.dll on the machine which isn't working? You
might want to ask in the interop newsgroup for more answers - I'm
afraid I'm not very hot on interop.
 
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]
- (e-mail address removed)

Tamir Khason said:
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
Click to expand...
 
Yes, I know this.
FooCOM.dll (original com) is in the same directory with interop and
registered by regsvr32
I thin kit might be problem with statics/dynamics FooCOM.dll creation,
inspite of in dependency walker i can not see anything missing

advice?

--
Tamir Khason
You want dot.NET? Just ask:
"Please, www.dotnet.us "

Nicholas Paldino said:
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]
- (e-mail address removed)

Tamir Khason said:
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
Click to expand...
Click to expand...
 
Tamir Khason said:
Yes, I know this.
FooCOM.dll (original com) is in the same directory with interop and
registered by regsvr32
I thin kit might be problem with statics/dynamics FooCOM.dll creation,
inspite of in dependency walker i can not see anything missing

advice?
Click to expand...

As I said before, I advise you ask in the interop group.
 
Thanks for Jon's quick response.

Hi Tamir,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you app could not run properly on other
machine that the exported assembly was not installed. If there is any
misunderstanding, please feel free to let me know.

Could you try to use regasm.exe to register the dll instead of
regsvr32.exe? regasm.exe allows COM clients to create .NET Framework
classes transparently. For more information, please check the following
link:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/htm
l/cpgrfassemblyregistrationtoolregasmexe.asp

HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Back
Top