CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 1999
    Posts
    5

    BUG: VB6 Package Deployment Wizard failure



    Installation programs, generated by VB6 Package Deployment Wizard for Visual Basic Projects fail during startup with message, like this:


    "Invalid line in setup information file!


    Section: Setup1 Files

    @ODKOB32.DLL,$(WinSysPath),,$(Shared),6.18.98 12:00:00AM,16896,4.0.81.69"


    I have VisualStudio'98 Service Pack 2 installed on my machine.


    Somebody know anything about this "feature" and how to overrun it?

  2. #2
    Join Date
    Mar 1999
    Location
    Fl, USA
    Posts
    23

    Re: BUG: VB6 Package Deployment Wizard failure



    Hello Alex,


    this is not bug of the developement tool. I assume that you're using

    an english/american relase of VB on a German windows system. The problem

    is, that the packager uses the english time code DD/MM/YY or and your system

    is configured for the german one DD.MM.YY .

    U can easily get rid of the problem by setting the Date separator from '.' to forward slashes ( / ).

  3. #3
    Join Date
    Mar 1999
    Location
    Fl, USA
    Posts
    23

    Re: BUG: VB6 Package Deployment Wizard failure



    Hello Alex,


    this is not bug of the developement tool. I assume that you're using

    an english/american relase of VB on a German windows system. The problem

    is, that the packager uses the english time code DD/MM/YY or and your system

    is configured for the german one DD.MM.YY .

    U can easily get rid of the problem by setting the Date separator from '.' to forward slashes ( / ).

  4. #4
    Join Date
    Apr 1999
    Posts
    5

    Re: BUG: VB6 Package Deployment Wizard failure



    Thank you great! Your solution works!

    The "feature" is next:


    -when Deployment Wizard making new package, it write file dates to SETUP.LST file in _current_ regional setting format


    ,but


    -when Setup is being started, it able to recognize dates in English/US (or like this) formats only!


    It seems to be strange, why international settings affects so critical on Visual Studio (Enterprise Edition) Components!

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

Featured