Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Is it incorrect or frowned up to use Visual Basic libraries on C# code?
One particular example is the CSV parser which exists for VB but not for C#.
using Microsoft.VisualBasic.FileIO for TextFieldParser
I am sure there is other examples. Of course there are ways to do the same in C# but would require writing more code, why reinvent the wheel?
The whole point of .NET (well, one major point) is that it doesn't matter what language things are written in! So calling a VB library from C# is no big deal.
TextFieldParser is perfectly safe and reasonable to use from C#. It's part of the default Framework install. Use it!
"Why reinvent the wheel?" -- Exactly!
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 days ago.
Improve this question
I'm (new to) teaching OOP and I'm racking my brains for a simple OOP project that uses inheritance that can have a simple GUI. I am not doing a calculator, its been done to death. I want to allow a reasonable amount of creativity and I don't think any of my students have used VS or C# before, which is good because I'm incredibly bored of the same errors in python.
I currently have them refactoring (python) a previous CLI sweet shop program to OOP so it can sell different products, which allows inheritance nicely. Doing this again in C# with a GUI is an option, or a library maybe with different types of media to "rent". I'm trying to think back to my uni days but that's proving difficult!
Any ideas welcome!
Thanks
As stated above, just looking for ideas, not solutions.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Is it a good idea to create a website using C# and .Net? I thought of using PHP and codeignator but I would have to learn two new things.
Is it possible to do this fully in C#?
Could I do it completely inside Visual Studio?
What kind of problems should I expect?
Is it a good idea or should I be looking at PHP and Phython (the only opinionated part so please use your own experience as example to prove this point).
The bold points are the ones I care most about. I understand #4 is very opinionated but if you can provide me with your own experience it would help, something like "I tried and my website was really slow/fast because of [this]." would help.
Yes. It's a good idea.
The entire StackExchange network is developed in .Net
yes
yes
A lot, performance, hosting, responsiveness, scalabilty.
It's possible, of course. I prefer .Net.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have been talking with one java programmer and he told me that all of the Payment Gateways are designed in Java because they are secure in comparison of any .net based language.
Is it true?
No, that is not correct. .NET based languages and Java can each be programmed securely, or insecurely.
Given the large number of high profile Java vulnerabilities which have surfaced over the years, I highly doubt the quality of the statement made by "one java programmer". This smells more of FUD spreading than any kind of factual statement.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Assuming I was writing my own version of .Net :)
What would be the downside of such a setup?
Yes, I am talking about a new anti-pattern here to avoid creating endless tuples and EventArgs. I think such a setup would have made coding a lot cleaner.
No. The Tag property has history, it was important in VB6 and Winforms was meant to replace it. It needed to be added to make porting code relatively simple.
It is entirely unnecessary in .NET. It supports implementation inheritance, a feature that VB6 didn't have. So if you want to add extra properties then you just derive a class and add them. And you'll be able to give them a good name and a type so you don't have to cast every time you read the property. This works just as well with Winforms controls.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Can anyone tell me what would be more efficient: A large program is written in visual-C++ years ago is now intended to be written in C#. What would be better, re-writing the whole code of visual-C++ in C# or write C++ DLLs to be used in C# program via DLLimport?
I guess it depends on how data-centric your code is. If you can easily separate out the functionality that does not require an interface, then you'd most likely be better off writing a DLL to utilize this functionality, and then re-writing the interface in C#.
If the program is rather interface heavy, and you do not want to go through separating out all of the data functions, then I'd just go ahead and re-write the whole thing in C#, although I'd expect to lose some performance.
VisualC++ is still a very widely used language - is this your only reason for wanting to move to C# (i.e. finding it hard to recruit people, lacking skills to continue development)?
There is only a single answer to this: "it depends". We cannot possibly know this, it's something you must decide.
Check what you need in terms of time and other resources for both. Check what benefit your gain from both. Weigth cost against benefit. Decide.