RE: [DUG] Distributing D8 .NET Apps

Tue, 07 Sep 2004 20:44:16 -0700

Title: Message
Congrats
 

Jason Saggers
ESecure Team
Expert Solution Providers

 

From: Jeremy Coulter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 8 September 2004 3:41 p.m.
To: Jason Saggers
Subject: RE: [DUG] Distributing D8 .NET Apps

HIZZAR !!! FINALLY its working.
I have finally caught the flu the rest of my family has/had and its not making me thingk too straight.
I was passing in the wrong URL....oh thats just embarising....yet forgivible since I am sick :-D
 
Jeremy
-----Original Message-----
From: Jason Saggers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 8 September 2004 11:07
To: [EMAIL PROTECTED]
Subject: RE: [DUG] Distributing D8 .NET Apps

Ok - I have a rather complex webservice running here.
 
 
The breakdown is
 
rootfolder of webservice
 
    *.asmx files
    DelphiProvider.dll
 
bin
    Compiled dll of the Webserver
 
 
 
 
If you are running on a 2003 Server IIS 6 there are some settings in the Configuration that also needs changing.
 
    An ASP.NET app will not run unless the Virtual Directory/Directory it is in is marked as an Application in the IIS Setup
 
 

Jason Saggers
ESecure Team
Expert Solution Providers

 

From: Jeremy Coulter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 8 September 2004 9:36 a.m.
To: Jason Saggers
Subject: RE: [DUG] Distributing D8 .NET Apps

Hmm....welll I am not sure.
I thought, so long as it was in the "GAC" dir it would be ok. But then something rang a bell about haveing the files in a BIN dir in the wwwroot folder too....agh...I am just confused now :-D
The error I get is This is just a webservice BTW that says hello or something....extreamly complex ;-) :-
 

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
-----Original Message-----
From: Jason Saggers [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 8 September 2004 08:19
To: [EMAIL PROTECTED]; NZ Borland Developers Group - Delphi List
Subject: RE: [DUG] Distributing D8 .NET Apps

Hi Jeremy,
 
    I have found that with the .NET Library Installed on the PC, the only things I needed to put on the PC was the binary complied, and any supported library I have created e.g.  I my case the interop libraries.
 
    THe only time I had to add any of the Borland Stuff was for the ASP.NET apps and that just requireds a single dll put in the same directory as the application to support the delphi language for the ASP.NET.
 
    Admittly I have been creating Window Form Apps and Service not Borland VCL Apps.
 
    I would suggest the Borland .dll for the .net Library can ether be put in the persistant directory, or in the application directory.
 

Jason Saggers
ESecure Team
Expert Solution Providers

 

From: Jeremy Coulter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 7 September 2004 9:47 p.m.
To: [EMAIL PROTECTED]
Subject: [DUG] Distributing D8 .NET Apps

Hi All.
I raised this question way back when D8 first came out, and pretty much I dont think anyone really new at the time.
But now I have got a .NET app ready, I have installed teh .NET SDK on the server, but my app. didnt run, and I suspect it is because it doesnt know about about D8.
Is this assumption right? and if so, what do I need to do? I assume I need to put the delphi or rather the Borland .NET DLLs on the server, but do I need to register something or whatever?
I found the Borland deploy.txt a bit vauge. It just says which dlls to distribute, but not how to do it etc.
 
Anyone help? I looked on the web, but didnt seem to find anything, but that might just be my search criteria.
 
Jeremy
_______________________________________________
Delphi mailing list
[EMAIL PROTECTED]
http://ns3.123.co.nz/mailman/listinfo/delphi

Reply via email to