C Visual Studio 2017 Setup Project Error 2727 Stack Overflow I create configuration projects (created as an "empty" project type in vs) and include the "content" of that project in the installer. the binaries get included as a merge module. When running an installation, windows installer error 2727 displays with the following message: the directory entry '[2]' does not exist in the directory table. [2] is a destination that should resolve to a primary key in the directory table.
C Visual Studio 2017 Setup Project Error 2727 Stack Overflow "error 2727: the directory entry ' [dir name]' does not exist in the directory table." i’ve checked my project settings, and all the folder paths seem correct. If the visual studio 2017 installer isn't able to properly update your existing version (and specifically if you have an older rc release), then you can try the following steps to clear the slate before attempting a fresh install: uninstall visual studio 2017 and the visual studio installer. delete the following directories:. The error code is 2727. i have found a set of msi error codes, and error code 2727 translates to the directory entry '[2]' does not exist in the directory table. could someone guide me towards fixing this? what should i do? [update] at the suggestion of cosmin pirvu, i have created an error log for my installer. I have a visual studio 2017 solution with four projects: a shared static lib (c ), a dll (c ) built with static dll linking, an exe (c ) built with dynamic linking, and a setup project that.
Installshield Visual Studio 2017 Setup Project Missing Stack Overflow The error code is 2727. i have found a set of msi error codes, and error code 2727 translates to the directory entry '[2]' does not exist in the directory table. could someone guide me towards fixing this? what should i do? [update] at the suggestion of cosmin pirvu, i have created an error log for my installer. I have a visual studio 2017 solution with four projects: a shared static lib (c ), a dll (c ) built with static dll linking, an exe (c ) built with dynamic linking, and a setup project that. You might need to roll your installation project back to a last known working copy and then work it forward bit by bit and see if you can detect the incremental change where the error first occurs. Refresh the dependendcies of the installer project. you can observe the duplicating references (see attached image). this issue prevents build a workable msi. the setup raises error 2727. expected behavior: references in the installer project should not be duplicated. and target msi should work. I checked the release settings the 'keep unused directories' is set to 'no' for the setup project. i am still getting the same errors as mentioned in the thread. thanks. To get help on a particular diagnostic message in visual studio, select it in the output window and press the f1 key. visual studio opens the documentation page for that error, if one exists. you can also use the search tool at the top of the page to find articles about specific errors or warnings. or, browse the list of errors and warnings by tool and type in the table of contents on this page.
Comments are closed.