Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
What are the possible ways to convert a windows form application (c# , .net) to a cross platform project?
My GOAL is have a project that can run in both Linux base os and windows.
I really like .net but it's not compatible with all OS (for example Linux) because of .Net Framework installation.
what is your suggestions?
As #paqogomez pointed out, IronPython does not take away the need for some sort of .net since, as it's stated on the website http://ironpython.net/ : "IronPython is an excellent addition to the .NET Framework, providing Python developers with the power of the .NET framework."
Since your goal is to run your existing winforms-c#-application on both, windows and linux, you might get away by just using mono (http://www.mono-project.com/).
If this doesn't work out (please refer to http://mono-project.com/Compatibility for compatability issues), you could manually rewrite your existing C# application in pure python. But then, it might well be possible to use any other unmanaged, managed or scripted language which can be used on both systems and which is either easier to translate manually or for which even automated translators exist (however, I don't know if there are any for C#).
Thinking about the last point, I did a quick websearch for "c# cross compiler" which shows some esoteric results which might be interesting for you depending on your project type.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I've done a bit of reading online and I'm not seeing a straight forward answer to a straight forward question. Is .NET for Windows and Mono for Mac? Maybe my understanding is off but I'm trying to figure out the difference between the two tools. Thanks in advance.
Mono was originally reimplementation of the .NET for linux. Today is much more (http://www.mono-project.com/).
There is actually funny story behind. Miguel De Icaza was working on linux email client and he loved .NET C# so much that we wanted to work with it also on linux. So he rewrite the .NET so he can wrote email client in C#. Wow.
Then mono evolved very very much all lead to the Xamarin platform (.NET cross mobile platform).
You can more read here: https://blogs.msdn.microsoft.com/cesardelatorre/2016/06/27/net-core-1-0-net-framework-xamarin-the-whatand-when-to-use-it/
.NET comes with a runtime environment that runs .NET apps on a windows based OS. It is of course produced and distributed by Microsoft. Mono is an open source version of the that which allows you to do this on Linux, Mac, and even windows.
Conceptually, the runtime seems to operate somewhat like a JRE does, in that, you can take a module built in .NET, and run it in Mono. So, it must be something like byte code that can then be interpreted and compiled to run natively (this last sentence is all speculation).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have made windows application in visual studio 2010 in windows 7.
Will it work properly in other OS version (like windows XP, windows 8, etc..)?
I have used third party DLL as reference for HID connection in application.
If there are c# controls which will behave differently depend on OS version, then please give list of them with details.
Thank you.
You should test on all the platforms you intend to support. Different O/S versions are, well, different (otherwise what's the point of them?), so you can't assume it will work the same way on each version. You may even find that things like the Service Pack version have an effect, or the version of other libraries available on the system (e.g. .NET framework in your case) can have an effect.
So, you should decide what platforms, with what minimum specs, you can support (from a technical point of view) and which of those platforms you are willing to put the time, effort and cost into supporting, for what period of time, and then plan to test thoroughly on all those platforms. And then repeat for each release of your software (so you might want to outline the support lifetime of each release in advance, so customers are prepared for when they need to upgrade).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
There's a lot of buzz around C# 6
However, I wanted to know that if they work in asp.net and asp.net mvc?
I mean, C# 6 cannot just run in framework 4.5 (Or can it?)
Should we use C# 6 for backend of asp.net/(mvc), because mostly all doesn't have private servers.
So, should we wait for hosters like godaddy to upgrade their system, before we could use much anticipated c# 6?
The preview-release of the C# 6.0 compiler is just that - a compiler. It doesn't target a new version of the .NET Framework. As such, there's nothing new that needs to be installed on your server - you just compile your code with the new compiler, upload it, and you're done.
Of course, this doesn't mean that all features will be available if you're not using a sufficiently up-to-date version of .NET - if you're targeting .NET 2.0, obviously you don't get to use LINQ since that was introduced in .NET 3.5.
Also, a lot of the features you've heard "buzz" about haven't even been implemented yet, even in the preview-release. They're planned, that's all. If there's a particular feature you've heard about that you're wanting to make use of, you should check whether it's even been implemented before you even bother downloading it.
The point though is that the C# compiler and the .NET framework are two completely separate things. There has not (yet) been any announcement of a new version of the .NET framework.
Another point worth bearing in mind though is that the preview-release compiler is exactly what it says - a preview-release. This is NOT the final release, and you need to be aware that features could change or even be removed from under you by the time the final release comes around. How likely that is, I can't say, and the risks involved in using new features introduced with a preview compiler for a production application are for you to weigh.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I want to create a deskband app, like BatteryBar, in C#. I understand that the deskband might not work in future versions of windows, that you shouldn't code explorer extensions in managed code, and whatnot. My question is, what is the current reccomended way to create a deskband (or a simulation of one) in C#? Thanks in advance!
This may not answer your question, but it is important information related to your question:
You said,
I understand ... that you shouldn't
code explorer extensions in managed
code
This is no longer true.
This used to be true because the multiple versions of the CLR could not be loaded into a single process. For example, Explorer could not load an extension that used both .NET 2 and .NET 1; the host process would fail to load the second CLR version.
But with .NET 4, which comes with a new CLR, you can now run multiple versions of the CLR in the same process. So if you write your code using .NET 4, you're no longer at risk of making host processes error out.
In short, it is now OK to write Explorer extensions in managed code, provided you're using .NET 4 or greater.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
How can I make an interface for console applications to make them look like edit.com under Microsoft's operating systems. Target languages are C, C++ and C#.NET.
Have a look at curses:
e.g.:
http://sourceforge.net/projects/curses-sharp/
That would be based on a very simple framework which writes directly to the video to draw the underlying shadows, drop down menus, etc, not alone that, since 'Edit.com` would be written in assembler for speed in relation to drawing, this is quite ancient by today's standards, you can however take a look at PDCurses which will enable you to do this kind of thing.
The neat beauty is, PDCurses is compatible with the unix equivalent of Curses.
But, really, today, it is all about GUI and Windows....
What kind of application are you trying to do?
IIRC, from my old days, there was an object orientated framework for this using TurboVision, which has a port available with open source now, see this wikipedia entry on this TurboVision.
Today, console applications are either old DOS applications emulated more and less in Windows, or command-line interpreters.
Anyway, if you really want to do an editor, use the System.Console class in the System NameSpace and use the SetCursorPosition method to write what you want where you want
The edit.com window you are showing appear to be developed with Turbo Vision, an old console gui library written by Borland many years ago.
Borland put the software in public domain and release its C++ sources. There is also a porting to Pascal, developed by the community, called Free Vision.
Unfortunately ,I don't think there is a porting or a wrapper to dot.net, so you have to write your own. Or, at least, you can look at the sources to get inspired...