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

Problems running .NET apps on other machines

P: n/a
Max
I'm fairly new to distributing .NET applications, and so far no one is able
to use the apps I create. They do run on all 3 of my machines. I include the
dotnetfxredist with the setup files. One person cannot even install the
framework from Windows Update. It's giving them errors and I'm unable to
troubleshoot over the phone. This pretty much blows since I've spent so much
time developing in .NET for my user base and they cannot use it! Is there a
way to convert my app to Windows executable or something? What are my
options?

-Max
Nov 18 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
First off I would post to the right group. This one is ASP.NET, for web
applications and not client ones.
--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com
"Max" <no****@notvalid.com> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...
I'm fairly new to distributing .NET applications, and so far no one is
able to use the apps I create. They do run on all 3 of my machines. I
include the dotnetfxredist with the setup files. One person cannot even
install the framework from Windows Update. It's giving them errors and I'm
unable to troubleshoot over the phone. This pretty much blows since I've
spent so much time developing in .NET for my user base and they cannot use
it! Is there a way to convert my app to Windows executable or something?
What are my options?

-Max

Nov 18 '05 #2

P: n/a
while this is the wrong group, this is the major problem with .net winform
apps. the client must install the 20mb+ .net runtime. no, you can not run
your app without a sucessful .net framework install (which must match the
version of your code). while ms is working on an application deployment
block, they miss the problem of actually getting the runtime installed.

you way not want to hear this, but unless its an inhouse app (where you can
control the .net install) or machines start shipping with .net installed
(though 2.0 is just around the corner), winform apps are a risky choice. my
guess is after longhorn becomes common, it will be safe to write winform
apps for the general public.
-- bruce (sqlwork)


"Max" <no****@notvalid.com> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...
I'm fairly new to distributing .NET applications, and so far no one is able to use the apps I create. They do run on all 3 of my machines. I include the dotnetfxredist with the setup files. One person cannot even install the
framework from Windows Update. It's giving them errors and I'm unable to
troubleshoot over the phone. This pretty much blows since I've spent so much time developing in .NET for my user base and they cannot use it! Is there a way to convert my app to Windows executable or something? What are my
options?

-Max

Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.