2 points | by rimlessspecs 10 hours ago
4 comments
You'd create macros or templates. In C# & VB.NET you can alias your imports for simpler/smaller code below.
Imports Word = Microsoft.Word ' VB using Word = Microsoft.Word // C#
Imports you only do once so that wouldn't be a huge pain... Though, SOLID/DRY would be a pain with many more imports.
You could also not use taps in toilets at home, and walk to the local river or something... but why would you ?
copy paste from the other files that I'm importing?, after checking out docs and what it does (and how)
I assume yes they would have to verify it somehow...
You'd create macros or templates. In C# & VB.NET you can alias your imports for simpler/smaller code below.
Imports Word = Microsoft.Word ' VB using Word = Microsoft.Word // C#
Imports you only do once so that wouldn't be a huge pain... Though, SOLID/DRY would be a pain with many more imports.
You could also not use taps in toilets at home, and walk to the local river or something... but why would you ?
copy paste from the other files that I'm importing?, after checking out docs and what it does (and how)
I assume yes they would have to verify it somehow...