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. General Programming
  3. Visual Studio
  4. Visual Studio .Net Integration SDK

Visual Studio .Net Integration SDK

Scheduled Pinned Locked Moved Visual Studio
csharpvisual-studiocomquestion
3 Posts 2 Posters 12 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.
  • P Offline
    P Offline
    Paul Selormey
    wrote on last edited by
    #1

    I have read that this SDK is now released for free use. Anyone has the link to its homepage or site for download? Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.

    R 1 Reply Last reply
    0
    • P Paul Selormey

      I have read that this SDK is now released for free use. Anyone has the link to its homepage or site for download? Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.

      R Offline
      R Offline
      Russell Morris
      wrote on last edited by
      #2

      It's free for Enterprise MSDN customers, not 'free' for anyone who wants to poke around with it (unfortunately). However, there is so much that can be done to VS.NET's design-time environment that the VSIP SDK is really only necessary for huge and vastly complex integration projects (like ActiveState's Perl.NET). Custom ControlDesigners, RootDesigners, CodeDomSerializers, ExtenderProviders, etc... really gives the developer alot of power to reinvent the design-time process to fit whatever specialized components they are developing. We're building tons of new design-time code at my company, and I don't think we're going to need the VSIP SDK to get what we want. The publicly available extensibility built into VS.NET is enough. -- Russell Morris "WOW! Chocolate - half price!" - Homer Simpson, while in the land of chocolate.

      P 1 Reply Last reply
      0
      • R Russell Morris

        It's free for Enterprise MSDN customers, not 'free' for anyone who wants to poke around with it (unfortunately). However, there is so much that can be done to VS.NET's design-time environment that the VSIP SDK is really only necessary for huge and vastly complex integration projects (like ActiveState's Perl.NET). Custom ControlDesigners, RootDesigners, CodeDomSerializers, ExtenderProviders, etc... really gives the developer alot of power to reinvent the design-time process to fit whatever specialized components they are developing. We're building tons of new design-time code at my company, and I don't think we're going to need the VSIP SDK to get what we want. The publicly available extensibility built into VS.NET is enough. -- Russell Morris "WOW! Chocolate - half price!" - Homer Simpson, while in the land of chocolate.

        P Offline
        P Offline
        Paul Selormey
        wrote on last edited by
        #3

        Well, we are on Architect version, so where can I find it? I am not doing any integration work now, but wish to know if the news and true and also play with the SDK - learning. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.

        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