Hi Redgate Team,
I wanted to provide a brief description of how we are integrating Smart Assembly into our build pipeline, including details on the download, installation, activation, build, and deactivation processes.
1. Download:
We download the Smart Assembly installer package directly from the official NuGet repository (https://api.nuget.org/v3/index.json) using a NuGet command in our pipeline. This ensures we always use the latest available version.
2. Installation:
After downloading, we extract and install Smart Assembly silently on the build agent using PowerShell and msiexec. The installation path is then located programmatically for use in subsequent steps.
3. Activation:
The pipeline includes a step to activate Smart Assembly using our license key before the build process begins. This ensures the tool is fully functional during the build.
However, we have observed an intermittent issue during this step: sometimes the activation fails with the error
“Program 'SmartAssembly.com' failed to run: Operation did not complete successfully because the file contains a virus or potentially unwanted software.”
This appears to be caused by the build agent’s antivirus or security software occasionally flagging the Smart Assembly executable as a potential threat, which interrupts the activation and build process.
4. Build:
Smart Assembly is invoked via command line to process our assemblies according to the configuration specified in our .saproj project file. This step handles obfuscation and any other configured protections.
5. Deactivation:
At the end of the pipeline, we run a deactivation step to release the license. This is done to comply with licensing terms and to ensure the license can be reused in future builds.
Since we are downloading Smart Assembly from the official public NuGet source, could you please advise why this issue might be occurring with Smart Assembly? Any guidance on how to prevent or resolve this would be appreciated.
If you need further details or have any questions about our implementation, please let me know.
Hi Redgate Team,
I wanted to provide a brief description of how we are integrating Smart Assembly into our build pipeline, including details on the download, installation, activation, build, and deactivation processes.
1. Download:
We download the Smart Assembly installer package directly from the official NuGet repository (https://api.nuget.org/v3/index.json) using a NuGet command in our pipeline. This ensures we always use the latest available version.
2. Installation:
After downloading, we extract and install Smart Assembly silently on the build agent using PowerShell and msiexec. The installation path is then located programmatically for use in subsequent steps.
3. Activation:
The pipeline includes a step to activate Smart Assembly using our license key before the build process begins. This ensures the tool is fully functional during the build.
However, we have observed an intermittent issue during this step: sometimes the activation fails with the error
“Program 'SmartAssembly.com' failed to run: Operation did not complete successfully because the file contains a virus or potentially unwanted software.”
This appears to be caused by the build agent’s antivirus or security software occasionally flagging the Smart Assembly executable as a potential threat, which interrupts the activation and build process.
4. Build:
Smart Assembly is invoked via command line to process our assemblies according to the configuration specified in our .saproj project file. This step handles obfuscation and any other configured protections.
5. Deactivation:
At the end of the pipeline, we run a deactivation step to release the license. This is done to comply with licensing terms and to ensure the license can be reused in future builds.
Since we are downloading Smart Assembly from the official public NuGet source, could you please advise why this issue might be occurring with Smart Assembly? Any guidance on how to prevent or resolve this would be appreciated.
If you need further details or have any questions about our implementation, please let me know.