Timeline for Convert a team from VB.Net to C#.Net
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2017 at 8:14 | comment | added | Bernhard Hiller | @aaroncatlin Of course it is possible to write clean object-oriented code in VB. Feel lucky that you have such a great team. Now scrutinize the job candidates that also they have that knowledge, instead of being superstitious because of their language preference. When you advertise the job with those keywords, C# developers should be more comfortable with sometimes maintaining such code which is still in VB. | |
| Apr 4, 2017 at 19:16 | comment | added | SeraM | @aaroncatlin From my experience, not quite as bad as single code blocks, but I've seen little separation of forms from business logic, grids connected to a dataset (and that directly to db) instead of a business object, etc. | |
| Apr 4, 2017 at 13:20 | comment | added | aaroncatlin | Based on this answer, I'd say that our current VB code base was far from typical. It utilises everything you might hope for with regards to structure and OOP. I don't understand this idea of "typical VB code". Is the assumption that VB developers write entire applications in single code blocks with no signs of OOP in sight? | |
| Apr 4, 2017 at 9:14 | history | answered | Bernhard Hiller | CC BY-SA 3.0 |