|
Permission granted, sir.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
If just a personal project go with what you are comfortable bit.
But if wanting to expand skills with something that is more commercially used at the moment then I'd use c#.
|
|
|
|
|
I'm in the C# camp but really only because of my path from BASIC to C and C++ (with a few others along the way - PHP, Protel, Swift, etc). I really like C# but you can achieve most (if not all) of the same things with VB.NET - if you're comfortable with that, I'd say stick with it as you'll be more productive.
As for ASP.NET Core, it looks really promising - the idea is great, but it's still early days. There are some holes around using Entity Framework (e.g. building and running an ASP.NET app on Linux/Mac that uses a SQL Server/SQL Azure backend) and publishing your finished app. I've played around with JetBrains Rider[^] which is really good (much better than VS Code in my opinion), but I think that a bit more development is needed to make it dependable for production apps.
If you're just looking to get into C# then go for it.. 
Ah, I see you have the machine that goes ping. This is my favorite. You see we lease it back from the company we sold it to and that way it comes under the monthly current budget and not the capital account.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
.NET will allow a lot of sharing amongst program pieces (DLL's, for example) - and they use the same set of procedures and namespaces.
That being said, C# follows the "C" syntax/structure - which is far and away the most often used structural design out there. It prepares you for then, now, and the future much more thoroughly.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
C#. AFAIK VB lacks the syntax for some capabilities, whihc is dumb since both are CLR based languages. Go with C#.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
If you're looking to use ASP.Net Core, it's worth remembering that .NET Core doesn't yet support Visual Basic.
If you'll be running on Windows using the full CLR and .NET Framework, you could still write most of your app logic in VB if you want to - your ASP.NET web app would be in C#, but you could have a separate VB project that you reference from your web app.
Of course, even that isn't so simple right now. In VS2015, if you add a regular .NET class library project to a solution that already contains an ASP.NET core application, you can't just add a reference to the class library project from the ASP.NET Core project. You'll have to build the class library first and reference the .dll.
That restriction will probably be gone in VS2017. .NET Core projects will be switching back to using .csproj instead of project.json. The VS2015 .NET Core tooling doesn't currently support that, but VS2017 RC does.
|
|
|
|
|
Thanks for that. I discovered it wasn't supported in Core 1.0, so have already decided to go with C#.
Ryan Peden wrote: That restriction will probably be gone in VS2017.
I can't wait for 2017 - I may not be here then. I'm 74 next week!!!
|
|
|
|
|
Sounds like a good plan!
For what it's worth, VS2017 RC available now, and according to these release notes, the updated .NET Core tooling will let .NET Core projects reference other projects in the same solution. So if you get into the project and find yourself wishing for VB, at least it's still an option.
|
|
|
|
|
xiecsuk:
I am probably the only guy here anywhere near your age. I know how hard it is to master "new" stuff after 60.
It appears that you are saying:
"I am a 74 year old long-time VB developer. I am going to build something in .Net Core with ASP and C#, none of which I have ever used before. I don't have time to wait for VB in 2017 because I am so old".
2017 will be one of your more interesting years ...
|
|
|
|
|
I moved from VB to C# and it wasn't a difficult transition (I did start out in life as a C programmer but I'm not sure that that was a huge factor).
C# is, undoubtedly, a vastly superior language to the syntactically hideous VB and it has the added advantage of being used by far more people so it's much easier to get help when you need it.
If you decide to go with C# you'll wind up being glad that you did.
Slogans aren't solutions.
|
|
|
|
|
|
C# 6 without question
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
They had VB for the Speccy?
Us experts used Sinclair Basic.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Of course, you are right; Sinclair Basic it certainly was. But that was virtually the same Basic that ran on any of the early machines. I had an Oric machine as well that had an almost identical version of Basic.
|
|
|
|
|
I saw no mention of this. You said the last C# you used was possibly 4.0? If it was then you don't have much to catch up on. C#5 and 6 are relatively small in changes compared to 3.0 and 4.0. C#5 introducing async and caller information for debugging while C#6 is mostly just quality-of-life improvements to syntax.
|
|
|
|
|
Forget the c# vs VB discussions on syntax and typing. there is only 1 valid criteria you should apply, which has the most and best support resources.
Others have mentioned it, most examples on the interweb are in c#.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
PHP, HTML, Java script, linux, these give you freedom. I been doing VB.6, VB.Net for 20 + years and use it regular.
But when looking for a job they throw it in the ad as a way to get you to look.
Reading the job ad deeper you realize they want C#, java script, hmtl, web api skills etc.
I have switched to Php and laravel and vue.js and am very happy.
|
|
|
|
|
It wont be as bad as you think. Yes, there is definitely a lot of C# quirks that you would never see in Visual Basic. Fortunately over the years, a lot of them have been removed. String Literals will be different, and type casting also can be a pain. What you will gain out weighs the losses by a tremendous amount. (And you are also fitting yourself for a very close to Java experience too).
Where there's smoke, there's a Blue Screen of death.
|
|
|
|
|
I resisted making the move to C# for a long time because I was so deeply vested in VB and finally the first part of this year I drove a stake in the sand and said that was it. I simply was not able to find the support for what I wanted to accomplish with my sites under VB and was clearly seeing abundant references for it under C#. It had become abundantly clear that community support for VB was waning.
I'm far from expert at this juncture but I've grown comfortable very fast with C# and haven't looked back for a second wishing I'd done differently.
So, if you're considering this for self improvement and development I would weigh heavy on the C# side of things. The only thing that might sway me to suggest VB in your case would be if you wanted to achieve something quick and dirty with something you know cold. Then there is an obvious consideration. However, with that benefit, comes walls that you must consider and for me those walls were insurmountable. You must consider those walls as well.
Good luck!
|
|
|
|
|
C#, it will reduce the amount of abuse you have to wade through from "fellow programmers" that hate VB.Net regardless of whether they know anything about it.
|
|
|
|
|
C# simply because there are more resources for it out there: Ebooks; tutorials; sample apps; app templates. When you need help, it'll be easier to find.
|
|
|
|
|
As someone with almost the exact background - although I started with Basic on the BBC Micro, and my money earning language back in the day was Fortran.
Last year I also started work on building a website with an SQL db, and decided to use ASP.Net. I have done a fair bit of work in MS Access using Visual Basic, and needed to take aspects of that db online. I now have an Access db auto syncing with an online ASP.net app.
I learned by following a few tutorials in MVC VB, and started working in VB, but most of the StackOverflow examples are in C#, so changed to C# and don't regret it.
The Contoso university tutorials are a great place to start: Getting Started with Entity Framework 6 Code First using MVC 5 | The ASP.NET Site[^] . I created my first app by copying that. I still use it as a reminder to set up the start conditions for a new development.
The fact of the matter, in my experience, is that fundamentally all languages use the same building blocks of variables, loops, conditionals etc. The real issue is learning the new way of writing them.
The MVC environment was new to me, and that was where working through the tutorials had the most impact on my learning curve.
I have now developed several ASP.net MVC apps. I have to admit that mine probably isn't the prettiest code - I know this when I look back at the earlier stuff I wrote and faint - but it works.
I still have trouble writing complex Lambda expressions for accessing SQL, but C# has the option of almost SQL like expressions so use that method instead.
I also had problems with Code First getting out of step when updating a live DB, probably because I didn't really understand how it was working, but as I have a fair bit of SQL, I now create the db first and link the MVC to it. That way I don't stuff up a live client db again when I update it!
And as someone who first developed programs using a teletype and punched paper tape for I/O, and had to set switches on the front panel of an Elliot 803 to get it to load, Visual Studio is a bit of a leap forward!
|
|
|
|
|
At this point there are 12 comments in this thread that recommend either VB or C#.
Technically the answer is obvious: he wants to do it in .Net Core.
.Net Core doesn't support VB. End of story.
What is interesting are the reasons given.
Of the 12, only one correctly identifies the fundamental issue.
Of the remainder, one suggests VB ("if you already know it"). A good answer (if you are ignorant of the .Net Core VB support issue).
One comment is neutral. In the way of things this neutral comment is the longest in the thread.
Prevaricators in Shakespeare always have the longest speeches.
That leaves nine recommendations - all of which can be classed as "virtue signalling", with no real information content.
The most blatant simply say that {bad people} use VB. Where {bad people} are either "liberal snowflakes" or "conservative flatulents". Two of these.
Also blatant are comments like "syntactically hideous VB" and "favorite loathsome script language du jour". Two of these.
Then there is the milder form of "C# is the industry standard". The virtue signal here is: "I am like all the others - you too should conform". Three of these.
One comments suggests that our man use C# because "you should work on being a polyglot programmer". The virtue signal here is "improve yourself!".
Enthusiastic support for C# over VB is almost always just of form of virtue signalling by insecure people.
Software development is a faddish, politically correct, and unstable industry. Virtue signalling is very important in that environment.
My recommendation to a young developer is not to reject virtue signalling because it is shabby, ignoble and false. Rather embrace it, use it to secure your cubicle over the long term.
|
|
|
|
|
Like you I use VB in a variety of incarnations for many years. Eventually I decided to take the plunge and change to C#. For me it was mostly pretty easy to change, there are still one or two things that occasionally catch me out but now when I go back to VB code I have to think about it more than I used to. If that's not enough, I think Resharper works better with C#
|
|
|
|
|
Or - forget both of them, try F#[^], FTW…
(And I started with ZX BASIC too, back in the day - although Z80 assembly pretty soon came along!)
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
Most replies here are likely to ignore the fact that you are well versed and productive in VB and tell you that you should use C# because VB is evil. 