views:

65

answers:

8

Hi,

I'm developing an application for wide use using c#.

I'v writen most of the project, a freeware app, using the 3.5 ,net framework and now it's time to publish this project. And I have run into a few dilemas I would like your opinion .

1] Most people don't have ,net 3.5, should i offer the user to install it? the install is quite complicated and there's a 250MB download (if the user doesn't have XP SP2). I'm not sure the user will click through.

2] If so, should I just downgrade the whole project to .NET 1.0? so that the max amount of people would be able to use my app, or should I use 4.0.

3] I can use .NET 4.0, ask the user to install a 28MB file, and save on development time which i can invest on making a great product the users would enjoy more.

I really don't know which way to go.

I'm really looking for some wisdom here.

Thanks.

A: 

Do you know who your target audience is?

Are they mostly windows XP users? SP3? Or mostly Windows 7 users? Are they mostly broadband users? What average speeds? You need to find this out first.

Once you have the statistics for your demographic, you should know you what operating systems they use and therefore what versions of the framework they would have installed and how painful getting different versions would be for them.

This data, in turn, will help you decide about which version to target.

Oded
My target audience is all pc users.
Haim Bender
@Haim Bender - Linux, Mac and BSD users included?
Oded
I meant windows users :p
Haim Bender
@halfdan - 1) PC = Personal Computer. 2) Intel Macs are PCs...
Oded
Can we not fight on this subject, with all due respect it's really irrelevant to the question.
Haim Bender
+1  A: 

You shouldn't go back to .NET 1.0/1.1. Your application, even though written in .NET 3.5, should run on .NET 2.0 (CLR) as all Versions up to 3.5 are compatible to the .NET 2.0 Runtime. 2.0 should be widely supported and installed on most up-to-date operating systems (Windows).

If you require features from .NET 4.0 you can of course upgrade, which in turn means that your users would have to upgrade too.

halfdan
+1  A: 

You can write your app in VS2010 but still set the target .NET framework to 2.0 or 3.5. You won't be able to use latest features but at least you can use latest IDE.

Jakub Konecki
A: 

it depends on the people interested in your app and their operating systems and .Net versions.
But I think if your app is very good no one will find a problem in downloding the newest version of .Net to use it.

M.H
+1  A: 

You could use the .net 4 Client profile libs, smaller install for the user, new technology for the dev. also, AFIK, .net 3.5 is now distributed via windows update, so you can pretty much be sure everyone has it.

Muad'Dib
Yeah, I'd love to use 4.0 but no one has that installed...
Haim Bender
4.0 is has been on Windows Update since June. http://blogs.msdn.com/b/servicing/archive/2010/06/22/net-framework-4-now-available-on-windows-update-wsus.aspx
rossisdead
i kinda thought that it might be.
Muad'Dib
A: 

Some options to consider (in descending order of goodness and difficulty!):

  1. Migrate to Silverlight - makes it easy to distribute and with the out-of-browser option you can now install and run full trust easily (see for example Seesmic Desktop).

  2. Use .NET 4 with the client profile - smaller download option and it sounds like much of your target audience will need to download something.

Hightechrider
Why? If I use 2.0, most of my audience wouldn't. 50% + have .net 2.0
Haim Bender
Your question didn't mention who the audience was. But if it's really 50% then that's still a lot of pain: 50% x a huge download ... might be a better overall experience if everyone has the same smaller download experience.
Hightechrider
+1  A: 

I strongly suggest to use what you already have, don't downgrade.

Now, those options aren't the ones you should have, instead:

  1. Use the client profile of 3.5 SP1
  2. Use the client profile of 4.0

Users are a more likely to have 3.5 SP1 than 4.0, but if you'll benefit greatly from features 4.0 its worth the upgrade. If you don't see a strong benefit in upgrading to 4.0, wait some time for it and keep it to 3.5 SP1.

eglasius
+1  A: 

I strongly share your dillemas, beeing author of online apps myself. I stick to framework 2.0, and only in recent time I am beginning to wander to upgrade to 3.51 or 4.0, and answer to 250mb download problem is called:

""CLIENT PROFILE""

Check this:

http://stackoverflow.com/questions/1359974/convince-me-to-move-to-net-3-5-from-2-0

and this:

http://windowsclient.net/wpf/wpf35/wpf-35sp1-client-profile.aspx

Daniel Mošmondor