[tonakis2108]

Should I use Visual Studio for an Open Source project?
I thought I could use C# on WPF for a variety of software but I would like an opinion about this.

[Killpot]

Visual Studio is pretty much your go to IDE for anything .Net, there's other alternatives like LightDevolop but like VS they're windows only.

WPF Is pretty neato, there's allot of cool things you can do with it, however I still prefer Forms simply because I'm used to it. I've never taken the time to properly learn WPF because there wasn't much a reason to use it over Forms, and there's much more public source and support for Forms. The argument for web usage is simply a pain in the ass, I've tried and barely got it working and it required pre-requisites to be installed client side, so phones and some other OS's wont be able to view it. So if I were you I would stick to Forms for programs and ASP.Net for all web dev.

[tonakis2108]

Visual Studio is pretty much your go to IDE for anything .Net, there's other alternatives like LightDevolop but like VS they're windows only.

WPF Is pretty neato, there's allot of cool things you can do with it, however I still prefer Forms simply because I'm used to it. I've never taken the time to properly learn WPF because there wasn't much a reason to use it over Forms, and there's much more public source and support for Forms. The argument for web usage is simply a pain in the ass, I've tried and barely got it working and it required pre-requisites to be installed client side, so phones and some other OS's wont be able to view it. So if I were you I would stick to Forms for programs and ASP.Net for all web dev.

I'm not into web developing that much I got partners to cover that for me but OS depended software are my subject. I prefer WPF because there's much more customization for GUI, xaml does the trick fine, however my only problem is MICROSOFT, let's say I create a project in VS will it still be loaded in VS 2020 for example? Maybe some new changes will make my project not usable anymore, more frameworks needed, no cross platform support etc.
What problems with pre-requisites did you come across?

[Killpot]

For WPF in web browser form, the client needed SilverLight. And I wouldn't worry about compatibility, there are VB.Net projects from just when it came out that still work today, and if they stop working i'm sure people will update the compatibility, unless the language itself changes, but that wont happen. And what customization in WPF do you need that Forms can't do? If worse comes to worse and you absolutely need a custom control it's probably already out there or you could just use GDI+ and make it.

[tonakis2108]

For WPF in web browser form, the client needed SilverLight. And I wouldn't worry about compatibility, there are VB.Net projects from just when it came out that still work today, and if they stop working i'm sure people will update the compatibility, unless the language itself changes, but that wont happen. And what customization in WPF do you need that Forms can't do? If worse comes to worse and you absolutely need a custom control it's probably already out there or you could just use GDI+ and make it.

I see so using WPF for web does contain it's own risks, propably these pre-requisites are covered byan installer where I'll compile all of them for every client. I like the way you can customize a button like a css template, a partner I work with keeps telling me that microsoft doesn't help with huge projects and only linux offers this kind of luxury especially for server sided code.

[Killpot]

Coming from personal experience, don't allow "friends" biased opinions to convince you about things verbatim especially with this Linux elitism that's going around.. I'd just get a clear plan in your head of what you want to do and take it as it comes, don't start out trying to cater to the end game when you haven't even created the project yet. Visual studio can handle large projects fantastically, I have yet to read about or personally run into a case of that being an issue. ASP.Net is an amazing engine for web design, it literally has everything and more, it has normal HTML and CSS + PHP, and then you have the .Net framework's robust engines on top of it to add functionality to everything. However WPF isn't without it's pit falls, it requires .NET Framework 3.0, and compared to Windows Forms, it's still in an evolving phase and bugs have been found with no work around. It also requires Dx9 compatible video card for advanced graphics.

[tonakis2108]

Coming from personal experience, don't allow "friends" biased opinions to convince you about things verbatim especially with this Linux elitism that's going around.. I'd just get a clear plan in your head of what you want to do and take it as it comes, don't start out trying to cater to the end game when you haven't even created the project yet. Visual studio can handle large projects fantastically, I have yet to read about or personally run into a case of that being an issue. ASP.Net is an amazing engine for web design, it literally has everything and more, it has normal HTML and CSS + PHP, and then you have the .Net framework's robust engines on top of it to add functionality to everything. However WPF isn't without it's pit falls, it requires .NET Framework 3.0, and compared to Windows Forms, it's still in an evolving phase and bugs have been found with no work around. It also requires Dx9 compatible video card for advanced graphics.

There's a project going on and we started it on NetBeans starting in JAVA which was awful... Couldn't sync with the changes as it should and had a lot of bugs, now we are in the middle of changing our project into C# that's why I started this question, to check which could be the best move up to now. All the dependancies will be covered by the installer so it will not cause any framework issues hopefully. The project isn't going to be hard for the system to handle or work with extreme graphics. Take CCLeaner as an example of what the project will be like.

[Killpot]

Hmm, yeah I suppose, it's really whatever you're comfortable with. And by mention DX I didn't mean intensive, I just mean it's a pre-requisite, if the client doesn't have it, it wont work. But if your heart is set on WPF then go kill it man, but don't shoot down options before you've tried them just because of someones biased opinions, I mean, I almost had the same situation here, and a friend that knew low level languages had me almost completely convinced I should be using languages like C and MASM/FASM, for a fucking mod installer, I never even considered other options because of what he said, I just stumbled upon .Net by accident.

[tonakis2108]

True, I work mostly with vb.NET but I wanted a more flexible language like C to do different projects even ASP.NET. Probably it's what people get used to, others have known C so they go with C not Java or VB, someone else could use PYTHON well I guess everything depends on what the person has grown more fond off. So do you think Visual Studio has everything a development team needs?
And one more question, C or VB?

[Killpot]

True, I work mostly with vb.NET but I wanted a more flexible language like C to do different projects even ASP.NET. Probably it's what people get used to, others have known C so they go with C not Java or VB, someone else could use PYTHON well I guess everything depends on what the person has grown more fond off. So do you think Visual Studio has everything a development team needs?
And one more question, C or VB?

Oh yeah, and more. There's plugins that allow you to even edit projects realtime, like google docs with multiple people. And it's really a matter of what you want to do in said language. I would probably say VB for most, simply because it has the .Net framework to do all sorts of things, like using NetClient to download a file online is like 2 lines of code, whereas in C that would be multiple libraries. You may have cross platform support, and some performance. But no one is going to miss the few picoseconds in between code execution. And honestly anything made for linux or windows should never be used interchangeably. The programs should be customized uniquely to each OS. If anything I would only use C as a middle man type deal, keep the main logic in VB and have low level stuff just be communicated via a C/ASM project if it really needs it. For things like drivers for example.