Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 195
  • Last Modified:

How to move finished code to another computer?

I finished writing a program and I need to move it to another computer to run. How do I do this?

I copied the exe file over, and it errored with need mscoree.dll. I copied that over and I think I need to register it?

Basically what do I need to copy, and where does it go?

thanks
Matt
0
mattdunlap
Asked:
mattdunlap
1 Solution
 
cookreCommented:
0
 
mattdunlapAuthor Commented:
Seen it...I Think need to learn how to use the packaging wizard?

I think this is what I needed:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/modcore/html/deovrDeployingYourSolution.asp

Thanks for your help
0
 
mattdunlapAuthor Commented:
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
cookreCommented:
I thought the problem was just that particular DLL.

As to the general issue of distribution:

If at all possible, I make my executables entirely self-contained (static link) - you never know what sort of crap is or isn't on a target box.

Although my user base is around 120,000 semi-rigidly controlled desktops going to a mix of MS and NetWare servers, there is enough variation to worry about some things.  For example, until we're all on Win2K, I write to Winsock 1.1 only - that let's me run on 9x, NT, and 2K (we don't do XP, yet).

For complex installs (for example, re-packaging IE for a silent install), we've managed to live with Wise.

Just a few general thoughts - other folks out there are bound to add their observations too.

0
 
SunBowCommented:
I dunno on your links. 1st step is to identify all targets. The dll's, ocx's, et al required can be different by OS and more.

2) Make package, using tools to autoload whatever 'extras' may be needed this way:

> If at all possible, I make my executables entirely self-contained (static link)

3) do not make user(s) have to locate more than one file, or research FAQs, or update pages, IMO

4) beware of backdating users, or upgrading them inappropriately, ex:

> to Winsock

5) know your audience
0
 
mattdunlapAuthor Commented:
I think I asked the wrong question?

I found that in VS.net they have the deployment project. I used that it packaged the project. I'm using the beta version and it says I need to upgrade a service pack that has the new microsoft installer, but other than that error it seemed to package it nicely.
0
 
nico5038Commented:

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
 - PAQ'd and pts refunded
Please leave any comments here within the
next seven days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER !

Nic;o)
0
 
moduloCommented:
Finalized as proposed

modulo

Community Support Moderator
Experts Exchange
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now