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
V

v3ct0r

@v3ct0r
About
Posts
3
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Using... before or after the Namespace
    V v3ct0r

    Thank you. I agree with you, I'll be pulling my using statements to the top of the page. Funny thing however, Microsoft had a Direct X 9 sample that had the using statments inside the namespace, this is actually where I picked it up from. Perhaps there was a specific purpose that I overlooked. Anyway, thanks everyone else as well.

    C# performance

  • Using... before or after the Namespace
    V v3ct0r

    Sweet thanx. I don't know why I've adopted putting them inside the namespace, I was happy with them outside and then suddenly I decided to put them in for no apparent reason:rolleyes:.

    C# performance

  • Using... before or after the Namespace
    V v3ct0r

    This is a bit confusing, I've seen the using keyword used both before and after the Namespace. using System; using System.Data; namespace MyCompany { public MyClass {} } as well as namespace MyCompany { using System; using System.Data; public MyClass {} } I've used both and cannot find a difference in actual performance. Is this something that is purely for personal choice or is there some sore of advantage to using one over the other.

    C# performance
  • Login

  • Don't have an account? Register

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