Running .NET 2.0 Debug builds

[Martin]

Hi there,
after experimenting a bit with VS2005 and .NET forms, I learned
that .NET applications that are compiled as debug build don't run
on machines that don't have VS (or at least the .NET SDK) installed...
(even if the framework is installed). Is this correct?
The error message I get is "Error executing program" or something
similar, depending on the machine. Is there a way to circumvent this
problem (except for installing the entire sdk) ?

Thanks
Martin

[Martin]

I forgot to say, I need to run the application _without_ having a
setup routine, just by copying the executable onto the target machine.
"Martin" <[e-mail]> schrieb im Newsbeitrag
news:uA**************@TK2MSFTNGP14.phx.gbl...

Hi there,
after experimenting a bit with VS2005 and .NET forms, I learned
that .NET applications that are compiled as debug build don't run
on machines that don't have VS (or at least the .NET SDK) installed...
(even if the framework is installed). Is this correct?
The error message I get is "Error executing program" or something
similar, depending on the machine. Is there a way to circumvent this
problem (except for installing the entire sdk) ?

Thanks
Martin

[n4ixt]

Yes, you must have the .Net framework installed, and that goes for whether
you compile in Debug or Release mode.

There is a redistributible installer for the .net framework, just go to the
microsoft site and find the one for whatever version of VS you have (you say
2005, so you'll need the 2.0 framework). Have the users install once, and
you'll be good to go for xcopy deployment after that.

Robert

"Martin" <[e-mail]> wrote in message
news:uA**************@TK2MSFTNGP14.phx.gbl...

Hi there,
after experimenting a bit with VS2005 and .NET forms, I learned
that .NET applications that are compiled as debug build don't run
on machines that don't have VS (or at least the .NET SDK) installed...
(even if the framework is installed). Is this correct?
The error message I get is "Error executing program" or something
similar, depending on the machine. Is there a way to circumvent this
problem (except for installing the entire sdk) ?

Thanks
Martin

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

[Brian Gideon]

Martin,

Can you post the exception message and stack trace?

Brian

Martin wrote:

Hi there,
after experimenting a bit with VS2005 and .NET forms, I learned
that .NET applications that are compiled as debug build don't run
on machines that don't have VS (or at least the .NET SDK) installed...
(even if the framework is installed). Is this correct?
The error message I get is "Error executing program" or something
similar, depending on the machine. Is there a way to circumvent this
problem (except for installing the entire sdk) ?

Thanks
Martin

[Martin]

this actually does not work...like I said, the .net 2.0 framework
is installed on the target machine, still only the release build
will run.

martin

"n4ixt" <n4ixt@notabitofspam_direcway.com> schrieb im Newsbeitrag
news:11*************@sp6iad.superfeed.net...

Yes, you must have the .Net framework installed, and that goes for whether
you compile in Debug or Release mode.

There is a redistributible installer for the .net framework, just go to the microsoft site and find the one for whatever version of VS you have (you say 2005, so you'll need the 2.0 framework). Have the users install once, and
you'll be good to go for xcopy deployment after that.

Robert

"Martin" <[e-mail]> wrote in message
news:uA**************@TK2MSFTNGP14.phx.gbl...

Hi there,
after experimenting a bit with VS2005 and .NET forms, I learned
that .NET applications that are compiled as debug build don't run
on machines that don't have VS (or at least the .NET SDK) installed...
(even if the framework is installed). Is this correct?
The error message I get is "Error executing program" or something
similar, depending on the machine. Is there a way to circumvent this
problem (except for installing the entire sdk) ?

Thanks
Martin


----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet

News==---- http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups ----= East and West-Coast Server Farms - Total Privacy via Encryption

=----