{"id":116,"date":"2012-08-22T04:45:53","date_gmt":"2012-08-22T12:45:53","guid":{"rendered":"http:\/\/www.installaware.com\/blog\/?p=116"},"modified":"2012-08-22T04:45:53","modified_gmt":"2012-08-22T12:45:53","slug":"list-of-bug-fixes-in-installaware-nx-65","status":"publish","type":"post","link":"https:\/\/www.installaware.com\/blog\/?p=116","title":{"rendered":"List of Bug Fixes in InstallAware NX (65)"},"content":{"rendered":"

The Most Recently Used Files listing was half empty.
\nUnpin from Start Screen was not functioning correctly with the final release of Windows 8.
\nSet Breakpoint was not displaying the breakpoint after a bookmark had been inserted.
\nEdit XML File lacked a Browse button to pick the XML document to edit visually.
\n64 bit ODBC data sources were not created successfully using the Native Engine.
\nThe automation interface lacked a build function which permitted specifying the parent window handle to the build window.
\nRead-only files were always overwritten when saving projects.
\nThe Impact theme contained a production progress dialog from InstallAware<\/strong> Virtualization, instead of the actual template progress dialog with interactive HTML.
\nInserting AVI animations in the Dialog Editor caused seemingly random errors with locating the AVI file.
\nMultiple files could not be selected to add to a setup project as new dialogs.
\nThe Project Manager did not remember the previous folder and\/or the project folder used when last adding resources to a project.
\nPatch references could not be added via the command line Build Tool.
\nSingle Instance setups, when launching second or more instances, would crash with random errors.
\nThe Native Engine did not properly load old installation data in certain cases.
\nPatches did not properly load old installation data if the product name was changed between versions.
\nRun commands in the IDE did not run new direct MSI built setups.
\nSome duplicate compiler variables were re-injected in duplicates (or more) when a build failed with a compiler variable conditional error.
\nBatch builds set some build mode compiler variables incorrectly.
\nPatches built after batch builds may have failed to enable the patch compiler variables, causing problems with actual patch application.
\nCompiler variable override values sometimes failed to override their desired targets if a default value was previously defined.
\nPatch references did not accept new direct MSI built setups.
\nThe Group Policy built MSI files lacked payload extraction progress report.
\nThe Group Policy built MSI files could not be aborted once starting extraction.
\nThe Group Policy built MSI files caused double User Account Control elevation prompts.
\nThe Group Policy built MSI files caused User Account Control elevation prompts that were sometimes hidden in the background.
\nAdding new scripts did not default to the current project folder.
\nSaving existing scripts did not default to the current project folder.
\nAutomatic code signing for all setup binaries failed after one effort, instead of accounting for intermittent network connectivity issues.
\nThe application user model identifier was sometimes not being properly set on Windows 8.
\nIf Visual Studio 2012 was started at least once before installing InstallAware<\/strong>, the InstallAware<\/strong> Add-In for Visual Studio 2012 would not be registered with Visual Studio.
\nVery slow runtime performance with InstallAware<\/strong> setups using large scripts.
\nIncorrectly overriding the NATIVE_LOGGING pre-defined variable without path information caused complete system drive deletion.
\nSome feature descriptions in the InstallAware<\/strong> setup were not fitting in their allocated space.
\nShortcuts could not be pinned into the Start Screen with the final release of Windows 8.
\nLow resolution icons were incorrectly used in the New Project | Custom tab when promoting setup projects into user made templates.
\nThere was no programmatic method to update the character set of dialog controls.
\nThe documentation for Set Access Control did not make it clear that the command is non-recursive in nature.
\nThe Display Dialog command editor control states malfunctioned in certain cases, leaving certain settings disabled until the command editor was re-initialized with the same command line twice in succession.
\nASP.NET version 4 application pools created by the Create Virtual Folder command sometimes contained superfluous versioning information in the application pool name.
\nASP.NET version 4 application pools created by the Create Virtual Folder command sometimes were accompanied by an unintended ASP.NET version 2 application pool in the desired name.
\nLiteral file exclusions were not honored by the Install Files command – unless wildcards were used, the exclusions would be still included in setup.
\nThe If command editor control states malfunctioned in certain cases, leaving certain settings disabled until the command editor was re-initialized with the same command line twice in succession.
\nThe GlowLabel control malfunctioned when double buffering states were being intelligently managed,
\nThe .NET Plug-In Bridge did not properly pass the state of variables back to the setup script.
\nInstalling .NET versions 2 through 3.5x failed on Windows 8.
\nInstallAware<\/strong> built plug-ins did not correctly set their parent window handle to the InstallAware<\/strong> IDE.
\nThe Dialog Editor did not refactor rules when a component name was changed, instead deleting all rules referring to the old component name.
\nProgress billboards did not resume from the last billboard shown between different displays of HTML progress enabled billboards, all activated within the same setup session.
\nSearch and Replace did not replace all occurrences of a given string literal in a single setup command.
\nThe Set Variable command editor sometimes did not reset the state of the “Persistent” option.
\nThe Continue command did not re-evaluate the loop conditional for While loops, unconditionally skipping to the next loop iteration.
\nA superfluous PackageAware<\/strong> folder would be created every time the InstallAware<\/strong> IDE or a built setup was run.
\nWhen setup invoked system tray commands, and the Explorer shell was unavailable or not started yet, setup would fail with a runtime error.
\nAll list views used in the IDE and setup engine lacked translucent selection rectangles.
\nThe SQL Server 2012 (Denali) runtime installation failed on Windows 8.
\nVirtual Machine detection failed to detect Hyper-V based virtual machines.
\nThe Portuguese spelling was incorrect in built setups and various places throughout the InstallAware<\/strong> tool chain.
\nThe command line Build Tool had intermittent build failures when running on 64 bit Windows.
\nThe InstallAware<\/strong> IDE instance name was incorrect.
\nThe Convert Path command behavior was undefined when the specified path did not already exist.
\nEditing a Create Shortcut command in the visual designers sometimes lost the associated icon.
\nIn rare instances, when a lot of identically named files were being included inside a single Web Media Block, the Weblock processing could fail at runtime, resulting in misleading extraction failure errors.
\nHybrid installation projects which combined 32 bit and 64 bit driver installations inside the same Web Media Block or the main setup executable would succeed in installing only the last referenced bitness driver in the setup script.
\nThe product name field in built EXE files was not injected.
\nThe product version field in built EXE files was not injected.<\/p>\n","protected":false},"excerpt":{"rendered":"

The Most Recently Used Files listing was half empty. Unpin from Start Screen was not functioning correctly with the final release of Windows 8. Set Breakpoint was not displaying the breakpoint after a bookmark had been inserted. Edit XML File lacked a Browse button to pick the XML document to edit visually. 64 bit ODBC … <\/p>\n

Continue reading “List of Bug Fixes in InstallAware NX (65)”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-116","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/116","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=116"}],"version-history":[{"count":2,"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/116\/revisions"}],"predecessor-version":[{"id":118,"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/116\/revisions\/118"}],"wp:attachment":[{"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=116"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.installaware.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}