Results 1 to 7 of 7

Thread: VS2003 controls in VS2002

  1. #1

    Thread Starter
    Fanatic Member pax's Avatar
    Join Date
    Mar 2001
    Location
    Denmark
    Posts
    840

    Question VS2003 controls in VS2002

    Hi.

    Imagine this:
    I make a UserControl DLL in VS 2003, of course using Framework V1.1

    Now, could I use that control in a VS 2002 project (provided that both Framework V1.0 and Framework V1.1 is installed, of course)?
    I wish I could think of something witty to put in my sig...

    ...Currently using VS2013...

  2. #2
    I'm about to be a PowerPoster! mendhak's Avatar
    Join Date
    Feb 2002
    Location
    Ulaan Baator GooGoo: Frog
    Posts
    38,170
    My (limited) knowledge of VB.NET tells me: yes.

    I would wait for someone to confirm this though.

  3. #3
    Hyperactive Member CyberHawke's Avatar
    Join Date
    May 2004
    Location
    Washington DC
    Posts
    477
    Tho I am not intimately familiar with the differences in the two versions of the framework, I am familiar enough to know that if you make function calls in your 1.1 version control, it probably will not work in your 1.0 version project.

    Now that I have provided an answer, could you please tell me what in the world would possess you to do such a thing?

  4. #4
    Sleep mode
    Join Date
    Aug 2002
    Location
    RUH
    Posts
    8,083
    It depends on which Framework your assembly (project) targets . You can set this via the project properties window . You can target both by the way .

  5. #5
    Fanatic Member
    Join Date
    May 2002
    Posts
    746
    Originally posted by CyberHawke
    Tho I am not intimately familiar with the differences in the two versions of the framework, I am familiar enough to know that if you make function calls in your 1.1 version control, it probably will not work in your 1.0 version project.

    Now that I have provided an answer, could you please tell me what in the world would possess you to do such a thing?
    I thought, and I could be really wrong here, that the list of breaking changes from 1.0 to 1.1 was pretty short - that the vast majority of things would continue to work.

  6. #6

    Thread Starter
    Fanatic Member pax's Avatar
    Join Date
    Mar 2001
    Location
    Denmark
    Posts
    840
    Hi guys.

    Thanks for your answers. Since none of them are really conclusive I guess I have to try it.

    The reason I wanna do this, is because some of the people that are going to use the control are only using VS 2002 (and are too cheap to update ).

    So if they only need the V1.1 redistributable to use the control, I can easily create a wrapper-class for e.g. the FolderBrowserDialog and other V1.1 specific functions.
    This is also the reason why I can't target the control to V1.0. It kind of defeats the purpose.

    I know that it would require my users to distribute with both V1.0 and V1.1, but that's up to them.
    Besides, it only going to be used in-house so I guess it would be ok.

    At any rate, I will try it tomorrow and I will post the result, just in case anyone else was wondering the same thing.

    Thanks again guys.
    I wish I could think of something witty to put in my sig...

    ...Currently using VS2013...

  7. #7

    Thread Starter
    Fanatic Member pax's Avatar
    Join Date
    Mar 2001
    Location
    Denmark
    Posts
    840
    Hi guys.

    I have just tried it, and it does not appear to work.
    At least, when I tried to add the DLL to the toolbox, it claimed that there where no items in the DLL that could be placed in the toolbox.

    I tried just adding a reference, which went fine. I could then Dim it thru code, but it failed when instantiating it.
    My control extracts some icons from Shell32.DLL, and the error was with Win32 Icon Handle, so it may not have anything to do with the framework, but the OS it self. (My V1.1 machine is XP and the test pc is Win2000).

    But it doesn't matter. If it can't be placed in the toolbox I don't think it's worth it.

    I just have to do what Pirate said, and target the control for V1.0 and miss out on the new features of V1.1
    I wish I could think of something witty to put in my sig...

    ...Currently using VS2013...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width