Re: Calling a .Net console app from IBM i

[Mike Wills <mike@xxxxxxxxxxxx>]

Keep on asking. About 90% of my time now is .NET programming connecting to
the IBM i.
--
Mike Wills
http://mikewills.me


On Fri, Jul 6, 2012 at 8:42 AM, Bryce Martin <bmartin@xxxxxxxxxxxxxxxxxx>wrote:

> So here is how I have deployed my console application to our windows
> server...
>
> As was suggested, I did a Release build.  There are lots of things
> thrown into the bin/release folder, but for this project there were only
> 3 things I needed.  First, I needed the TaxUpdate.exe.  This is my
> actual console application.  The next thing I needed was the
> TaxUpdate.exe.config.  This is basically the App.config from the
> project.  For me, this contained my connection string for my Entity
> Framework connection to the other EF project I had referenced.  The last
> thing I needed was my TestModel.dll which is the build of my EF project.
> So, if I didn't have this EF project, you would only need the .exe and
> its corresponding .config file (and I'm not sure if the .config would be
> needed in really simple cases, I will test this at a later time).  Then
> since I was referencing another project in my solution, I needed to grab
> that projects .dll in this case.  I just copied and pasted them over an
> RDP to the windows server in a manageable path structure that I
> constructed for further integrations in the weeks to come.
>
> Thanks everyone for your help.  I know I'm new to the .Net world, but
> I'm willing to experiment and bounce ideas for different scenarios with
> this list if you guys have any questions.
>
> Thank You
> Bryce Martin
> National Ticket Company
> 570-672-2900 ext. 226
>
> -----Original Message-----
> From: systemidotnet-bounces@xxxxxxxxxxxx
> [mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
> Sent: Saturday, June 30, 2012 1:42 PM
> To: systemidotnet@xxxxxxxxxxxx
> Subject: Re: [SystemiDotNet] Calling a .Net console app from IBM i
>
> OK still confused :-)
>
> It sounds like you're describing a standard EXE deployed using an xcopy
> deployment where you simply copy all files.
>
> That's how we do deployments with most .Net apps.
>
> That's different than the one-click deploy from my understanding.
>
> I thought one-click deployment was meant to be able to post an app on a
> web site and have it auto-download the whole thing without an installer.
>
> Regards,
> Richard Schoen
> RJS Software Systems Inc.
> Where Information Meets Innovation
> Document Management, Workflow, Report Delivery, Forms and Business
> Intelligence
> Email: richard@xxxxxxxxxxxxxxx
> Web Site: http://www.rjssoftware.com
> Tel: (952) 736-5800
> Fax: (952) 736-5801
> Toll Free: (888) RJSSOFT
>
>
> ------------------------------
>
> message: 5
> date: Fri, 29 Jun 2012 15:29:58 -0500
> from: Mike Wills <mike@xxxxxxxxxxxx>
> subject: Re: [SystemiDotNet] Calling a .Net console app from IBM i
>
> In your project folder under /bin/Debug.
>
> So for one of my projects, I go to C:\Documents and Settings\USER\My
> Documents\Visual Studio
> 2010\Projects\SendToInternet\PullFromInternet\bin\Debug. (There is also
> a "Release" if you compile it as such.
>
> In there I have the calling program PullFromInternet.exe. There are
> other files in there too that are most likely needed as well. Put them
> all in a location on the target computer and voila! It works!
>
> We do this to schedule tasks on Windows servers.
>
> --
> Mike Wills
> http://mikewills.me
>
>
> --
> This is the .net use with the System i (SystemiDotNet) mailing list To
> post a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
> or email: SystemiDotNet-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> http://archive.midrange.com/systemidotnet.
> --
> This is the .net use with the System i (SystemiDotNet) mailing list
> To post a message email: SystemiDotNet@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
> or email: SystemiDotNet-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/systemidotnet.