ApexSQL Script Standard 2018.01

Includes Visual themes and new Visual Language Dictionary for Microsoft Visual Studio.

Features

• Visual themes.
• Visual Language Dictionary for Microsoft Visual Studio for iconography and other imagery concepts applied.
• "Manage Owners" option is added in New Project form.
• Added /on (/output_name) and /eso (/exclude_schema_objects) CLI switches.

Fixes

• The Windows taskbar is not shown on hover, when the Auto-hide the taskbar option is checked, and the application is maximized
• Missing the Row filter option for the Structure view
• Missing a step in the installer that will check if there is a previous version installed and to remove it
• The Run executable installer now check-box gets unchecked once clicked the Back button in the Export batch form
• When adding pattern in Object filter step of the wizard, pattern should become active when checked
• The 'loading objects failed' error is encountered if no database is selected when initiating Schema mapping or Object filter
• Default installation folder name is not by standard, it must be “ApexSQL Script"
• The path given in the Output folder text-box is not consistent with the one given in the Save as form when saving the batch file
• Unresponsive progress forms when connecting datasource - selecting Schema mapping or Object Folder
• The Create database option cannot be saved as "my defaults" in the connection form, the structure tab
• Missing the dialog whether to uninstall previous version
• Parsing errors keep reoccurring once encountered
• Automatic updates are not checked by the default
• Indicator of excluded objects doesn't respond in status bar (Data tab)
• Indicator of excluded objects doesn't respond in status bar (Structure tab)
• Lack of summary after scripting process
• The Schema mapping tab is not consistent with other ApexSQL applications
• The Additional scripts tab is not consistent with other ApexSQL applications
• Missing the Logging option in the Package tab
• The Package tab is not consistent with other ApexSQL applications
• The Working folder is redundant as a source control system
• Missing line numbers in the Where clause window
• Unable to execute file in temporary directory. Setup aborted, when downloading and installing ApexSQL Script
• "Could not load file or assembly 'Newtonsoft.Json, Version=7.0.0.0...' or one of its dependencies. The system cannot find the file specified" error is encountered when the Test or Finish button is clicked once all system logins are provided for TFS
• Objects still showing for scripting even if they were deselected in the Object filter
• Compatibility level option is not saved in the project
• "Parse error: [Incorrect syntax near 'READ']" error is encountered while parsing the procedure
• Missing the /exclude_dependent_objects switch that will exclude objects that depend on the excluded objects specified in the /exclude
• The license file disappears when virtual machine is stopped and then run on Amazon AWS
• "Cannot insert duplicate key in object 'SchemaName.TableName'. The duplicate key value is (0)" error is encountered when executing the generated SQL script to create a trigger after renaming a table and creating a view on which trigger depends on
• The license file disappears when virtual machine is stopped and then run on Amazon AWS
• Wrong CLI switch is used for the output name in the Save as batch window when SQL script is selected as the output type
• Arguments can be combined in output_elements switch error is encountered while exporting the CLI help file into HTML
• Wrong switches and values are generated and missing switches in the Save as batch window when the C# solution is selected as the output type
• Wrong switches and values are generated and missing switches in the Save as batch window when the Executable installer is selected as the output type
• Wrong switches are generated and missing switches in the Save as batch window when the Script folder is selected as the output type
• Wrong switches are generated and missing switches in the Save as batch window when the Source control is selected as the output type
• When using Source control as the Output type and clicking on Commit without providing source control credentials. the app crashes
• The Create database option cannot be saved as "my defaults" in the connection form, the structure tab
• When using dual setup monitor environment, sometimes application starts on the secondary monitor even though it was used on the primary
• Changes:
  • The application now requires Microsoft .NET framework 4.7.1
  • Windows Vista and Windows Server 2008 are no longer supported
  • The /pf switch is changed to /pr CLI switch
  • Removed /fl, /in, /fn, /sta, /stc, /stl, /stc1, /stc2 and /stc3 CLI switches