I'm trying to build a TDS project the TFS hosted server. The project uses the HedgehogDevelopment.TDS package, but when build time comes, a license exception occurs.
I am passing the owner and key information to visual studio in this way:
/p:TDS_Owner="$(TDSOwner)" /p:TDS_Key="$(TDSKey)"
Where the variables are the owner and key. I have verified that the values are correct, yet I still get a license exception, indicating that TDS cannot find these values.
Is there a flaw in how I am giving visual studio these parameters? How can I get a TDS project to build using the HedgehogDevelopment.TDS package?
First, please make sure you have installed TDS on the build server.
You can actually include the License info with a config file by following below steps.
Add this file manually here: xxx(TDSFilesFolder)\HedgehogDevelopment\xxxProject\vx.0
Call the file TDSLicense.config
Save the following (with your license information in) in the file: <?xml version="1.0" encoding="utf-8" ?> <license Owner="CompanyName" Key="aaaa-bbb-ccc-dddd" />
If it's a permissions issue with reading the license from the registry - this should sort it out. More detail info you can take a look a this blog.
Related
I am trying to sign all executables + dll files in my application, within an Azure Pipeline, using Azure signtool for that. (doing basically the described here) - on the result of running dotnet publish.
Exception is updater.exe, because it is generated by Advanced Installer API or some other proprietary way. Signing the updater.exe file that lies inside Advanced Installer installation folder /x86/updater.exe - does not help (it will work, but the updater.exe that is deployed when installing the MSI is not signed, meaning it is generated during processing of the .AIP file, which happens after running dotnet publish)
Is there a way the updater.exe AI generates (with the custom icon, etc) to be created using AdvancedInstaller.com command line API ? How ?
The question has already been answered in the forums here:
https://www.advancedinstaller.com/forums/viewtopic.php?f=5&t=50297#p127034
Using Visual Studio 2019 to publish an update to an existing windows store application. This worked a week ago.
Our solution builds without error. When I go to create the setup package I get an error "Failed to sign 'D:\dev\MeyerMusic\MeyerTablet\TabletDistribution\bin\AnyCPU\Release\MeyerMusicTabletSetup_2.6.6.0_AnyCPU.msix'."
We are distributing the application as a Microsoft Store app under the existing app name.
Last week on this same development computer I built version 2.6.5 as well as many packages before that.
The error number is blank or missing. I do not have a reason for the failure. I only see one fact in the error message and that points to line 4574 in the file: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets
That line is this:
<SignAppxPackage Condition="'$(AppxPackageSigningEnabled)' == 'true'"
AppxPackageToSign="$(AppxMainPackageOutput)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
CertificatePassword="$(PackageCertificatePassword)"
HashAlgorithmId="$(AppxHashAlgorithmId)"
EnableSigningChecks="$(EnableSigningChecks)"
SignAppxPackageExeFullPath="$(SignAppxPackageExeFullPath)"
TempCertificateFilePath="$(TempCertificateFilePath)"
VsTelemetrySession="$(VsTelemetrySession)"
SigningTimestampServerUrl="$(AppxPackageSigningTimestampServerUrl)"
SigningTimestampDigestAlgorithm="$(AppxPackageSigningTimestampDigestAlgorithm)"
/>
Troubleshooting steps:
Attempted to build a side load package. Results in same error
Successfully built a side load package that was not signed
I have restarted Visual Studio
I have rebooted the machine
I have deleted OBJ, BIN for the entire solution
I have looked for errors in the event log but none have been found so far.
After uninstalling KB4535996 the problem was resolved.
I found this via a tip from the following post: https://developercommunity.visualstudio.com/content/problem/934967/uwp-error-failed-to-sign.html
I am trying to build an automatic deploy system for Magnolia 5.4 EE. For this, I exported the license config node /config/modules/enterprise/license to a file config.modules.enterprise.license.xml and attached this to the mgnl-bootstrap/my-module-directory of my module.
In this bootstrap-directory, other xml configuration files are present and are entered as expected into the configuration database. However, after deploy Magnolia still asks me to enter the license key - everything else works fine, my product is deployed, etc.
I tried to find information in the Magnolia documentation, but to no avail. Anyone here who was able to automatically deploy a Magnolia EE?
It should work if you add a dependency to enterprise magnolia module in your my-module descriptor file. This way the enterprise module will be installed before your module, and you just add a new node to its config.
Another option is to add the license import file to WEB-INF/bootstrap/common, the difference here is that everything in that folder gets bootstrapped after all modules are started.
I have created MSI package using advanced Installer. It contains App Config to which i have to pass the siteURL which varies depending on location. I need to pass the siteurl to app config when msi is installed . Please help me with it. I am new to Advanced Installer
You can check the online user guide for Advanced Installer, it has a lot of useful info. For example the article on importing and editing XML config files.
Or how to add a custom dialog and write in the system the values captured from the end users.
EDIT: additional answer regarding command line
You can run the installation silently from the command line but you will still see the message box saying the package is built with a trial. You will not see the standard MSI dialogs. And the trial messages will be gone once you purchase license for Advanced Installer.
Please note that your command prompt window (cmd.exe) must be launched as administrator, if your installation is installing per-machine (i.e. you write in Program Files or HKLM registry hive). Otherwise the installation will fail silently and you will not know why, because on silent installation the OS will not show an error message.
Here is a command line example:
msiexec.exe /i C:\setup\installer.msi /qn ID="235424" SiteURL="www.example.com"
Please note that it is not recommended to use private properties, i.e. properties with lower case letters in their name, we recommend public properties, for example: SITE_URL.
I keep getting the TF60024 error "Unable to create the intermediate database required by VSS Converter on Microsoft SQL Server .\SQLEXPRESS. CREATE DATABASE permission denied in database 'master'." When I run the VSSConverter with "Migrate" and my xml file.
Here is my XML file:
<?xml version="1.0" encoding="utf-8"?>
<SourceControlConverter>
<ConverterSpecificSetting>
<Source name="VSS">
<VSSDatabase name="z:\CHS_SourceSafe"></VSSDatabase>
</Source>
<ProjectMap>
<Project Source="$/Account Automation SQL" Destination="$/Account Automation SQL"></Project>
<!--Other projects excluded-->
</ProjectMap>
</ConverterSpecificSetting>
<Settings>
<TeamFoundationServer name="CHS-TFS" port="8080" protocol="http" collection="tfs/DefaultCollection"></TeamFoundationServer></Settings>
</SourceControlConverter>
My network guy told me to mention:
I am a local admin on the Server (CHS-TFS)
I am a sys adm on both TFS 2010 64 bit and SQL Server (2008 R2 64 bit).
I'm running this from the (win 7): "c:\program files (x86)\Microsoft Visual Studio 10.0\Common7\IDE" folder.
The ANALYZE function returned 0 errors.
I've tried adding the ".root" to the end of the Source, that didn't help.
We also tried NT AUTHORITY\NETWORK SERVICE full access (thinking that maybe it was using that as a default login)
Any suggestions?
EDIT:
I found this one blog post:
http://blogs.msdn.com/b/dparys/archive/2009/09/17/create-database-permission-denied-in-database-master-my-fix.aspx
that seemed to deal with the issue, I worked though it, and still I'm getting the same error.
I finally figured out how to do this a different way. I watched this video:
You Tube video that explains other way of doing this
And downloaded this tool:
File to download
And it was much easier to do.