By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,333 Members | 1,022 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,333 IT Pros & Developers. It's quick & easy.

Large piecemeal application

P: n/a
I have developed a large accounting application piecemeal. . . A/R, A/P,
P/R, Inventory, G/L, etc. Uses 3 databases, 3 DLLs, and 6 EXEs.

I need to combine them so going from one EXE to another EXE isn’t a problem.
I am now using instances of both of the following code snippets:

Dim proc As New Process()
proc.StartInfo.FileName = "EXE3.exe"
proc.StartInfo.WorkingDirectory = "C:\A_VS.Net"
proc.Start()
proc.WaitForExit()
Dim sPath As String
sPath = "C:\A_VS.Net\EXE3.exe"
System.Diagnostics.Process.Start(sPath)

Unless all members are in the same directory there are problems. If I make
a change, I have to copy the new EXE member from it’s default folder to the
combine directory folder.

I am ready to create a deployment for the application and I’m not sure what
the best way to proceed is. . . Need some help.

Thanks

--
MerlinOnRockCreekInGraniteCounty
Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
=?Utf-8?B?UmljTWFyYmxl?= <Ri*******@discussions.microsoft.com> wrote in
news:00**********************************@microsof t.com:
Unless all members are in the same directory there are problems. If I
make a change, I have to copy the new EXE member from it Ts default
folder to the combine directory folder.


Just change your default build path to the combined directory output path.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/
Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.