Python and C#
Cameron Laird
claird at lairds.us
Mon Oct 4 14:08:03 EDT 2004
More information about the Python-list mailing list
Mon Oct 4 14:08:03 EDT 2004
- Previous message (by thread): cgi long running jobs
- Next message (by thread): Python and C#
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <BL6dnev5xezS4_zcRVn-vA at comcast.com>, Larry Bates <lbates at syscononline.com> wrote: > > Looking for advice on this as a course of action. Obviously, >> I'm not doing this for fun, but for some reasons that are >> supported by base workaday considerations. Will this work? >> What are the biggest hassles in making it work? Any >> pitfalls? > >Sure this will work. You can call COM server code from Python >no matter what the COM server is written in. I've written >COM servers in Python and called from Python, VB, PowerBuilder, >etc. I've also called COM servers written in other languages. > >> >> If I get this to work well, next I want to make it easy for >> users to install and run the apps. I haven't tried to >> package any python apps in about a year. Which packaging >> package is better now for this -- py2exe, McMillan's, or >> something else? I want the end-users with no python on >> their Windows machine to run a simple and non-descript >> installer and then be up and running with my app, no >> problems. > >I like the combination of py2exe and Inno Setup. py2exe >create standalone code and Inno to create a distributable >installer. . . . 'Know what *I* think'll be the biggest surprise? 'Getting the run-time right for the C# part. You're developing the C# server under WinXP, right, but some users will try to run it under Win98? *That* might be a bit of an adventure ...
- Previous message (by thread): cgi long running jobs
- Next message (by thread): Python and C#
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list