Bug in Packager -- Filename

dm4714dm4714 Posts: 28
edited December 5, 2005 12:22PM in SQL Packager Previous Versions
Can someone please fix the bug when saving a package and using a number at the end of the filename.

For example, if I save a .Net Executable as:

MyAppSQLFullv100

it saves the file as

MyAppSQLFullv100.

However, if I go back to edit the package and save again, it never displays the 100 and I end up creating a new .EXE filename. Arrghhh

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hello,

    I'm unaware of this problem. I haven't encountered an error when putting a number at the end of a package name.

    The only problem I'm aware of is when you put a period in the filename of the package, and that happens because when Packager creates a .NET executable, it uses that filename as the project's namespace. The dot will cause Packager to think that there are two namespaces and that isn't allowed.
  • Hi,

    I agree with the original post.

    On the "Create .NET executable" dialog page if I give the name:

    MyDatabase_100

    then it creates a .NET exe called MyDatabase_100.exe.

    I then save and close the package.

    When I then edit the package and go back to this page the name is now populated with:

    MyDatabase_

    So the numbers have been lost.
  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hello James,

    That's a bit more clear. I'll have a look into that...
This discussion has been closed.