Freigeben über

Visual Basic Power Packs is included in Visual Studio 2008 SP1

  • Artikel

After Visual Basic Power Packs 3.0 was released to the web, we got a lot of questions and feedbacks from Visual Basic Power Packs MSDN forum.   So when Visual Studio 2008 Service Pack 1 was about to release, we decided to ship  Visual Basic Power Packs with all the bug fixes with this service pack.  While you can still use the web release of the VB Power Packs, it is recommend that you use the version included with Visual Studio 2008 SP1.

If you had installed Visual Basic Power Packs 3.0, you would end up with two tabs in the toolbox, one labeled “Visual Basic PowerPacks” (released with Visual Studio) and “Visual Basic PowerPacks 3.0” (web release).

clip_image002

To differentiate these two versions, the assembly name is changed to Microsoft.VisualBasic.PowerPacks.VS.dll.   If you have an existing application that is using Visual basic Power Packs 3.0 or lower version, you can upgrade to the new VB Power Packs by deleting the reference to Microsoft.VisualBasic.PowerPacks.dll and add reference to Microsoft.VisualBasic.PowerPacks.VS.dll.  

clip_image004

We also provided a new bootstrapper package for the new VB Power Packs.   So if you were using Windows installer or ClickOnce to deploy your application, you need to also change the prerequisites of your setup project to point to the new bootstrapper package.

Comments

  • Anonymous
    July 23, 2009
    Now Visual Basic Power Packs making Visual Studio 2008 Service Pack1 more effective.

  • Anonymous
    July 24, 2009
    Will the VB power pack be included in VS2010?

  • Anonymous
    July 24, 2009
    Yes, the VB Power Packs will be inlcuded in the VS2010.

  • Anonymous
    August 01, 2009
    The comment has been removed

  • Anonymous
    August 02, 2009
    Hi, Chris, I'm not sure if I fully understand your scenario. If you set "HomeSite" to be the install location, it will point to the new bootstrapper package. Or could you be more specific about your scenario please?

  • Yang
  • Anonymous
    September 14, 2009
    The comment has been removed
  • Anonymous
    September 16, 2009
    Hi, Will, Sorry that we cannot tell what the problem is with the error you copied. Could you please log a bug at MS Connect (http://connect.microsoft.com/) so that we could follow up with you for more information? Thanks! Yang