Timeline for Convert a team from VB.Net to C#.Net
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 5, 2017 at 7:10 | comment | added | aaroncatlin | @Doc Brown - I guess I wasn't that worried about that point because our existing VB base is split into deep namespaces and has clear separation of entities, business and data logic that means we only ever have to convert functionality from small projects. My expectation is that we will mark existing logic as obsolete and build new logic and any logic that needs updating in new C# project files. In our circumstances, both answers are therefore right, though I appreciate this wouldn't necessarily apply to all. If I could mark both, I would. | |
| Apr 4, 2017 at 20:12 | comment | added | Doc Brown | This should be the accepted answer. Though JeffO's answer is not bad overall, his bullet point 2 is still too rewrite-friendly. But I guess the OP is not willing to take this warning seriously and will most probably learn it the hard way. | |
| Apr 4, 2017 at 2:28 | history | answered | RubberDuck | CC BY-SA 3.0 |