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
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Using .Net and SMO on multiple SQL versions

Using .Net and SMO on multiple SQL versions

Scheduled Pinned Locked Moved Database
csharpdatabasehelpquestiondiscussion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    devenv exe
    wrote on last edited by
    #1

    Is there a way to create a single .Net application that uses SMO and have it work correctly on a box with SQL 2008 R2 as well as on a box with SQL 2012? The two solutions I've found so far are: 1) Create a version of the application for each version of SMO. 2) Create a version of the application with the latest SMO. Install the latest SMO on all client boxes. I'm not really thrilled with either option. Any thoughts or help is greatly appreciated

    "Coming soon"

    L 1 Reply Last reply
    0
    • D devenv exe

      Is there a way to create a single .Net application that uses SMO and have it work correctly on a box with SQL 2008 R2 as well as on a box with SQL 2012? The two solutions I've found so far are: 1) Create a version of the application for each version of SMO. 2) Create a version of the application with the latest SMO. Install the latest SMO on all client boxes. I'm not really thrilled with either option. Any thoughts or help is greatly appreciated

      "Coming soon"

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      EricCiz wrote:

      I'm not really thrilled with either option.

      I don't know any others besides these, do you? The second option "sounds" like a simple one; just program against the latest interface and update all the components on the client-computers. The first option "is" the simple one; create a version-agnostic wrapper, and two version-specific implementations (as small as possible).

      Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] They hate us for our freedom![^]

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

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