Generate setup from within Visual Studio not working

[mvirs8]

I am trying to create a setup project from within Visual Studio 2013. I chose INSTALLAWARE, Create Setup Project, then Setup Properties, and set values for all properties. When I ran Build Setup, I got an error referring me to the .log file:

Building Project: MVIRS Manager
Output Folder: C:\Users\Peter Kipe\Documents\Visual Studio 2013\Projects\MVIRS Manager\InstallAware\Release\UncompressedDeployment Type: Uncompressed Directory Layout
Code Signing: Disabled
Compression: Best
Compiler Variables: UAC=highestAvailable,BUILDMODE=CD,LANGUAGE=English,"TITLE=MVIRS Manager",TARGETDIR=$TARGETDIR$,IADIR=C:\PROGRA~2\INSTAL~2,PROJDIR=C:\Users\PETERK~1\DOCUME~1\VISUAL~4\Projects\MVIRSM~1\INSTAL~1,IAVER=19.01
###
Cleared output folder C:\Users\Peter Kipe\Documents\Visual Studio 2013\Projects\MVIRS Manager\InstallAware\Release\UncompressedBuilt plug-in action (Un)Install MSI Setup
Built plug-in action File Bag
Copied file C:\Users\Peter Kipe\Documents\Visual Studio 2013\Projects\MVIRS Manager\bin\Debug\MVIRS Manager.exe
Error during build: Cannot open file "C:\Windows\assembly\GAC\ADODB\7.0.3300.0__b03f5f7f11d50a3a\ADODB.dll". The process cannot access the file because it is being used by another process

When I looked at the folder tree using Windows Explorer, there is no GAC folder. What am I doing wrong, or how can I fix the problem?

I downloaded the white paper "Using InstallAware 7 To Deploy Microsoft .NET Framework Applications", but it is out of date in many respects, and it doesn't appear to answer this problem.

Thanks, Pete

[FrancescoT]

Dear Pete,

I believe the error is caused due the fact that your application uses that ADODB.dll component. The Visual Studio add-in automatically tries to include the dependencies used by the application and for what concerns your specific issue, the first found, it's the assembly that seems to be registered under the GAC of your system.

To solve your problem, load your project from the InstallAware IDE and remove/comment-out the entry used to install such file. Successively, include that file in your project from different location. It is always a good practice to use a separate folder where all the files used by the project are available. This removes the possibility that the project files can be shared or used by a different process.

For what concerns the white paper "Using InstallAware 7 To Deploy Microsoft .NET Framework Applications"; it's true that is not a recent document, but this because nothing is changed with the steps required to Deploy a Microsoft .NET Framework Application.

Regards