|
| Computing.Net: Over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to sign up now, it's free! |
Windows Application Deployment
|
Original Message
|
Name: varriable@yahoo.com (by fredABOS)
Date: July 6, 2006 at 15:02:25 Pacific
Subject: Windows Application DeploymentOS: Windows XPCPU/Ram: 512Model/Manufacturer: intel |
Comment: I am about to deploy a new system I wrote for a company. It was developed in VB.net using Visual Studio 2003. I am using the MYSQL database. I installed it on their server. they just bought a windows 2003 server. I was wondering if I can deploy that windows application on the server, so everybody can access it from the server instead of having it deployed on each single machine, and when it comes to maintenance, it is a pain in the neck. Please let me know if it is possible. Fred
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: SN
Date: July 6, 2006 at 17:23:38 Pacific
|
Reply: (edit)You have a few options for deployment. If you really truly only want the program installed on the server, then you're pretty much stuck with using terminal services (ie remote desktop) for everybody to access it. However, that's a pretty crappy solution. What you really want to do is have your application updated automatically. Here are some options: 1. Package the application in an msi and use group policy to deploy it from the server. Deploying applications using group policy 2. Upgrade to visual studio 2005 and use ClickOnce to deploy and the machines will install from a URL and update themselves. 3. Write your own updater to check an xml file somewhere for updates, then use a command prompt WMI to install the new version. Which solution is best for you depends on your particular setup and how often it changes. If you're going to have regular updates to this application, probably #2 is your best bet. If you don't have the budget, then go with #3. Good luck, -SN
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: SN
Date: July 6, 2006 at 21:03:05 Pacific
|
Reply: (edit)"Write your own updater to check an xml file somewhere for updates, then use a command prompt WMI to install the new version." I meant use a command prompt OR WMI. Personally I prefer the WMI approach, but it's definitely harder than just running msiexec. Good luck, -SN
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: jhunt303
Date: July 9, 2006 at 06:50:36 Pacific
|
Reply: (edit)Yes, .net really is not the best for desktop apps. If you check your DEBUG directory, then you'll notice a nice little exe that will run from a server, aha, result... no, the .net framework has built in security preventing this from running database connections etc. Ok, I'll just give the user local-area permissions aha, .net 2 doesn't come with the permission configuration tool as standard..... ah microsoft. But, all is not lost. If you configure a batch file to copy the exe from your server to the local machines whenever there is an update then you are ok, not ideal, but it works.
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: varriable@yahoo.com (by fredABOS)
Date: July 19, 2006 at 09:52:19 Pacific
|
Reply: (edit)Is it possible to copy a file from the server to a local machine on the netwrok using DOS. Like a DOS command.
Report Offensive Follow Up For Removal
|

Post Locked
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
Go to Programming Forum Home
|
|
|