End user .NET applications?
-
Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. :omg: Any thoughts? -- Dana Holt Xenos Software
-
Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. :omg: Any thoughts? -- Dana Holt Xenos Software
I'd definately consider it for bespoke projects, but for commerical/freeware/shareware etc, no way. Nobody is going to download 21MB just to use at little 500k app when they can find something that does the same elsewhere. Give it 4 or so years and it'll be acceptable for the vast majority of users to have the framework. Simon This message has not been scanned for viruses. It may destroy your hard drive. Not likely, but run a virus scanner through everything I write before you read it. Just in case. Sonork ID 100.10024
-
Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. :omg: Any thoughts? -- Dana Holt Xenos Software
ASP.NET surely is a won bet by Microsoft ! Faster , with a lot of improvements and with real languages, not just script ones ... So IMHO ASP.NET and Web Services that we can use will definitely have success ... Cheers, Joao Vaz A person who is nice to you, but rude to the waiter, is not a nice person - Natalie Portman (Padme/Amidala of Star Wars)
-
Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. :omg: Any thoughts? -- Dana Holt Xenos Software
Dana Holt wrote: Any thoughts? If through your research into your user base you feel that your users will be willing to download the 21mb .NET Framework to run your application then yes, use .NET. However if you cannot motivate your user base to do so* , then don't use .NET and wait until the .NET Framework has been distributed through others means** to a large enough proportion of your user base. Thank god I develop web applications where I can use .NET on the server side and not worry whether my users have .NET or not. :-D * maybe by bundling your app with another app (which need not neccesarily require the .NET Framework, just don't tell your users that) which in total makes getting the .NET Framework seem worth it to the user ** Windows .NET, Office .NET etc. regards, Paul Watson Bluegrass Cape Town, South Africa The greatest thing you'll ever learn is just to love, and to be loved in return - Moulin Rouge "Reports of my death have been greatly exaggerated."
-
I'd definately consider it for bespoke projects, but for commerical/freeware/shareware etc, no way. Nobody is going to download 21MB just to use at little 500k app when they can find something that does the same elsewhere. Give it 4 or so years and it'll be acceptable for the vast majority of users to have the framework. Simon This message has not been scanned for viruses. It may destroy your hard drive. Not likely, but run a virus scanner through everything I write before you read it. Just in case. Sonork ID 100.10024
I think it will be much quicker than 4 years. MS will ship it with new versions of all their apps (probably), service packs..and wathever it is they ship. Other companys gonna ship it. And there doesn't seems to have been that big a problem for people to keep downloading the new IE versions, so as soon as ther is any good apps that use it they gonna get it.
-
Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. :omg: Any thoughts? -- Dana Holt Xenos Software
I would wait for Adobe,Autodesk,Microsoft,Macromedia, and other companies to adopt .NET for their products before doing so myself. As a client side technology, .NET faces the same acid test as java. It we dont see a Flash or Photoshop written using the .NET framwork within the next 3-4 years, .NET would be a non-starter on the client side, just like Java. There will no doubt be a lot of cool toy apps, but no pudding. So, if my livelihood depended on the success of my client application, I would stick with proven stuff. At the same time evaluating (play around) .NET. That way, if .NET becomes a hit on the client, I wouldnt be too far behind. OTOH, the server side is a very different story. - Vivek
-
I think it will be much quicker than 4 years. MS will ship it with new versions of all their apps (probably), service packs..and wathever it is they ship. Other companys gonna ship it. And there doesn't seems to have been that big a problem for people to keep downloading the new IE versions, so as soon as ther is any good apps that use it they gonna get it.
.. but I though everyone had/has broadband!:omg: :confused: :eek: KR Al. (In the UK!!) Alice thought that running very fast for a long time would get you to somewhere else. " A very slow kind of country!" said the queen. "Now, here , you see, it takes all the running you can do, to keep in the same place".
-
Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. :omg: Any thoughts? -- Dana Holt Xenos Software
Most useful applications have dependencies on third-party frameworks and libraries. MFC, Java are examples of some. you can write an app with limited dependencies, but at the cost of good code. For example: there is obviously a big advantage to writing an app in MFC vs. the Win32 api. Supporting the code becomes simpler in the future.
-
I'd definately consider it for bespoke projects, but for commerical/freeware/shareware etc, no way. Nobody is going to download 21MB just to use at little 500k app when they can find something that does the same elsewhere. Give it 4 or so years and it'll be acceptable for the vast majority of users to have the framework. Simon This message has not been scanned for viruses. It may destroy your hard drive. Not likely, but run a virus scanner through everything I write before you read it. Just in case. Sonork ID 100.10024
Simon Walton wrote: bespoke Excellent word! -- Russell Morris "WOW! Chocolate - half price!" - Homer Simpson, while in the land of chocolate.
-
Most useful applications have dependencies on third-party frameworks and libraries. MFC, Java are examples of some. you can write an app with limited dependencies, but at the cost of good code. For example: there is obviously a big advantage to writing an app in MFC vs. the Win32 api. Supporting the code becomes simpler in the future.
Yes, but statically linking MFC to your app or including mfc42.dll increases the size by at most a meg. If the .NET download is about 20 meg, and you only distribute over the web, then that is a BIG difference. :eek: No generalization is 100% true. Not even this one.
-
Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. :omg: Any thoughts? -- Dana Holt Xenos Software
All my client side windows development is with C#. Now I haven't released any applications yet, but that is another story. :cool: Jason Gerard
-
Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. :omg: Any thoughts? -- Dana Holt Xenos Software
Dana Holt wrote: Now that .NET is here I am interested to know when you plan to make use of .NET for end user Windows applications? Yes! I am currently developing a vertical market commercial program which should be released in the next 60-90 days. It will of course have the .NET on the CD. You can (and your clients can) look at .NET as the latest MDAC or any other updatible componet for Windows. It is nothing more than any other serivce pack as far as the end user is concerned. Dana Holt wrote: I would like to use the features and ease of development of C#, but many users won't have to .NET framework on their machine. Even worse, if they have a dial-up internet connection they aren't going to want to download it. Maybe not if they have dial up. I have programmed for around twenty years now and I have watched many major moves in the industry. Of course I would make the wrong choices and always end up on the back side of all new technology. That is a thing of the past. The most important thing I have learned from all the large sucessful companies is that they do not develop for today's machine but what will be the top of the line machine (and OS) when the start to deploy. They know that they several years of sales ahead before that top of the line machine is then outdated. In short, program for tomorrow as you have already missed todays deadline! Currently, .NET is offered in XP's Window Update function. I would imagine it will be in 9x and 2K Windows Update soon. Then they will ship all future versions of XP with .NET built in. After August all future (Windows) machines will come with .NET already loaded as it will be a part of the XP Upgrade. So, maybe today you will not get as many downloads from the masses, but in the short future you will. Of course, right now everyone is hungry to see something new for .NET so they download about anything ;) One last thought, for my I can produce programs in about a forth of the time as my old VC/MFC. Have you thought of how many different apps you can have on the market in the same length of time that you would spend developing just one :) I personally, just do not look back! Just my $0.035 worth. Rocky Moore