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

Moving to a new development computer

P: n/a
Hi,

I am using Visual Studio 2003.

After moving my project to a new development computer my project compiles
and works on the new development computer but the program will not work when
I test it on the client's computer. . I checked and both old and new
development computers have the same list of references.

When I switch out only the exe that was compiled using the same project code
on the old dev computer the client installation likes that exe. What am I
missing on getting the new development computer configured to compile like
the old one?

Thanks!

Bob
Jul 21 '08 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Thanks.

The operating system is WinXP Pro on old and new dev computer.

The exe on the client computer fails with the following message...

++++++++++++++++++++
ProgamName.exe - Common Language Runtime Debugging Services

Application has generated an exception that could not be handled.

Process id=0xce4 (3300), Thread id=0xa8 (680).

Click OK to terminate the application.
Click CANCEL to debug the application.
++++++++++++++++++++++++++

When it has failed this fast in the past it was always a missing reference
or dll needed at load time. Could it be that I just need to go back and
reapply all my references??

Thanks so much!

Bob

"Cor Ligthert[MVP]" wrote:
Bob,

To make it more clear for us, what is the OS from the new development
computer, is that the same as the old one?

(And what do you exactly mean with not working, is it in the program list
but dies without giving any information?)

Cor

"BobAchgill" <Bo********@discussions.microsoft.comschreef in bericht
news:34**********************************@microsof t.com...
Hi,

I am using Visual Studio 2003.

After moving my project to a new development computer my project compiles
and works on the new development computer but the program will not work
when
I test it on the client's computer. . I checked and both old and new
development computers have the same list of references.

When I switch out only the exe that was compiled using the same project
code
on the old dev computer the client installation likes that exe. What am I
missing on getting the new development computer configured to compile like
the old one?

Thanks!

Bob
Jul 21 '08 #2

P: n/a
Bob,

Looks to me like the target machine might be missing .Net Framework 1.1.
You might want to re-install (or install if missing) that version of the
framework.

HTH,

-b

"BobAchgill" <Bo********@discussions.microsoft.comwrote in message
news:49**********************************@microsof t.com...
Thanks.

The operating system is WinXP Pro on old and new dev computer.

The exe on the client computer fails with the following message...

++++++++++++++++++++
ProgamName.exe - Common Language Runtime Debugging Services

Application has generated an exception that could not be handled.

Process id=0xce4 (3300), Thread id=0xa8 (680).

Click OK to terminate the application.
Click CANCEL to debug the application.
++++++++++++++++++++++++++

When it has failed this fast in the past it was always a missing reference
or dll needed at load time. Could it be that I just need to go back and
reapply all my references??

Thanks so much!

Bob

"Cor Ligthert[MVP]" wrote:
>Bob,

To make it more clear for us, what is the OS from the new development
computer, is that the same as the old one?

(And what do you exactly mean with not working, is it in the program list
but dies without giving any information?)

Cor

"BobAchgill" <Bo********@discussions.microsoft.comschreef in bericht
news:34**********************************@microso ft.com...
Hi,

I am using Visual Studio 2003.

After moving my project to a new development computer my project
compiles
and works on the new development computer but the program will not
work
when
I test it on the client's computer. . I checked and both old and new
development computers have the same list of references.

When I switch out only the exe that was compiled using the same project
code
on the old dev computer the client installation likes that exe. What
am I
missing on getting the new development computer configured to compile
like
the old one?

Thanks!

Bob

Jul 22 '08 #3

P: n/a
Bruce,

The target machine runs the exe perfectly that has been compiled on the old
developement computer but fails when trying to run the exe compiled on the
new development computer. The code is compiled from the exact same project
in either case.

That leeds me to think that the problem is NOT with the target machine.

This is happening on other target machines, too.

The code compiled on the new development machine will ONLY run on right
there on the new development machine. I will double check the resources
today to see that they look the same as the old machine.

Thank you!

Bob

"Bruce W. Roeser" wrote:
Bob,

Looks to me like the target machine might be missing .Net Framework 1.1.
You might want to re-install (or install if missing) that version of the
framework.

HTH,

-b

"BobAchgill" <Bo********@discussions.microsoft.comwrote in message
news:49**********************************@microsof t.com...
Thanks.

The operating system is WinXP Pro on old and new dev computer.

The exe on the client computer fails with the following message...

++++++++++++++++++++
ProgamName.exe - Common Language Runtime Debugging Services

Application has generated an exception that could not be handled.

Process id=0xce4 (3300), Thread id=0xa8 (680).

Click OK to terminate the application.
Click CANCEL to debug the application.
++++++++++++++++++++++++++

When it has failed this fast in the past it was always a missing reference
or dll needed at load time. Could it be that I just need to go back and
reapply all my references??

Thanks so much!

Bob

"Cor Ligthert[MVP]" wrote:
Bob,

To make it more clear for us, what is the OS from the new development
computer, is that the same as the old one?

(And what do you exactly mean with not working, is it in the program list
but dies without giving any information?)

Cor

"BobAchgill" <Bo********@discussions.microsoft.comschreef in bericht
news:34**********************************@microsof t.com...
Hi,

I am using Visual Studio 2003.

After moving my project to a new development computer my project
compiles
and works on the new development computer but the program will not
work
when
I test it on the client's computer. . I checked and both old and new
development computers have the same list of references.

When I switch out only the exe that was compiled using the same project
code
on the old dev computer the client installation likes that exe. What
am I
missing on getting the new development computer configured to compile
like
the old one?

Thanks!

Bob


Jul 22 '08 #4

P: n/a
Found the problems(s).

I had not added 'copy to local' in my references when I set up the
development computer. Then when I upgraded my third party classes for FTP
and Grid the compiles would work on the new dev computer only because the
class dll were installed elsewhere on the computer.

Changing to copy to local in the references and redistributing the project
to the client machines along with the updated local dll's ... everything
works!

It is too bad .Net can give a better error statement on the client machine
when a resource issue likes this occurs. I was only able to see specifics
when I had Visual Studio installed on the client machine.

Thanks Cor and Bruce for walking me through this.

Bob
Jul 23 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.