Sign in to follow this  

converting a C#.NET app to... what?

This topic is 4812 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I've written a nice user interface for my shell extension, using C#.NET. And personally I really enjoy it, C#.NET works very smoothely and I like it. But some users (and would-be users) has expressed that they don't have .NET and/or find it demanding that my small app requires the .NET framework installed. So now I might port my code to something else. All the main functionality is already in a DLL, but it's more the... Infotips, CheckedListBox, Buttons, GroupBox, and how they affect the flow of the program on user interaction that I'm worried about. What would be a suitable library to use that's similar to the .NET framework? I've used MFC and I hate it... Maybe wxWidgets might be good? Never used it. Any suggestions?

Share this post


Link to post
Share on other sites
My personal opinion for you, if you don't mind, is to stick with your decision about the .NET framework. If you think about it, pretty quick everyone is going to have the framework installed, especially when Longhorn comes out. With the .NET framework you have a robust library to build your applications with, constant improvements from Microsoft, and if you design your application again using an older or 3rd party framework, I feel it will be outdated a lot quicker than a .NET saavy application. I think from a maintainability and technical point of view, I would stick with .NET. The runtime is not that bad, only has to be installed once, and you gain access to a myriad of features that will speed up your development time ten fold.

Just my two cents!

~Graham

Share this post


Link to post
Share on other sites
Thank you for your quick responce =)

Yes I personally prefer .NET, it was just a attempt to please all. But that's probably not possible =/

Oh well, more time to code more features then ;)

Share this post


Link to post
Share on other sites
Instead, write a small 'What is the .NET framework' bit that is understandable by all at the download links to your project. You will increase the number of users who will be willing to download it, if they see briefly what it is, and how useful it will be in the future as more .NET programs become available, and if they know its a one time only download.

I guarantee you that anyone who is serious about using your software will then be willing to download it and the required component.

Share this post


Link to post
Share on other sites

This topic is 4812 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this