Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
A

awicurrent

@awicurrent
About
Posts
1
Topics
0
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Visual Basic - when to switch?
    A awicurrent

    As I see it VB6 is the same as visual basic for applications. So as long as they are going to support VBA it seems logical Microsoft will have to support VB6. My concern is that the Microsoft people are not merging VB.net nominclature with C#. They share the same code base now, so why not upgrade the editor to handle both syntax in one environment. That way there would never be a need to retire either one. Computers are powerful enough to support that structure now which may not have been the case years ago. I prefer personally "if then ....... end if" for tracing purposes over the c# equivalent which ends everything with a }. Nested loops with everything sharing the same ending are much more difficult to debug. Thank you.

    The Lounge com question
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups