| View previous topic :: View next topic |
| Author |
Message |
Erick Sasse Guest
|
Posted: Wed Jun 16, 2004 7:58 pm Post subject: Deploy VCL.NET App |
|
|
I've created a hello world using WinForms. Copied to a remote shared
folder and it works.
Then I've created a hello world using VCL.NET, copied to a remote
shared folder and when I try to run it in my machine (D8 and everything
installed) I get a System.TypeInitializationException. It is only a
form with a button and a call to ShowMessage.
If I run it locally, it works.
What's wrong?
--
Erick Sasse
|
|
| Back to top |
|
 |
Marc Rohloff [TeamB] Guest
|
Posted: Thu Jun 17, 2004 3:13 am Post subject: Re: Deploy VCL.NET App |
|
|
On 16 Jun 2004 12:58:07 -0700, Erick Sasse wrote:
| Quote: | Then I've created a hello world using VCL.NET, copied to a remote
shared folder and when I try to run it in my machine (D8 and everything
installed) I get a System.TypeInitializationException. It is only a
form with a button and a call to ShowMessage.
|
What is the text of the exception?
--
Marc Rohloff
marc rohloff at myrealbox dot com
|
|
| Back to top |
|
 |
Erick Sasse Guest
|
Posted: Thu Jun 17, 2004 12:21 pm Post subject: Re: Deploy VCL.NET App |
|
|
When I try to run the app, I'm told that a exception ocurred (withou
showing the text) and if I want do debug it using CLR Debugger or
VS.NET Debugger.
When I start VS.NET Debugger I get a text like "Additional information:
The type initialization from "Project2.Unit" raised an exception". The
original text is in portuguese, so I translated to english.
--
Erick Sasse
|
|
| Back to top |
|
 |
Marc Rohloff [TeamB] Guest
|
Posted: Thu Jun 17, 2004 11:59 pm Post subject: Re: Deploy VCL.NET App |
|
|
On 17 Jun 2004 05:21:15 -0700, Erick Sasse wrote:
| Quote: | When I try to run the app, I'm told that a exception ocurred (withou
showing the text) and if I want do debug it using CLR Debugger or
VS.NET Debugger.
|
Applications run off the network have different security permissions
to those for applications run off a local drive. The VCL runs some
code which requires higher security permissions.
The easiest is to run the code off a local drive. Otherwise you have
to give security rights to applications running off the network or to
your application.
--
Marc Rohloff
marc rohloff at myrealbox dot com
|
|
| Back to top |
|
 |
Erick Sasse Guest
|
Posted: Fri Jun 18, 2004 12:36 pm Post subject: Re: Deploy VCL.NET App |
|
|
Marc Rohloff [TeamB] wrote:
| Quote: | The easiest is to run the code off a local drive. Otherwise you have
to give security rights to applications running off the network or to
your application.
|
Thanks Marc, I was trying to modify the security on the server, but now
I got it right modifying the security locally.
--
Erick Sasse
|
|
| Back to top |
|
 |
TObject Guest
|
Posted: Tue Jun 22, 2004 10:57 pm Post subject: Re: Deploy VCL.NET App |
|
|
"Erick Sasse" <esasse (AT) mandic (DOT) com.br> wrote
| Quote: | Then I've created a hello world using VCL.NET, copied to a remote
shared folder and when I try to run it in my machine (D8 and everything
installed) I get a System.TypeInitializationException. It is only a
form with a button and a call to ShowMessage.
If I run it locally, it works.
What's wrong?
|
You need to copy the following dll libraries to the same folder
where your application resides on the remote machine
(or to the remote machine GAC):
Borland.Vcl.dll
Borland.Delphi.dll
Borland.VclRtl.dll
Possibly some more, but for a "Hello Word" application
those three should be plenty.
|
|
| Back to top |
|
 |
TObject Guest
|
Posted: Wed Jun 23, 2004 10:41 pm Post subject: Re: Deploy VCL.NET App |
|
|
"Erick Sasse" <esasse (AT) mandic (DOT) com.br> wrote
| Quote: | No, it was a security problem. It is already solved.
|
Cool! What did you have to do to solve the security problem?
|
|
| Back to top |
|
 |
Erick Sasse Guest
|
Posted: Thu Jun 24, 2004 12:13 am Post subject: Re: Deploy VCL.NET App |
|
|
TObject wrote:
| Quote: | You need to copy the following dll libraries to the same folder
where your application resides on the remote machine
(or to the remote machine GAC):
Borland.Vcl.dll
Borland.Delphi.dll
Borland.VclRtl.dll
|
No, it was a security problem. It is already solved.
Thanks anyway! :)
--
Erick Sasse
|
|
| Back to top |
|
 |
|